TMS320F2800156-Q1: unifalsh

Hello,

Did you try unlocking the device first? I see the error warnings for Zone 1 and Zone 2 unlock.

Thanks and regards,

Charles

hi

this happened in  a new chip(empty chip).

Try again, and you can successfully program it.

Hi Youjun,

Did these warnings appear immediately after first connection? If you were able to try again and program on a second attempt.

Thanks,

Charles

Youjun,

Can you try disabling the Run Action?

hi

Try again, and I can successfully program it.

sometimes.i try many times,and I can successfully program it.

hi 

I can give it a try.

hi

After trying, there was no effec.

If you try flashing with CCS, does the same issue occur? Or only with UniFlash?

hi

We didn't use CCS because we are mass producing and the CCS configuration is actually the same as Uniflash,may be have the same issue.

Would it be possible to try with the latest CCS version? This will help us investigate the issue.

hi

sorry，due to being a mass-produced product, it is not convenient to use CCS for program.

youjun zhang said:

due to being a mass-produced product, it is not convenient to use CCS for program.

I was asking if someone can flash with CCS as a quick test just to see if the same issue happens there. 

Would it be possible to share the hex file also? You can provide using private E2E message.

hi

It doesn't happen every time, it just happens occasionally

How frequent does it occur? Out of 100 tries, how many times would it occur on average?

These occasional issues are very difficult to debug.

hi

uncertainty，maybe 10 times.

Sporadic errors are difficult to diagnose. They are usually due to some instability with the environment.

All I can provide is what your errors mean. 

Error -1066: the debugger was unable to set a software breakpoint. Typically this is because the memory region it tried to set it on is not writable memory. However, it tried to set it first on address 0x8058 and then with address 0x8154 which I believe are both RAM. So something is wrong with the device state where this memory is not writable for the debugger. 

The next series of errors look like issues with device configuration issues where some algorithm is unable to execute - perhaps the flash algorithm? Then there various memory write errors and more breakpoint errors.

Perhaps the main question is why the device failed to unlock. I assume when you try again and it works, there are no issues unlocking the device.