When I connect to my BF533-EZKIT from VDSP++ it does some initialization of the hardware. Is the sourcecode for this available some place?
There is a config file in the System/ArchDef folder. It is XML and you can edit it if needed. I think you want ADSP-BF533-proc.xml, but you should double check that.
Laz wrote: There is a config file in the System/ArchDef folder. It is XML and you can edit it if needed. I think you want ADSP-BF533-proc.xml, but you should double check that.
Laz is correct, when VisualDSP++ connects to a target, it configures some registers which setup external memory on the board. This is enabled by an option within the tools, under:
'Settings'->'Target Options'->'Use xml reset values'.
Enabling this option instructs the IDDE to use "register-reset-definition" values defined in an XML file within the VisualDSP++ Installation.As you are using a BF533 EZ-KIT, the IDDE will use the values located in the <register-reset-definitions> section of the file "...\System\Archdef\ADSP-BF533-proc.xml". This file defines the EBIU register settings specific to the SDRAM part used on the EZ-KIT Lite, and because these settings are specific to the SDRAM part used we only provide them in the XML files that correspond to an EZ-KIT Lite.
Thanks for the info. I'm trying to compile code for the BF533 using the GNU toolchain and have an odd problem (at least I think it's weird). I know this is not the place for support of the GNU Toolchain, but since VisualDSP++ is involved, perhaps you can help me.
I have compiled two images of a simple led blinker application. A DXE compiled with VisualDSP++, and an ELF compiled with the GNU Toolchain. Then I used GNU tools on both images to create an ldr for booting in SPI mode on our custom HW.
VisualDSP+ DXE converted to loader by GNU tools worked.
GNU ELF converted to loader by GNU tools did not work.
The odd thing, and the reason for my initial question, is that if I load the ELF to the BF533-EZKIT using VisualDSP++ it works.
I also did a more lowlevel test. Using only GNU tools I compiled a file called start.S that contained the __start symbol and the asmcode turning on the led. The loader I created worked fine. Then I tried putting the same code in a file called main.S that defined the _main symbol. Using the default startupcode from the GNU Toolchain it seems I never got to main ... except if I load my code with VisualDSP++.
I'm talking to the people at http://blackfin.uclinux.org/gf/ about it, but I thought I'd chance a question here as well in case you have complementary knowledge
As you're already talking to people on the uClinux forum we suggest you continue to work with them as ADI engineers regularly monitor and answer questions posted on that forum.
A you solve the problem?
I assume you posted here as a result of the behaviour you mentioned in your other thread: Unable to connect to ADSP-BF533
As mentioned on that thread, I believe your connection issue is license-related. If that proves to be incorrect we can continue the discussion on your other thread.
Retrieving data ...