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.

TMS320F28379S: Question about F2837x SafeTI diagnostic library

Part Number: TMS320F28379S

 

Hi Champ,

I have some question about   F2837x SafeTI diagnostic  library  example project.

Could you kindly help on my following question?

 

In sta_tests.c there have below testing:

 

Qusetion 1:

For the startAddress, endAddress, goldenCRC are fixed for this device?

If the address is fixed , any document to description these address and the goldenCRC?

 

        case STA_BROM_CRC:

        {

            //

            // Set range to calculate CRC for and the golden CRC value.

            //

            uint32_t startAddress = 0x3F8000;

            uint32_t endAddress = 0x3FFFBF;

            uint32_t goldenCRC = 0xBA67176C;

 

 

Qusetion 2:

For the startAddress, endAddress, goldenCRC is fixed for this device?

If the address is fixed , any document to description these address and the goldenCRC?

When the address range is 0x78000 to  0x7800F? these address are Z1-LINKPOINTER1 to  Z1-LINKPOINTER3.

Z1-LINKPOINTER1 to  Z1-LINKPOINTER3 value will be changed by customer if they use DCSM function.

 

 

        case STA_FLASH_CRC:

        {

            //

            // Set range to calculate CRC for and the golden CRC value.

            //

            uint32_t startAddress = 0x78000;

            uint32_t endAddress = 0x78010;

            uint32_t goldenCRC = 0xB70C7E38;

  • Hi,

    1) You can modify this if you wish. Just run the CRC calculation a couple time or on different devices to find the golden CRC. We do not publish golden values and ranges.

    2) If they use DCSM then those values will change, but will remain constant until they update them again. In either case, the values are known and CRC can be calculated. Or CRC can be ignored for these values since there are 3 link pointers and there is a safety mechanism already in place to handle any bit errors. Please see the DCSM chapter for more details. There are 3 link pointers because there is no ECC on these addresses.

    sak