TMS570LS3137: het1ParityCheck: RAM Parity test

Kalyan Vagvala61

Expert 1075 points

Part Number: TMS570LS3137

Hi,

I am trying to perform HET1 RAM Parity test, below is the steps i am executing:

1. Write known value to 0xFF460000 HET RAM address say (0xFFFFFFFF)

2. Disable HET1 RAM parity.

3. Toggle bit Zero of data at HET RAM address 0xFF460000.

4. Enable HET1 RAM parity.

5. Read data from 0xFF460000 HET1 RAM address

but when when i write 0xFFFFFFFF to HET RAM address 0xFF460000, i could see 0x03FFFFFF in the memory browser. some how i could get any details in TRM why first 6 bits are not able to write?

Can you please help me in understanding this issue?

Thanks,

Kalyan

over 6 years ago

0 Sahin Okur over 6 years ago

TI__Mastermind 27355 points

Hi Kalyan,

You will need to set the TEST bit in the Parity Control Register (PCR) to enable test mode and write the parity bit. Then make sure to disable test mode before reading the RAM.

Please refer to the response from Charles in this thread for more details:

0 Kalyan Vagvala61 over 6 years ago in reply to Sahin Okur

Expert 1075 points

Hi Sachin,

I think i haven't conveyed my question correctly. Is the HET instruction ram whole 32-bit writable?

When i try to write data 0xFFFFFFFF to address 0xFF460000, i could see in memory browser that 0x03FFFFFF.

Thanks,

Kalyan

0 Sunil Oak over 6 years ago in reply to Kalyan Vagvala61

TI__Mastermind 49120 points

The program field is physically implemented as a 26-bit value and not a 32-bit value. The upper 6 bits for all instructions always read as zeros.

0 Kalyan Vagvala61 over 6 years ago in reply to Sunil Oak

Expert 1075 points

Hi Sunil,

Thanks for your response. Can you please point me to the details of this program field in TRM or any TMS570LS3137 releted documents?

Thanks,

Kalyan

0 Sunil Oak over 6 years ago in reply to Kalyan Vagvala61

TI__Mastermind 49120 points

Hi Kalyan,

The information about the physical implementation of the memories is not described in a public document. There is usually no need for the application to write and read back from the individual peripheral memories in order to test the diagnostic mechanisms. For example, while testing parity error generation, you can choose to "throw away' the data read back from the HET RAM and make sure that a parity error is generated.

Regards, Sunil

Arm-based microcontrollers

Arm-based microcontrollers forum

TMS570LS3137: het1ParityCheck: RAM Parity test