I have searched EZ for this problem but I was unable to find any results. I am using the EVAL-ADV7625-SMZ board.
After installing a fresh copy of VisualDSP++ 5.1.2 off the ADI website, I opened up VisualDSP++ and navigated to File > Open > Project..., and then to VisualDSP 5.1.2/Blackfin/Examples/BF_7625_7625_X2.3.3REL_20150323/ADV7625_BF524.dpj, it won't open the project file. I get the following error window for a missing source file:
When I obtained the latest SDK software pack for my EVAL board (ADV7625_Evaluation_Board_Software-Rel2.4.0), it contained the following files in the SRC directory:
When I copied these files across (overwrote them) in the Examples\BF_7625_7625_X2.3.3REL_20150323\ADV7625_SW directory the situation never changed, and I still got the same error message.
"Could not locate the file: app_edid.c"
It seems that the software pack ADV7625_Evaluation_Board_Software-Rel2.4.0 does not contain app_edid.c.
Surely an example that comes packed with an IDE from Analog Devices for one of their own EVAL boards should at least open (let alone compile). Could it be that the example and the software pack are too far apart in date?
If so, could you recommend a software pack, EVAL-ADV7625-SMZ example, or both that actually open and compile?
There are differences in EDID related source files between X2.3.3 and 2.4.0.
Those modified files needs to be taken care when compiling the old project with new software package.
We will post…
Assuming that you replaced (overwrote them)software pack ADV7625_Evaluation_Board_Software-Rel2.4.0 files in the Examples\BF_7625_7625_X2.3.3REL_20150323\ADV7625_SW directory and following the above…
It won't be necessary to upload my sources for ADI to debug, I now have it working! I am very happy.
The key was to use VDSP++ to upload u-boot ONLY according to https://ez.analog.com/video…
We will post the updated VDSP project for 2.4.0 soon in EZ page.
Please follow the steps as shown below, build the project and let us know if you have any issues.
1. Remove app_edid.c and app_edid.h from folder XREP/EDID as shown below
2. Remove eedid.c and eedid.h & add edidmerge.c and edidmerge.h from folder MIDLWARE/EDID as shown below
3. In addition to the above, there are some additional files under OSD/firmware/source folder, please add those files also if you are using OSD.
Thanks for the fast response.I followed your instructions and I got the following error message:
----------------Configuration: ADV7625_BF524 - EVALADV7625SMZ----------------C:\Program Files (x86)\Analog Devices\VisualDSP 5.1.2\gmake-378: *** No rule to make target `ADV7625_SW/APP/XREP/OSD/firmware/source/osd_animation.c', needed by `EVALADV7625SMZ/osd_animation.doj'. Stop.No valid command(s) to build.Build was unsuccessful.
Assuming that you replaced (overwrote them)software pack ADV7625_Evaluation_Board_Software-Rel2.4.0 files in the Examples\BF_7625_7625_X2.3.3REL_20150323\ADV7625_SW directory and following the above mentioned steps.
Here we tried and we could build the project with the above mentioned changes. In another thread, we were discussing about the integrating your designed OSD and build the same?
To make sure, Are you trying with OSD files without modification(default OSD)doing the above steps or with new OSD?
If you are facing issue still, can you share the Project files via offline to check?
In the other thread here, I didn't overwrite the ADV7625_SW files with the files from ADV7625_Evaluation_Board_Software-Rel2.4.0.
So my steps were:
1) Take 'firmware' directory (containing include/ and source/) generated by Blimp and use it to replace the one at BF_7625_7625_X2.3.3REL_20150323\ADV7625_SW\APP\XREP\OSD inside the VDSP++ Blackfin Examples directory.
2) Replace the *.c and *.h files in ADV7625_SW\APP\XREP\OSD\DemoOsd with the *.c and *.h files generated by Blimp with the same name, except for blimp_external_api.c or blimp_external_api.h.
3) Open the ADV7625_BF524.dpj project in VisualDSP++ 5.1.2. Connect to target. Change all project options according to B.2 Project Settings To Do and B.3 Additional Settings To Do, Clean Project and Rebuild Project.
I got some compile warnings (mostly originating from the Blimp auto-generated code), but it did compile successfully. Unfortunately, using the flasher inside VDSP++, the generated binary didn't run, and nothing came up on my TeraTerm nor on my TV. If I used the debugger to "Run" or "Reset/Run" the same result occurred.
Do you think that it's necessary for me to include the skipped step of using the HPM files from ADV7625_Evaluation_Board_Software-Rel2.4.0?
If you are using X2.3.3REL software, then no problem. No need to replace.
If you want to use latest SDK software pack(ADV7625_Evaluation_Board_Software-Rel2.4.0), then the changes we mentioned to be taken care.
To integrate new OSD, the steps followed by you is correct. We assume that after U-Boot, you are not seeing anything on TeraTerm? We are not sure why you are not getting any output.
Can you share the project files offline?
Thanks Poornima for all your help.
I am using X2.3.3REL software. I'm actually getting nothing on TeraTerm, not even u-boot.
Could you confirm that I should be creating a *.bin firmware according to the below screenshots from the guide? If I intended on using Blackfin BF524 internal flash, should I be selecting "SPI"? I thought maybe Flash/PROM would be the correct choice for internal Blackfin flash?
It's early morning AEST, but as soon as I get to work tomorrow I'll post the source files here as *.zip.
Thanks again Poornima!
The key was to use VDSP++ to upload u-boot ONLY according to https://ez.analog.com/video/w/documents/689/how-can-i-restore-u-boot-on-eval-adv8005-smz.
After resetting the board, I interrupted u-boot countdown, and used YMODEM to upload my custom VDSP++ binary. I reset the board again and the TV showed up with the output of the BluRay player.
I then issued them command i2cw 0xF0 0x00 0x14 to enable OSD_EN bit and OSD blending, and the custom Blimp image showed up. Very happy! The demonstration to our customer who wants to use this chip is in 1 hour so I can breathe easily now thanks to your help.