Mar 08, 2016
03:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 08, 2016
03:13 AM
Hello,
due to the UM of XMC4500 following steps/setups must be done if the Fallback ABM is used:
1. Boot mode pin encoding for PORST (Table 26-1): BMI
2. Content of UCB2, User Configuration Block 2 evaluated by SSW after PORST/any reset: SWCON = Fallback ABM, Speed-up = 1, valid XOR checksum, all others optional
3. ABM[0] at end of 1st 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
4. ABM[1] at end of 2nd 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
If ABM[0] corrupted, SSW will choose the ABM[1].
Are the above described steps/setups correct ? Thanks in advance for any comment.
due to the UM of XMC4500 following steps/setups must be done if the Fallback ABM is used:
1. Boot mode pin encoding for PORST (Table 26-1): BMI
2. Content of UCB2, User Configuration Block 2 evaluated by SSW after PORST/any reset: SWCON = Fallback ABM, Speed-up = 1, valid XOR checksum, all others optional
3. ABM[0] at end of 1st 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
4. ABM[1] at end of 2nd 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
If ABM[0] corrupted, SSW will choose the ABM[1].
Are the above described steps/setups correct ? Thanks in advance for any comment.
- Tags:
- fallback abm
- IFX
2 Replies
Attachments are accessible only for community members.
Mar 08, 2016
06:21 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 08, 2016
06:21 PM
Mar 08, 2016
06:25 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 08, 2016
06:25 PM
1. Boot mode pin encoding for PORST (Table 26-1): BMI
Yes, Startup Software (SSW) will check on this pin to determine BOOT MODE
2. Content of UCB2, User Configuration Block 2 evaluated by SSW after PORST/any reset: SWCON = Fallback ABM, Speed-up = 1, valid XOR checksum, all others optional
3. ABM[0] at end of 1st 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
4. ABM[1] at end of 2nd 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
Basically, if the checksum listed in the ABM is correct for both the ABM and defined software the MCU will executed the code from the specified boot address.
Yes, Startup Software (SSW) will check on this pin to determine BOOT MODE
2. Content of UCB2, User Configuration Block 2 evaluated by SSW after PORST/any reset: SWCON = Fallback ABM, Speed-up = 1, valid XOR checksum, all others optional
3. ABM[0] at end of 1st 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
4. ABM[1] at end of 2nd 64kB sector on flash: valid magic key, valid start address of code, app.-length = 0xffff ffff (if not used), app.-crc32 = 0xffff ffff (if not used), valid crc32 of ABM header
Basically, if the checksum listed in the ABM is correct for both the ABM and defined software the MCU will executed the code from the specified boot address.