MPC8315: tsec_id2 register value

[gouravjain]

Hi,

After reading MPC8315 RM, i understand that, it supports 1588 timer feature. 

But while reading tsec_id2 register it shows:  0x0030_00F0 that means bit 8 is "0" i.e. 1588 protocol not supported.

Pls let me know while MPC8315 supports 1588 protocol or not ?? And what should be the correct value of tsec_id2 value ??

Thanks,

Gourav Jain

[alexander_yakov]

The correct after-reset value of TSEC_ID2 register is shown in MPC8315 Reference Manual, Figure 19-3 - 0x00E000F0

Have a great day,
Alexander,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[gouravjain]

Thanks Alexander for paying attention on my query.

But in my case its coming 0x0030_00F0. Since this is RO register i cant modify. How to debug??

What all changes are required to get 0x00E000F0 ??

--

Gourav

[gouravjain]

Hi Alexander,

u-boot shows the following values,

md e0024000
e0024000: 01240005 003000f0 00000000 00000000 .$...0..........
e0024010: 00000600 00000000 00000000 00000000 ................
e0024020: 00000050 00000000 00000000 00000000 ...P............
e0024030: 0000001f 00000000 00000000 00000000 ................
e0024040: 00000000 00000000 00000000 00000000 ................
e0024050: 00000080 000000c0 00000040 00000080 ...........@....
e0024060: 00000000 00000000 00000000 00000000 ................
e0024070: 00000000 00000000 00000000 00000000 ................
e0024080: 00000000 00000000 00000000 00000080 ................
e0024090: 00000000 00000000 00000040 00000080 ...........@....
e00240a0: 00000000 00000000 00000000 00000000 ................
e00240b0: 00000000 00000000 00000000 00000000 ................
e00240c0: 00000000 00000000 00000000 00000000 ................
e00240d0: 00000000 00000000 00000000 00000000 ................
e00240e0: 00000000 00000000 00000000 00000000 ................
e00240f0: 00000000 00000000 00000000 00000000 ................
=> md e0025000
e0025000: 01240005 003000f0 00000000 00000000 .$...0..........
e0025010: 00000000 00000000 00000000 00000000 ................
e0025020: 00000050 00000000 00000000 00000000 ...P............
e0025030: 0000001f 00000000 00000000 00000000 ................
e0025040: 00000000 00000000 00000000 00000000 ................
e0025050: 00000080 000000c0 00000040 00000080 ...........@....
e0025060: 00000000 00000000 00000000 00000000 ................
e0025070: 00000000 00000000 00000000 00000000 ................
e0025080: 00000000 00000000 00000000 00000080 ................
e0025090: 00000000 00000000 00000040 00000080 ...........@....
e00250a0: 00000000 00000000 00000000 00000000 ................
e00250b0: 00000000 00000000 00000000 00000000 ................
e00250c0: 00000000 00000000 00000000 00000000 ................
e00250d0: 00000000 00000000 00000000 00000000 ................
e00250e0: 00000000 00000000 00000000 00000000 ................
e00250f0: 00000000 00000000 00000000 00000000 ................
=>

[alexander_yakov]

We have device errata, where is is said that incorrect TSEC_ID2 value may be reported, but this does not affect TSEC functionality.

According to our knowledgebase, incorrect 0x003000F0 was reported previously by other customers, and for more recent devices, for example, for P2020 processor, we specify this value 0x003000F0 as default in Reference Manual.