Oct 06, 2020
02:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 06, 2020
02:40 PM
Hi there,
I am using Aurix triCore TC275-D. I have some non-zero data located at 0x8001C000. And I have the following code to read and copy the value to a variable
debugCnt2 = modelParam.rev_num;
0x8003F016 91 20 00 F8 MOVH.A a15,0x8002
0x8003F01A 19 FF 00 0C LD.W d15,[a15]-0x4000
0x8003F01E 91 10 00 F7 MOVH.A a15,0x7001
0x8003F022 59 FF 28 CC ST.W [a15]-0x3CD8,d15
But for whatever reason. the value of the 'debuCnt2' is zero. I checked the register of d15 is 0, as well.
Thanks for help. Ke
I am using Aurix triCore TC275-D. I have some non-zero data located at 0x8001C000. And I have the following code to read and copy the value to a variable
debugCnt2 = modelParam.rev_num;
0x8003F016 91 20 00 F8 MOVH.A a15,0x8002
0x8003F01A 19 FF 00 0C LD.W d15,[a15]-0x4000
0x8003F01E 91 10 00 F7 MOVH.A a15,0x7001
0x8003F022 59 FF 28 CC ST.W [a15]-0x3CD8,d15
But for whatever reason. the value of the 'debuCnt2' is zero. I checked the register of d15 is 0, as well.
Thanks for help. Ke
3 Replies
Oct 06, 2020
06:58 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 06, 2020
06:58 PM
Just to be sure - can you dump a bit of memory at 0x8001C000?
Could it be that there's an interrupt handler that isn't saving and restoring D15 in between those instructions?
Could it be that there's an interrupt handler that isn't saving and restoring D15 in between those instructions?
Oct 08, 2020
12:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 08, 2020
12:07 PM
I can read the memory with debugger. I can read the constant variable located at 0x8001C000, as well. I cannot copy the value to the ram mirror. The disassembly code seems to be right. is it because some safety measurement, overlay setting, ...?
Oct 08, 2020
01:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 08, 2020
01:22 PM
Is this executing on CPU0? If it's executing on a different CPU, could it be that the data cache is active, and the debugger's view of memory is stale?
This widget could not be displayed.