Oct 21, 2020
03:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 21, 2020
03:30 AM
Hi everybody,
I have one more question for you concerning the TC397 chip.
I use DAP interface to BMHD programming and my application downoaling to PFLASH, I can properly program BMHD in UCB_ORIG and UCB_COPY for BMHD0 and after the reset SSW successfully recognize it and sets BMHD state like UNLOCKED. Then CPU goes to HARR state. But when I try to unhalt CPU, it doesn't start and infinitely stay on the constant PC address 0xA00024f4 (my application start address).
May be I have to change confiration state to CONFIRMED? If yes, How can I do it? HWCFG[3]..[5] are in "1".
I have one more question for you concerning the TC397 chip.
I use DAP interface to BMHD programming and my application downoaling to PFLASH, I can properly program BMHD in UCB_ORIG and UCB_COPY for BMHD0 and after the reset SSW successfully recognize it and sets BMHD state like UNLOCKED. Then CPU goes to HARR state. But when I try to unhalt CPU, it doesn't start and infinitely stay on the constant PC address 0xA00024f4 (my application start address).
May be I have to change confiration state to CONFIRMED? If yes, How can I do it? HWCFG[3]..[5] are in "1".
- Tags:
- IFX
2 Replies
Oct 22, 2020
12:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 22, 2020
12:49 AM
The described behavior has nothing to do with the BMHD. Don't set the BMHD to CONFIRMED otherwise it will be more complicated to reprogram the BMHD.
From my point of view there is a breakpoint with break before make set on the start address from the startup software. this breakpoint must be clear before you unhalt the CPU.
Which debugger you use?
From my point of view there is a breakpoint with break before make set on the start address from the startup software. this breakpoint must be clear before you unhalt the CPU.
Which debugger you use?
Oct 22, 2020
01:37 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 22, 2020
01:37 PM
MoD wrote:
The described behavior has nothing to do with the BMHD. Don't set the BMHD to CONFIRMED otherwise it will be more complicated to reprogram the BMHD.
From my point of view there is a breakpoint with break before make set on the start address from the startup software. this breakpoint must be clear before you unhalt the CPU.
Which debugger you use?
Our company designed programmer board for most of chips including the Tricore Aurix family. I use this programmer for debugging (through the DAP IF).
Thanks a lot for breakpoint idea. I'll try to check.