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.

TMS320F280039C: Flash API issue

Part Number: TMS320F280039C

My customer is porting a code from F280049 to F280039 due to shortage and recently they meet a strange issue.

It is found in fab that some F280039 can not jump to app after programing by bootloader. And I have customer to do below test:
1.They test the XRSn pin and know the F280039 is reset.
2. After that, they connect F280039 to CCS and found a flag which should be changed in app code is not changed, that caused logic error so the F280039 reset and always meet the same issue, so the phenomenon they see is XRSn has low pulse.
3.They found the Flash API they used for Bootloader and App is not same, Bootloader use right F280039 flash API, but App use the wrong F280049 Flash API.
4.After they change to right flash API, the issue is fixed.
But the fact is they program 500 F280039 but only 5 F280039 report the issue, they really want to know why some F280039 can manipulate the flash normally using F280049 API. They also read the flash of the F280039 which work normally from the beginning and the flag is indeed changed. And they only use BANK0 and BANK1 on F280039.

BR

Emma

  • Hello Emma,

    The F28003x and F28004x devices share the same flash controller, but there are some small differences in the flash bank designs. This likely explains why you had many units program successfully but a few failed. Due to these variations, the correct Flash API for the device should always be used to avoid edge cases like this.

    Best regards,
    Ibukun