no-os : 2019_r2
Windows 64-bit OS
I successfully built the HDL for the ADRV9001 project.
I am getting the following error when trying to build the no-os for the adrv9001
Use cmd, not cygwin.
the above build actually produced adrv9001.elf file.
I opened sdk workspace and added FSPL and .bit file and generated BOOT.bin
put it on SD card and using my ZED board, it printed the…
Yes, for me it failed when I tried JTAG boot on zed.
When I say it succeeded with SD Card boot, I mean adi_adrv9001_profileutil_Parse returned 0 and the code executed normally until Bye was printed…
I am still getting the errors shown in the above picture. Also, when I added
to the makefile, I didn't see any changes to the project source code.
Question: I see a "builds.json" in the project directory and it only mention "zcu102" board...does that mean ZEDBOARD is not supported?
The following link mention it as a supported carrier!
in order to see the changes made to makefile you need to delete the build directory and redo the build procedure.
builds.json is used for automated builds and does not contain the full list of possible hardware combinations, so no, it does not mean that zedboard is not supported. This is information that you'd normally get from the documentation (wiki). As a matter of fact, zed + adrv9002 is a possible combination both for 2019_r2 and master code.
I built the BOOT.bin. When I power the ZEDBOARD, it boots and prints the ''Hello" but nothing else. when debugging, I noticed it stuck at line 168 [ret = adrv9002_setup(&phy, adrv9002_init_get());].
BTW: as shown in the picture, I am still getting lots of warnings and some related to SPI...why all these warnings?!?!
while debugging, I noticed that the GPIO offset was set to 78 for the ZYNQ. I am familiar with the 7Z035 and it was 54. When I changed it to 54, the system worked!
Even though this solved the issue, I am kind of frustrated if this is a BUG...how come it made it to git!!!!