Jun 28, 2021
01:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 28, 2021
01:54 AM
I'm struggling to verify if the software in third party product based on a XMC1400 microcontroller remained unschanged since the first delivery.
Is there any kind of hash value or checksum which is accessible by debugger, even if the memory of the device is protected?
Unfortunately I was not able to find any information to this topic within datasheets or related documents.
Is there any kind of hash value or checksum which is accessible by debugger, even if the memory of the device is protected?
Unfortunately I was not able to find any information to this topic within datasheets or related documents.
Solved! Go to Solution.
- Tags:
- IFX
1 Solution
Jun 30, 2021
02:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 30, 2021
02:20 AM
Hi,
There are two conditions,
If the firmware is locked and if the programming connector is not available then it cannot be Verified
If either of the above conditions are true, we cannot verify
If the firmware is not locked, and we can access the programming pins, we can take a snapshot of the new equipment.
We can use this to later verify the firmware integrity.
Regards
Alakananda
There are two conditions,
If the firmware is locked and if the programming connector is not available then it cannot be Verified
If either of the above conditions are true, we cannot verify
If the firmware is not locked, and we can access the programming pins, we can take a snapshot of the new equipment.
We can use this to later verify the firmware integrity.
Regards
Alakananda
Alakananda
3 Replies
Jun 30, 2021
02:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 30, 2021
02:20 AM
Hi,
There are two conditions,
If the firmware is locked and if the programming connector is not available then it cannot be Verified
If either of the above conditions are true, we cannot verify
If the firmware is not locked, and we can access the programming pins, we can take a snapshot of the new equipment.
We can use this to later verify the firmware integrity.
Regards
Alakananda
There are two conditions,
If the firmware is locked and if the programming connector is not available then it cannot be Verified
If either of the above conditions are true, we cannot verify
If the firmware is not locked, and we can access the programming pins, we can take a snapshot of the new equipment.
We can use this to later verify the firmware integrity.
Regards
Alakananda
Alakananda
Jun 30, 2021
10:31 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 30, 2021
10:31 PM
Thank you very much for the quick reply.
The P0.13, P0.14, P0.15, VSS and VDD Ports are accessible.
I got myself a DAP-MiniWiggler and tried to establish a connection using DAS and the Mem-Tool.
Unfortunately I always get the attached error message.
Is this because the device is fully protected, or because I made some mistake(s) in setting up the connection?
Regards
Andreas
The P0.13, P0.14, P0.15, VSS and VDD Ports are accessible.
I got myself a DAP-MiniWiggler and tried to establish a connection using DAS and the Mem-Tool.
Unfortunately I always get the attached error message.
Is this because the device is fully protected, or because I made some mistake(s) in setting up the connection?
Regards
Andreas
Jul 04, 2021
10:16 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 04, 2021
10:16 PM
Hi,
Can you confirm us the boot mode of the device?
Can you also power on reset the device and try to connect immediately and test.
Regards
Alakananda
Can you confirm us the boot mode of the device?
Can you also power on reset the device and try to connect immediately and test.
Regards
Alakananda
Alakananda