Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hi,
I am developing programming of two core chip TMS320F28379D for mass production purpose.
I had some unpleasent experience with DSLite and the command line environment generated from UniFlash.
The most painfull was when programming broke in the middle of programming flash or OTP memory leaving the device in strange state.
Generally it was possible to correct the state in CSS but it is time consuming. The percentage of incorrect programmed devices is significant.
That is why I decided to switch to DSS (Debug Server Scripting).
I already modified provided example called loadti (written in JavaScript) and succesfully programmed flash in both cores (so far without OTP).
I have some questions to DSS:
- How can I check and print progress of programming when I call debugSession.memory.loadProgram()?
I found that there is no way to do that: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/725300/ccs-how-to-access-the-debug-server-scripting-loadprogram-progress
but DSLite and CCS are doing that. - Why I get exception when I am trying to get checksums of memories? I tried debugSession.flash.getFlashChecksum() as well calculateChecksum().
Log is below:+++Calculate checksum... getFlashChecksum: ENTRY waitUntil: ENTRY timeout: infinite C28xx_CPU1: Calculating Checksum... C28xx_CPU1: Main Flash Checksum: 0x8774 C28xx_CPU1: Main ECC Checksum: 0x2121 C28xx_CPU1: OTP Checksum: 0xFC00 C28xx_CPU1: OTP ECC Checksum: 0xFF80 waitUntil: RETURN waitUntil: ENTRY timeout: infinite waitUntil: RETURN SEVERE: Error getting data associated with "FLASHCHECKSUM": Unknown key Error code #4020, could reset target!
-
Is there any specific sequence or requirements for working with OTP in DSS?
Kind regards,
Piotr Romaniuk