• State
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 54 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TMS320F2800137: Device flash changed to 0

Joe Ji
Expert 3990 points

Part Number: TMS320F2800137
Other Parts Discussed in Thread: UNIFLASH

Hi Expert 

This issue is from customer's mass production project and cannot be reproduced.

Customer reports an issue that the flash data changed to 0, but there is no API changed the flash data before, below is the normal flash data and error flash data:

Normal flash data:

:201750008AA906C41E44761A064807428AA906C40F4460039A006F0328A90201FE8840006D8

:20176000FE0896472B487648191C5201600356SBF014892486017924752106012BE07B60093

:201770000205C242C3441E46FF201104764816959648520060079247764818CC6F03284852

:2017800002009248FE880006B2BDAABDA2BDFIE0882A4D1005ACB6F155CAD2901560303A1D6

:2017900007A3DC8809025CA483A9020876481880C064261068A4483467648180C5ACBD901E1

:2017A0092A254A166EAFE8882BE86BE8BBE0606FE0CA04A1E48A8462B4B1E42064676482F

:2017B00015BA520160147648189206501E42922519643834A8A4606487648135852006109D9

Error flash data:

:201750008AA906C41E44761A064807428AA906SC40F4460039A000000000000000000000A6

:20176000000000000000000000000000000099000000000000000000000000000000000000069

:2017700000000000000000000000000000009000000000000000000000000000000000000059

:2017800000000000000000000000000000000000090000000000000000000000000000000049

:2017900000000000000000000000000000009000000000000000000000000000000000000039

:2017A0000000000000000000000000000000000000000000000000000000000000000000029

:2017B000000000000000000000000000000000000000000000000000000000006F0361093D

:2017C0008A4A02001EF4284B01F46F03284B01FB924BFE8C0006FE041E422B438F0521D016 

the start flash address is: 0x08175B 

is there any possiblity that uniflash failed to program some of the flash ranges or the flash ranges are effected by some physical issues?

 

Thanks

Joe

 

 

  • 0
    TI__Expert 5265 points

    Hi Joe,

    The SME is OOO till 9 Feb 2026. Please expect a delay in response.

    Regards,
    Aswin

  • 0
    TI__Mastermind 26220 points

    Hi Joe,

    Could you please help provide some more context?

    Joe Ji said:
    This issue is from customer's mass production project and cannot be reproduced.

    What is meant by 'cannot be reproduced'? This is a singular unit exhibiting this behavior?

    Joe Ji said:
    but there is no API changed the flash data before

    When did they observe this issue? For example, did they perform an OTA operation or something where they are using Flash API or doing any kind of flash operation?

    Joe Ji said:
    is there any possiblity that uniflash failed to program some of the flash ranges or the flash ranges are effected by some physical issues?

    If there was an issue programming certain flash ranges then UNIFLASH would have thrown an error and it would most likely have been repeatable across more than just one unit.

    How long has this device been in mass production and what was the failure signature that prompted this device to be reviewed?

    Best Regards,

    Marlyn

  • 0 in reply to Marlyn Rosales Castaneda20
    TI__Expert 3990 points

    Hi Marlyn

    Nice to meet you, please see my reply:

    Could you please help provide some more context?

    --  [Joe] you need more data in flash or some other information to look into the issue?

    What is meant by 'cannot be reproduced'? This is a singular unit exhibiting this behavior?

    --  [Joe] it is the singular unit, and once this unit is reprogramed by uniflash, the issue won't appear too. So I think will the issue related to Uniflash programming?

    When did they observe this issue?

    --  [Joe] the issue is observed in a brand new device, and 1st programed by uniflash.

    If there was an issue programming certain flash ranges then UNIFLASH would have thrown an error and it would most likely have been repeatable across more than just one unit.

    -- [Joe] the uniflash v8.7 will report the issue c28xx_CPU1:GEL:Error while executing OnReset(0): identifier not found: pkgType at (pkgType&(0xFU<<0U))[F2800137.gel:766] at Device_Config()[F2800137.gel:210] at OnReset(0). But we did not captured the certain issue reported by Uniflash when program the certain piece.

    thanks

    Joe

  • 0 in reply to Joe Ji
    TI__Mastermind 26220 points

    Hi Joe,

    Likewise, thank you for providing more details. If this just happened with one unit and the issue cannot be reproduced then there might have been an issue with the initial programming of that unit. Without being able to reproduce the issue it's difficult to speculate what might have happened, especially if there was no error logged by Uniflash during the 1st programming. 

    Best Regards,

    Marlyn