TMS570LC4357-EP: Created a bin file for eeprom programming

Hi LayEng,

LayEng Chan said:

1. I am still trying to get the scireg4 working on my hardware. I think it is more our hardware than your software advice. As a result, I have not closed the case in the other thread. I also would like to view all the threads created by me. Hope you can show me how.

I guess you already solved this, because you mentioned in other thread.

LayEng Chan said:

2. I would like to create a bin file for the eeprom programming and I would like to download in a similar manner as the program bin file using uart. Can you tell me the tools to create the bin file?  I am looking at programming the different block numbers of the eeprom. Eg:

You already knew how to create a binary file from CCS right?

We can create it by adding below command in post build steps. For more details refer the FAQ.

"${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/armofd" "${CG_TOOL_ROOT}/bin/armhex" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

(+) [FAQ] TMS570LC4357: Step by step procedure to execute UART Bootloader on TMS570LC4357 - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

Now i would like to suggest you create one application program and there you can create two array blocks with the required data. And now in the main function of this application program you can write a code to program this array blocks into the EEPROM.

Now generate the bin file for this application program and you can send this application program to the bootloader as we discussed in above FAQ. Once you send this application binary to the bootloader then bootloader calls the application and application will program the EEPROM.

--
Thanks & regards,
Jagadish.

Dear Jagadish

Thank you for your reply. What you have suggested is an option. But I wasn't looking at that kind of implementation. I was thinking of creating a bin file directly as opposed to getting it created using the post build steps

"${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/armofd" "${CG_TOOL_ROOT}/bin/armhex" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

I will then download this bin file using the bootloader and flash it in eeprom using the fee api in bootloader application. If you have any info with this kind of implementation, do let me know. Thank you

Hi LayEng,

1. First time, you have to use the FEE driver to program the data array to EEPROM.

2. If the configuration data or calibration data have been written to EEPROM, you can dump the EEPROM content to a binary file. The binary file can be loaded to EEPROM through CCS or Uniflash.

Dear QJ

Thank you for your reply. How do you dump the eeprom contents to a bin file? Looking forward to your reply. Thank you

Dear QJ

I have a problem in another thread which I would like to consult you. I have asked Jagadish earlier. I am using a sample uart bootloader to flash my application program. After successfully flashing, the program jumps to the application but my application doesn't work. What can be wrong? In another thread, the forum member say the application needs a reset. I am not sure if the reset is referring to bootloader reset or flashed application reset. I have reset the mcu using hard mcu reset and it always runs from the bootloader and jump to the application. But application doesn't work.  Looking forward to your reply. Thank you

Dear QJ

I have read in online forum that dumping eeprom to bin file is using memory browser and saving to memory. If that is the case, please define what kind of bin file I should use and the memory locations to dump. Thank you

LayEng Chan said:

If that is the case, please define what kind of bin file I should use and the memory locations to dump

You can use binary, COEF, or hex format. The Uniflash supports those format.

LayEng Chan said:

I have a problem in another thread which I would like to consult you

Can I have the link to this thread?