This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Flash470 v3.42 Error 199 - Unable to connect to target on port address 0x510.

Other Parts Discussed in Thread: TMS570LC4357, UNIFLASH, TMS570LS3137

Hello forum team,

I have a problem with the tool Flash470.

I test our start up code TMS570LC4357 with CCS5.5.0.00077 and Flash470 v3.42.

I could run the test with CCS. After I have changed the start up code, I can no more flash the new code with Flash 470. I got "Error 199 - Unable to connect to target on port address 0x510."

If I test with another ECU, I can run the debugger. So I can be sure the JTAG connect etc. works well.

Below is the screen shot of Flash470:

 

 

Afer lauching the configuration, if I try to connect to the target, I see the following error:

 

If I run Test Connection, I see the following error:

I have had such problem a few times. So far we can solve this problem as follows: Flash the same ECU with a old working start up code  using Lauderbach debugger. Now I can flash the device with Flash470. Usually to avoid the same problem, I can add an endless loop at the beginning of the start up code (add "S B S" as the first instruction in cint_00.asm), and then flash the changed start up code (instead of that code which caused the problem) with Flash470.  It seems that if the start up code has an endless loop which reset the CPU permanently (something like reset --- start up --- ...--- some error triggers a reset ), then we can't flash it with Flash470. With the added endless loop (S B S), I can prevent the endless  reset, and such I can flash the new code. After I corrected the error which causes the endless reset, I can remove "S B S" and flash the code with Flash 470.

But this solution is too complicated and costs time. During development, I am not sure if the new code will trigger an endless reset. If it does, then I have the flash problem again. If I add the "S B S" code to cint_00.asm, the debug session becomes completed because there are many fail safe safety self tests which cause reset (LBIST etc). 

I wonder if you have seen this problem, and if you can provide some simple solution.

Thank you!

Best regards,

Libo

 

 

 

 

 

 

 

 

 

 

  • Hi Libo,

    Neither Flash470 nor the XDS510 USB are supported for the LC4357.   The replacement for Flash470 is http://www.ti.com/tool/uniflash and the suggested emulators are listed in the product folder http://www.ti.com/lsds/ti/microcontrollers_16-bit_32-bit/c2000_performance/safety/tms570/tools_software.page#software.

  • Hi Anthony,

    thanks for the quick answer. We use Flash470 and XDS510 for TMS570LS1213, TMS570LS3137, TMS570LC4357. We have the same problem with LS1213 and LS3137 too. Could you please check if there is a solution for LS1213 and LS3137?

    Thanks and regards,

    Libo

  • Hi Libo,

    Yes this is the case across all of the 570 products now.   The flash programming solution is Uniflash and the supported emulators are the XDS100v2, XDS200, and XDS560v2 class.   The older emulators like the 510 may or may not work but the 510 USB for example has stopped receiving driver updates for about 2 yrs now so it's going to start to give more and more trouble.  

    If you can't switch over to Uniflash then we will need to get someone who is dedicated to supporting your company in the loop for help w. Flash470.   Do you have a contact for direct support?  If not if you let me know your site I can work on finding out who the right person would be.

  • Hi Anthony,

    thanks for the update. Yes, I know the local support. I will see if we can get help from them. I will close this thread. Thank you!

    Regards,

    Libo