Does HSM PCODE Flash need to be always Contiguous from S0 for Aurix 2G architecture?

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User9635
Level 4
Level 4
50 replies posted 50 questions asked 25 replies posted
Hello Support,

For Aurix 2G System, when Tuning Protection feature is not being used by the user,

1> the HSM PCODE Image has to reside from S0 Sector of PF0 Flash and it has to be contiguous only always?
Or,
2> it can reside in any non contiguous sectors within S0 to S39 range of sectors from PF0 Flash Bank?

Are either of the above options can be used or only one of them?
If only one of the above option, then which one
Software Over The Air feature is not being used.
Best Regards
0 Likes
1 Solution
NeMa_4793301
Level 6
Level 6
10 likes received 10 solutions authored 5 solutions authored
#1: The boot sector is specified in PROCONHSMCBS. It does not have to be S0.
#2: HSM code sectors do not have to be contiguous. Sectors can be individually specified as HSM exclusive via PROCONHSMCX0/1.

View solution in original post

0 Likes
3 Replies
NeMa_4793301
Level 6
Level 6
10 likes received 10 solutions authored 5 solutions authored
#1: The boot sector is specified in PROCONHSMCBS. It does not have to be S0.
#2: HSM code sectors do not have to be contiguous. Sectors can be individually specified as HSM exclusive via PROCONHSMCX0/1.
0 Likes
User9635
Level 4
Level 4
50 replies posted 50 questions asked 25 replies posted
Hello Support,
Can we say that the User Manual is saying wrong as it is asking HSM PCODE to be contiguous as shown below :
5363.attach
Best Regards
0 Likes
NeMa_4793301
Level 6
Level 6
10 likes received 10 solutions authored 5 solutions authored
I suspect we're just trying to keep from applications tripping over their toes as the CPUs prefetch instructions and possibly cross sector boundaries.

Keeping HSM PCODE contiguous avoids that sort of trouble.
0 Likes