Issue in Flashing(burning) the External Flash of DSK5510A using Flashburn

Hi,

Team is working on and we will get back to you as soon as possible.

Thanks & regards,

Sivaraj K

This might be caused by the mismatch between output format defined as ASCII while the boot table file prefix is hex. Please refer to TI's VC5510 bootloader application report, SPRA763C. You can access this document plus other VC5510 related documents via: http://www.ti.com/product/TMS320VC5510A/technicaldocuments

Hope this help.

Hello Sir,

Thank you for your response. I'll refer the documents you suggested.

 The issue is we are able to run the code but every time when we turn off the board and restart we need to run the code again that means its not flashing (volatile memory).we need the code to be in external flash(non-volatile memory) so that even when we turn off the board and restart it the code should start running. That's  what we are looking for.

Thank you.

Ok. Your previous issue was not able to program the flash memory, Has this been resolved? If Flashburn ran successfully, it should have programmed the code into falsh and be loaded after powered up. What steps have you taken to program the flash?

Regards.

Hello Sir,

We are still not able to program the flash memory (non volatile memory) using the Flashburn utility.

We are just free running the code using the CCS V3.3 which means the program is residing in SRAM (volatile memory). The steps for programming using CCS V3.3:

1) Debug  -> Connect.

we are connecting to Emulator(XDS510 USB).

2) File -> Load program.

we are loading the .out file.

3) Debug -> Free Running .

We are free running the code and observing the output.

But when we turn off or reset the board, we need to program it again as the steps mentioned above. That means the code is residing in volatile memory and not in Flash memory(non volatile memory).

As far as Flashburn utility we are stuck at the same point as i mentioned in my first post.

What you described using CCS is correct. You have to reload every time.

Have you tried changing the file prefix as I replied previously? Recommend to focus on getting Flashburn to work.

Good luck.

Hello sir,

We have succeeded in programming into  external Flash memory using FlashBurn 4.5v .

We shifted to CCS V5.3 from CCSv3.3

Created Target configuration (.ccxml) file  for XDS100v2 emulator, DSK5510A using CCSV5.3

Using Flashburn 4.5 we connected to the DSK5510 board and programmed the .hex file which we had created earlier into External Flash memory.

but the Issue now is its not booting from External Flash.we have set the boot mode command for booting  from External flash through EMIF that is 1011(Parallel EMIF boot 16-bit external asynchronous memory)

What might be the issue?

could u please give any suggestion.

Thank you.

Recommended debug steps:

1. Does your application code run correctly in CCS mode?

2. What revision of hex55 is used? It needs to be 2.10 and later.

3. What hex55 command options used to convert your .hex file? Be sure it is 16 bits are you expected.

4. Have you tried other output formats, like .bin?

5. Have you scope probed IO4 to monitor the boot process?

Good luck.

Hello sir,

We wanted to verify whether code is flashing into external flash. So we programmed an example LED blink code for DSK5510 board using Flashburn4.5, but the LED didn't blink, which proved that its not flashing.

We programmed the same LED code using CCSV5.3 and observed the LED blinking.

could you please help us in resolving this issue.

Thank You

Ok. You have confirmed #1. How about the rest of steps?

Hello Sir,

We tried your debugging steps:

1)The application code works perfectly in CCS mode.

2)We tried using hex55.exe (v3.3.2 & v4.4.1).

3)hex55 command options used to convert .out file to .hex file.
 (below contents were present in .cmd file):

tmsc55xx.out           /* Input COFF file */
-m2                        /* Select Motorola-S1 */
-boot                      /* Place all initialized sections in image */
-map tmsc55xx.map      /* Name hex utility map file */
-parallel16                /* Set Flash system memory width */
-v5510:2                   /* Set processor type */
-o tmsc55xx.hex        /* Name hex output file */

ROMS
{
    PAGE 0 : FLASH : o=0x400000, l=0x80000
}

4)We tried following output formats:

    -a ascii format
    -m2 Motorola format
    -i intel format
    above hex files got burned using Flash Burn utility.
    
    -b binary format(we got error using -parallel16 so -parallel8 was used to create .bin file)
    FlashBurn couldn't read binary format file.
    
5)IO4 pin was not available for probing as our custom board didn't have a test point for it.
    Its routed internally in the PCB board.

What might the issue?
Is it something to do with .cmd file or .gel file?

Please give us some suggestions,

Thank you

Hello Sir,

We made it to work.

The issue was the boot mode settings.

BOOTM[3:0] pins were set to 1011b for 16-bit external memory.

Thank you for your help