Hello,
I have a Crosscore project which is running fine in the debugger. How can I program the code in the BF512? I would like to let the BF512 run stand-alone, without debugger.
In VisualDSP++ I used the Flash Programmer tool. Load the driver and programmed the ldr file. Is there a manual how to do that in CCES? I found something in the help of CCES about clpd command's but I haven't it working.
Your help will be appreciated.
Best regards,
Jeroen
Hi Craig,
Thank you for your reply.
Here is the information about the elfloader.exe:
VisualDSP++:
"C:\Program Files (x86)\Analog Devices\VisualDSP 5.0\elfloader.exe" .\Release\MyProject.dxe -b SPI -f HEX -Width 8 -v -init C:\Projects\VisualDSP\MyProject\InternalSPI\Debug\BF518FEzFlashDriver_SST25WF040.dxe -o .\Release\ MyProject.ldr -No2Kernel -si-revision 0.2 -proc ADSP-BF512
CCES:
elfloader.exe -v -proc ADSP-BF512 -si-revision 0.2 -b spimaster -f hex -width 8 -init C:/Projects/CrossCore/MyProject2/Driver/CCES_driver.dxe -o MyProject2.ldr MyProject2.dxe
The 'driver.dxe' - is an Initialization file (.dxe) which is selected by the loader options. And yes I have converted the file using the elf2elf utility.
I have the code of the driver in VisualDSP++ but that project is not yet converted to a CCES project. That's the reason why I used the elf2elf utility.
I created a new launch configuration as you had described. I have started that configuration a few times and I saw the PC at address: 0xFFA11B32 or address close to it. When I look at the memory map I see that the addresses are in the MEM_L1_CODE_CACHE. But the memory map is showing that all words are unused.
When I look at the disassembly when the launch is started it seems that there is code in the MEM_L1_CODE_CACHE:
Is that normal or should there be no code?
When I try to load the CCES driver (The driver which is generated by the elf2elf converter of the driver of VisualDSP++) in the VisualDSP++ Flash programming tool it gives the following error:
Driver Error: Unable to allocate storage for the buffer
Error: Driver load failed.
Is it possible to load an CCES driver in the VisualDSP++ flash programmer? or is the elf2elf utility not working fine? because the VisualDSP++ driver gives no errors.
Best regards,
Jeroen
Hi Craig,
Thank you for your reply.
Here is the information about the elfloader.exe:
VisualDSP++:
"C:\Program Files (x86)\Analog Devices\VisualDSP 5.0\elfloader.exe" .\Release\MyProject.dxe -b SPI -f HEX -Width 8 -v -init C:\Projects\VisualDSP\MyProject\InternalSPI\Debug\BF518FEzFlashDriver_SST25WF040.dxe -o .\Release\ MyProject.ldr -No2Kernel -si-revision 0.2 -proc ADSP-BF512
CCES:
elfloader.exe -v -proc ADSP-BF512 -si-revision 0.2 -b spimaster -f hex -width 8 -init C:/Projects/CrossCore/MyProject2/Driver/CCES_driver.dxe -o MyProject2.ldr MyProject2.dxe
The 'driver.dxe' - is an Initialization file (.dxe) which is selected by the loader options. And yes I have converted the file using the elf2elf utility.
I have the code of the driver in VisualDSP++ but that project is not yet converted to a CCES project. That's the reason why I used the elf2elf utility.
I created a new launch configuration as you had described. I have started that configuration a few times and I saw the PC at address: 0xFFA11B32 or address close to it. When I look at the memory map I see that the addresses are in the MEM_L1_CODE_CACHE. But the memory map is showing that all words are unused.
When I look at the disassembly when the launch is started it seems that there is code in the MEM_L1_CODE_CACHE:
Is that normal or should there be no code?
When I try to load the CCES driver (The driver which is generated by the elf2elf converter of the driver of VisualDSP++) in the VisualDSP++ Flash programming tool it gives the following error:
Driver Error: Unable to allocate storage for the buffer
Error: Driver load failed.
Is it possible to load an CCES driver in the VisualDSP++ flash programmer? or is the elf2elf utility not working fine? because the VisualDSP++ driver gives no errors.
Best regards,
Jeroen
