Hi, I am testing with BF533 EZ Lite Kit and i have an issue as below:
- After finishing building my source code, i debug it on my Kit with CCES. My code run OK. But when i turn off my Kit and turn on it again, the Kit will be empty and i have to load my code again. As my understanding, my .dxe file only be loaded to RAM and it will be lost when i turn off Kit. So i want to load my .dxe file to ROM of Kit and when i restarted Kit, the default program will be my source code. But i do now know how to do it. Could you help me to resolve this issue ?
In order to load your code into target, you have to create an .ldr file. To do that, go to Project properties > C/C++ Build > Settings > Build Artifact.Now select, artifact type as "Loader file" and click "Apply".
Now build the project and verify that the *.ldr has created inside of debug folder.
The available utility to flash the LDR into target using CCES is the Command Line Device Programmer(CLDP). You can use this command line utility without opening CCES.
You can get more details about CLDP in the below CCES help paths.CrossCore® Embedded Studio x.x.x > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > About the Device ProgrammerCrossCore® Embedded Studio x.x.x > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > Device Programmer Command Line > Device Programmer Command-Line Switches
Please refer the below FAQ to program flash into target board.FAQ: How do I program flash on my target board using CrossCore Embedded Studio?ez.analog.com/.../faq-how-do-i-program-flash-on-my-target-board-using-crosscore-embedded-studio
For details, You can install ADSP-BF609 BSP and refer the chapter "5. Using Loader Files" in the Read me file of the Power On Self Test BSP example from the below path about create a loader file and program the LDR image to flash:<installation path>\Analog Devices\ADSP-BF609_Evaluation_Board-Rel1.1.0\BF609_EZ-Board\Blackfin\Examples\Power_On_Self_Test\readme.html
Please use the below link to download Board Support Package of BF609.download.analog.com/.../ADI_ADSP-BF609_Evaluation_Board-Rel1.1.0.exe
Booting the EZ-KIT from Flash MemoryConfigure the ‘Boot Mode’ Switch on your EZ-KIT to boot from flash memory.
Refer to the "Boot Mode Switch" chapter in below linked Evaluation System Manual for details on correctly setting the 'Boot Mode'.www.analog.com/.../ADSP-BF533_ezkit_man_rev.3.2.pdf
Once the appropriate Boot Mode is set simply reset your board to boot the code from flash.
Thank you for your support.
As my understanding, the *.ldr file will be writen to flash Plash PSD4256G6V TQFP80 chip on BF533 Ez Lite Kit board, but there are two flashs: flash A and flash B. So which flash will be writen ?
Beside, i am using Visual Dsp++ too. Could you show me how to program my code to flash using Visual Dsp++ ?
And i have two more questions about BF533 Ez Lite Kit board:
First, i see there is a FlashLINK JTAG HEADER on my BF533 Ez Lite Kit board. But I don't know what this JTAG is for ?
Second, i am now connect my computer to the board by using USB port on the Kit and debug my code over usb port. And i have not test with JTAG port on the board. Coud you recommend me some JTAG device, which i can use to debug the BF533 Ez Lite Kit board using USB 2.0 port ?
Hi,We recommend you to go though the debugging steps in the below linked FAQ which might helps you.ez.analog.com/.../faq-what-is-the-cause-of-a-core-fault-detected-before-halt-at-address-error-messageRegards,Nishanthi.V
Hi Nishanthi.V, i have one more question with JTAG pin:
On the board ADSP BF533 EZ Lite Kit, there are two JTAG header, one is the DSP JTAG HEADER (ZP4) which connects to Jtag module of chip ADSP BF533, the other is Flash link Jtag header (P1), with using ADZS-ICE-2000 Emulators, which JTAG pin should i connect to ?
Could you explain me some basic about Flash link Jtag header ?
Hi,The JTAG header is the connecting point for a JTAG in-circuit emulator pod. When an emulators(ICE-1000 or 2000 etc.,) is connected to the JTAG header, the USB debug interface is disabled.If you want to connect ICE-1000 or ICE-2000,etc., you have to use ZP4 JTAG header.The PSD4256G6V flash can be re-programmed using the FlashLINK JTAG programming cable available from STMicoreclectronics (www.st.com/psd)The FlashLINK connector allows you to configure and program the STMicroelectronics DSM2150 flash/PLD chip.Could you please refer "Configuring Flash Memory" chapter in the below linked evaluation manual.www.analog.com/.../402257434ADSP_BF533_EZ_KIT_Lite_Manual_Rev._1_3.pdfRegards,Nishanthi.V
Hi Nishanthi, as my understanding, the code i load to EZ-Kit Lite BF533 will be stored on the flash A and B. And i can load code directly to flash A and B by using FlashLINK JTAG.
So it mean i have three methods to load my code to flash:
1. Using JTAG header of DSP whit ICE 1000 or 2000. In this method, my .ldr will be loaded to DSP Ram and then go to the flash or it will be load directly to flash ?
2. Using USB cable, which is attached with the Ez-Kit Lite BF533. In this method, my .ldr file will be loaded to chip BF535P and then loaded to BF533 RAM and then "go to" flash ? I am not sure about "mechanism" of how the .ldr file "go to" flash. If could please explain me how it work ?
3. Using flahsLink Jtag of STMicroelectronics. In this method, my code .ldr file will "go" directly to flash ?
And i have one more questions as below:
4. In my development board, can i use another flash ? And what i have to change if i use an another flash to replace PSD4256G6V ? (Some thing like project setting on CCES or build setting or buikd artifact or driver file... )
5. When i load the code to flash psd4256g6v on the EZ-Kit Lite BF533, by using cldp of CCES, i have used the comand:
cldp -proc ADSP-BF533 -emu usb -driver "C:\Analog Devices\ADSP-BF533_EZKIT-Rel1.0.1\BF533_EZ-Kit_Lite\Blackfin\Examples\Device_Programmer\parallel\bf533_psd4256g6v_dpia.dxe" -cmd prog -erase affected -format hex -file "C:\Users\Dicom\cces\2.9.1\test4\Debug\test4.ldr"
Is the "C:\Analog Devices\ADSP-BF533_EZKIT-Rel1.0.1\BF533_EZ-Kit_Lite\Blackfin\Examples\Device_Programmer\parallel\bf533_psd4256g6v_dpia.dxe" is driver file of psd4256g6v for bf533 ?
Hi,If you have placed any other flash part in your custom board, you have to modify the flash driver according to your flash part.We would recommend that you to take one of our current drivers (bf533_psd4256g6v_dpia.dxe) as a base for creating a driver, which will be compatible with your flash part.The flash drivers we ship with our tools are specific to our EZ-Kit boards. For example, the bf533_psd4256g6v_dpia.dxe driver is specific to the BF533 EZ-KIT.We provide documentation for the Device Programmer API, which describes the commands the Flash Programmer Drivers require to perform the Flash accesses. Following the API, it's relatively simple to port an existing Flash Programmer Driver to match your specific flash part.When modifying a driver we would recommend referring to both the custom flash part data sheet and the data sheet for the original device when doing so, so that you can verify elements such as number and size of sectors, reset commands, Manufacturer and Device codes, then see how these differ in the data sheet for your custom flash device. The examples/drivers are well documented/commented so you should be able to determine where changes are required to suit your target.Following the API, it's relatively simple to port an existing Flash Programmer Driver to match your specific flash part. This documentation is available atHelp > CrossCore® Embedded Studio <version> Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > Custom Device DriversWe are aware of many customers who have successfully modified our flash drivers to suit different flash parts.Also please have a look at below EE-240 application note, which describes the booting process for the ADSP-BF531, ADSP-BF532, and ADSP-BF533 Blackfin® processors which might help you.www.analog.com/.../EE-240_Rev4.pdfRegards,Nishanthi.V
I have some questions with the EBIU of BF533
Q1: Can i add an TSI (time slot interchange) MT90869 connect to BF533 via EBIU same as the flash A and B ? As my understanding, i can connect maximum 4 devices to EBIU of BF533, so with flash A, flash B and SDRAM, i will add a TSI device. This device use non-multiplexed Motorola microprocessor interface.
Q2: In the document: https://www.analog.com/media/en/dsp-documentation/processor-manuals/ADSP-BF533_hwr_rev3.6.pdf adn document: https://www.analog.com/media/en/dsp-documentation/legacy-evaluation-kit-manuals/402257434ADSP_BF533_EZ_KIT_Lite_Manual_Rev._1_3.pdf, i can not find the description about how transfer data via pin D[0:15] and A[1:19] for peripheral EBIU transfer data. Could you give an example code or a document describe about how to transfer data via pin D[0:15] and A[1:19] ?
Q3: In the document: https://www.analog.com/media/en/dsp-documentation/legacy-evaluation-kit-manuals/402257434ADSP_BF533_EZ_KIT_Lite_Manual_Rev._1_3.pdf page 2-7 and 2-8:
I know understand why the we have the address value in this table ? Could i change this by software ? If i connect a new device, what is the value of address?
Hi,Regarding Q1,>>The EBIU only supports asynchronous interfaces such as SRAM, ROM, FIFOs, flash memory, and ASIC/FPGA designs. And yes, you can connect upto 4 devices to EBIU of BF533.Regarding Q2,>>This is handled in a different thread. Please continue the discussion there to avoid duplication of efforts.ez.analog.com/.../how-bf533-interface-with-flash-psd4256g6v-on-board-ez-kit-liteRegarding Q3,These address values are specific to ADSP-BF533 EZkit. I would suggest you to refer the Application Note(EE-302 Interfacing ADSP-BF53x Blackfin® Processors to NAND FLASH Memory) for more details on this. The link for downloading the Application Note is given below.www.analog.com/.../EE-302.pdfRegards,Anand Selvaraj.