Oct 08, 2018
12:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 08, 2018
12:27 AM
Hi All,
I read the CHIP_ID of TLE987x through USER_READ_100TP, but the ID bytes are aways zero. How to read the correct ID?
According to BootROM User Manual, the Chip_ID bytes can be read via BSL mode A. How to do it?
I read the CHIP_ID of TLE987x through USER_READ_100TP, but the ID bytes are aways zero. How to read the correct ID?
According to BootROM User Manual, the Chip_ID bytes can be read via BSL mode A. How to do it?
Labels
- Tags:
- chip_id tle987x
- IFX
3 Replies
Oct 08, 2018
07:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 08, 2018
07:37 AM
Hi jacko,
What is the full marking on your device ? What is written on your chip after TLE987 ?
Best Regards
What is the full marking on your device ? What is written on your chip after TLE987 ?
Best Regards
Oct 08, 2018
06:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 08, 2018
06:45 PM
pestadieu wrote:
Hi jacko,
What is the full marking on your device ? What is written on your chip after TLE987 ?
Best Regards
Hi Pestadieu,
It is TLE9877QXA40.
In addition, how to protect the flash from reading out? I download the software NVM_PROTECTION_EXAMPLE_TLE987X, but it can be read out use J-LINK.
Oct 10, 2018
07:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 10, 2018
07:37 AM
Hi,
You can read the Chip_ID with the USER_READ_100TP function, see the following example:
The first argument of the USER_READ_100TP function is the page, the second is the offset and the third is the variable in which the Chip_ID value will be stored.
The Chip_ID is 12 bytes long, so each chip_id_x variable will store 4 bytes of the Chip_ID.
Concerning your other question, you have to reset the chip after starting the debugger. Otherwise the debugger will have access to the flash before the protection is actually active.
Be aware that once the protection is activated, you can't write the flash anymore.
Best regards
You can read the Chip_ID with the USER_READ_100TP function, see the following example:
uint32_t chip_id_0_3;
uint32_t chip_id_4_7;
uint32_t chip_id_8_11;
USER_READ_100TP(0x11, 0x6c, &chip_id_0_3);
USER_READ_100TP(0x11, 0x70, &chip_id_4_7);
USER_READ_100TP(0x11, 0x74, &chip_id_8_11);
The first argument of the USER_READ_100TP function is the page, the second is the offset and the third is the variable in which the Chip_ID value will be stored.
The Chip_ID is 12 bytes long, so each chip_id_x variable will store 4 bytes of the Chip_ID.
Concerning your other question, you have to reset the chip after starting the debugger. Otherwise the debugger will have access to the flash before the protection is actually active.
Be aware that once the protection is activated, you can't write the flash anymore.
Best regards