LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ADSP-BF548 EZ Kit Lite Flash Programming

I am using ADSP-BF548 EZ Kit Lite and NI Embedded Module for blackfin Processor (Labview 8.5 and VisualDSP++ 5.0).
I wanted to create a program and put it in the flash memory of the kit so that I could operate it as a stand alone.
 
So I modified the example on "C:\Program Files\National Instruments\LabVIEW 8.5\examples\lvemb\Blackfin\BF548\BF548 Keypad 2"
by making the LED turn on on different column presses on the keypad. When I was done I compiled it (build) using release mode then
loaded (LOAD PROGRAM) the DXE file to the VisualDSP++ environment. Then I check on the forum thread titled
 
"Programming the Flash Memory of the ADSP-BF537 EZ-KIT Lite" for the steps and found out there were differences in the directories and filenames so I just searched the files closest and seem most appropriate for the job :
 
*For the flash driver I loaded :
 
"C:\Program Files\Analog Devices\VisualDSP 5.0\Blackfin\Examples\ADSP-BF548 EZ-KIT Lite\Flash Programmer\Burst\BF548EzFlashDriver_PC28f128.dxe"
 
*For the Init File I used "ezkitBF548_initcode.dxe"
 
*S.I. Revision is 0.0
 
*Processor is ADSP-BF548
 
 
The command line is as written below :
 
 
elfloader "C:\Ronan\Blackfin-Labview\BF548 Keypad 2\BF548 Keypad2\BF548\VDK_Application\BF548 Keypad2.dxe" -b flash -f hex -Width 16 -init "ezkitBF548_initcode.dxe" -o "C:\Ronan\Blackfin-Labview\BF548 Keypad 2\BF548 Keypad2\BF548\VDK_Application\BF548 Keypad2.ldr" -si-revision 0.0 -proc ADSP-BF548
 
 
After I generated the ldr file I opened the flash programmer and loaded the flash driver. Then I selected the generated ldr file for the "Data File" field and programmed the device with the default "programming" tab options.
 
Default options where :
1. Pre-program erase options = Erase Affected.
2. File Format = Intel Hex
 
The programming went thru successfully and the previous program in the flash was obviously erased but the new program did not operate.
*Note : I debugged the new program in both Labview and VisualDSP++ and it works perfectly.
*Note : I use EZ lite USB Debug Agent port.
 
It seems the flash was erased but the program was not loaded from flash. I tried to "Compare" the data but my PC just hangs.
I attached all of the code (zip file) and the other files (drivers) are just located on the installation directory of VisualDSP++
 
Thanks for the help!!!
0 Kudos
Message 1 of 10
(7,234 Views)
Hi Ronnier,
 
It looks like you've taken all the right steps to flash the ADSP-BF548 EZ Kit Lite . I would suggest trying out one of the VisualDSP++ examples which come along with the program. For example, try flashing the keypad example available at \Program Files\Analog Devices\VisualDSP 5.0\Blackfin\Examples\ADSP-BF548 EZ-KIT Lite\Drivers\Keypad\. Build the project and see if the keypad works properly. The Readme_KeypadExample.txt explains how the example should function. Hope this helps.
0 Kudos
Message 2 of 10
(7,201 Views)
hi everyone!
i have ADSP BF537 EZ kit lite and using labview embedded module for programming
i want to program in flash ROM but i can not create ldr file .
i have read this post and i can not understand.
elfloader "C:\Ronan\Blackfin-Labview\BF548 Keypad 2\BF548 Keypad2\BF548\VDK_Application\BF548 Keypad2.dxe" -b flash -f hex -Width 16 -init "ezkitBF548_initcode.dxe" -o "C:\Ronan\Blackfin-Labview\BF548 Keypad 2\BF548 Keypad2\BF548\VDK_Application\BF548 Keypad2.ldr" -si-revision 0.0 -proc ADSP-BF548.
i have opened elfloader utility from C:/program files/Analog devices/VisualDSP5.0 but just one blink and finished!
could any body help me how to create ldr file from dxe file?
0 Kudos
Message 3 of 10
(6,971 Views)
Hi Seoul,
 
The following KnowledgeBase has more information on how to program the Flash Memory of the ADSP-BF537 EZ-KIT Lite. Hope this helps.
[article no longer available]
 
 
 
 
0 Kudos
Message 4 of 10
(6,947 Views)
Hello everybody,

I just started programming BlackFin DSPs with LabView this morning. I am currently trying to create code in LabView which I then want to program onto the EZ-Kit lite BF537 board to run "stand-alone" (with the BF-537-board not beeing connected to LabView).

What I did:
1) Created the code in LabView which then generated me a MyCode.dxe file
2) I used the elfloader to create a MyCode.ldr file from the previous .dxe file (as described here: http://digital.ni.com/public.nsf/websearch/5E2460ECF2A76D3386257169007B7C28?OpenDocument )
3) I wanted to copy this MyCode.ldr file onto the BF-537-board using the Flash-Programmer included in the VisualDSP++ IDE (as also described in the above knowledgebase article)

Here is my proble:
When I want to select the driver-file in the Flash-Programmers window it just throws me an error.

The driver file I selected is: C:\program files\Analog Devices\VisualDSP 5.0\Blackfin\Examples\ADSP-BF537 EZ-Kit Lite\Flash Programmer\BF537EzFlashDriver.dxe
The returned error is: Error: Could not allocate storage for the buffer. Error: Driver load failed.

I have not created any projects in the VisualDSP++ IDE nor have I opened anything else etc...

What can I do?
Is there another way to generate stand-alone code for the BF-537 EZ-kit lite from LabView?

Sincerely,
Alex Bürgel
0 Kudos
Message 5 of 10
(6,859 Views)
Hi Alex,

Thanks for posting to the NI Discussion Forum.

There is no other way to generate stand-alone code for the BF-537 EZ-Kit Lite. We link to Analog Device's VDSP++ tool chain so when you want to program the flash, you must go through the steps outlined in the KB you linked.

I did find some information on the error you reported. From the VisualDSP++ 5.0 Help for Blackfin Processors:
"Could not allocate storage for the buffer.

When doing a malloc for AFP_Buffer, if there is not enough memory allocated for the heap in the .LDF file used by the Flash Programmer driver, this error is generated. For example, if the heap is defined to be a size of 0x1000 bytes and we try to malloc 0x2000 bytes, a failure occurs and this message appears. If you are not using the heap for anything else, you can speed up the time to program a file to flash by maximizing the number of bytes that you malloc."

At what step in the KB instructions did you run into the error? It sounds like you are running into this error at step 3 and 4. Are you receiving this error after selecting your data file and clicking Program? I haven't been able to reproduce the error. Make sure the title bar of the VDSP++ 5.0 says "Target: ADSP-BF537 EZ-KIT Lite via Debug Agent". If you are still experiencing problems, you may want to call into support. Thanks Alex and have a great one!
0 Kudos
Message 6 of 10
(6,808 Views)
Hi Mike,

thank you for your efforts. Good to hear that there is someone who wants to help.
You are right, I encounter the error after clicking the "load driver"-button in the FlashProgrammer.

And this is what I do not understand: Up to this point (selecting the driver) as far as I can see there was nothing that I could have done wrong myself so it seems to be a general error in my VDSP++ installation?!

Hope this information helps you somehow.
Have a nice day, too.

Alex
0 Kudos
Message 7 of 10
(6,801 Views)

Hi Alex,

There are three steps we can try out.

1) Something went wrong when VDSP++ was installed, hence reinstallation should solve it

2) The second option is to send a mail to support@ni.com referring to this post and we can send you another copy of the BF537EzFlashDriver.dxe file to test with.

3) Getting in touch with Analog Devices to see if they have come across this issue.



Message Edited by Nitin T on 05-14-2008 10:52 AM

Message Edited by Nitin T on 05-14-2008 10:54 AM
Message 8 of 10
(6,764 Views)
Hello Nitin T,

thank you for your help. The problem is solved now and (as in 99% of all cases) it was a user-mistake. VDSP++ was set to Blackfin Simulator instead of being set to an existing Blackfin processor.

So the knowledgebase article is 100% correct.
Thanks a lot,
sincerely
Alex
0 Kudos
Message 9 of 10
(6,688 Views)

There's an explaination of this problem on the Analog Devices website:

http://www.analog.com/processors/cda/epTASearchResult/#35129+207

If the SCLK is set too low at start up the external DDR memory can't be accessed.

I modified the ezkitBF548_initcode.dxe so that the SCLK is set to 133 MHz instead of 50 Mhz.  Try building your .ldr file using the attached ezkitBF548_initcode.dxe.

Matt

 

0 Kudos
Message 10 of 10
(6,623 Views)