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.

TMS320F280038-Q1: Customer board can't be programmed by UniFlash tool

Part Number: TMS320F280038-Q1
Other Parts Discussed in Thread: UNIFLASH

Hi BU experts and Tool experts, 

In customer site, encountering a wired situation: 

          The customer board F280038 can be programmed by CCS but can not be by UniFlash (the debugger is XDS110, and the connection is cJTAG 2-pin. And in UniFlash, we used the same ccxml file for CCS). 

          The F280039C LaunchPad can be programmed both by CCS and UniFlash. 

          And with UniFlash tool, the customer board can not read the memory in first time try but should try twice to read the memory successfully. 

          No matter the F280038 device is powered by probe or the board, customer board F280038 can't be programmed. 

          And if using UniFlash downloads a RAM image into the device, the progress will stop at "set the PC to entry point". 

          With CCS, the gel file's OnTargetConnection() will stall forever. From debug, if we remove the memory initialization codes in the OnTargetConnection(), this process can be finished. 

Please help check the above phenomenon and give your comments. And I have following questions: 

1). What is the difference between CCS and UniFlash Flash programming kernel? 

2). Any hardware design should be noticed for using UniFlash Flash programming? 

3). The debugger firmware should update to support UniFlash tools? 

4). Why the memory initialization of OnTargetConnection() can't be finished on customer board? 

Regards, 

Will 

  • Hi Will,

    1) For this device, there should not be any difference in the kernel between CCS and Uniflash.

    2) As long as the voltage lines are within the datasheet's operating spec, it should be fine.

    3) What are the versions of CCS and Uniflash used by the customer?

    4) Where is the control stuck in the OnTargetConnection()?

    Regarding RAM load:  Uniflash and CCS flash plugin are developed to load the image to the flash memory only.  Hence, the executable should be a fully embedded flash image.  RAM loads are not guaranteed.  If anything needs to be mapped to RAM, it should be loaded to flash and later copied to RAM at runtime.

    Question 1: What error do they get when Uniflash failed to load?

    Question 2: I don't see any proprietary information in this post.  Can this be moved to the external forum?

    Thanks and regards,
    Vamsi

      

  • Hi Vamsi, 

    3) What are the versions of CCS and Uniflash used by the customer?

    CCS version is 11.1.0 and Uniflash version is 8.2.0. 

    4) Where is the control stuck in the OnTargetConnection()?

    From my test, it stuck in the memory initialization part: 

    Regarding RAM load:  Uniflash and CCS flash plugin are developed to load the image to the flash memory only. 

    Ok, understood. 

    Question 1: What error do they get when Uniflash failed to load?

    The data verification error. 

    Question 2: I don't see any proprietary information in this post.  Can this be moved to the external forum?

    I can only choose internal forum for F28003x device, I don't know why...

    Best Regards, 

    Will 

  • Will,

    Can you send the exact data verification error that you got?

    Also, I will ask our RAM expert to take a look at why the RAM INIT in gel file is causing the problem for you.  Once the RAM expert clarifies your gel concern, they will assign it back to me as needed.

    Can I move this post to external forum?

    Thanks and regards,
    Vamsi

  • Hello Will,

    Does the customer stall on every RAM initialization while loop if they only uncomment one at a time?

    Best regards,

    Omer Amir

  • Hi Omer, 

    They did not try every RAM initialization loop, I will let them try it. 

    Best Regards, 

    Will