• 状态
  • 已锁定 已锁定
  • 个回复 3 个回复
  • 名订阅用户 12 名订阅用户
  • 次查看 349 次查看
  • 用户 0 名在线用户
选项
选项
相关

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C1290NCZAD: After the bootloader has downloaded the application, the microcontroller has a chance to enter the FaultISR() function.

xxx xxx
Prodigy 30 points
Part Number: TM4C1290NCZAD

For the original Bootloader program of TM4C, the main points of my modification are

1. Modified the start address 0x8000.

2. Modified the communication protocol.

3. Added download area and APP run area.

4. Initialized the SPI port.


For Bootloader, the hex written to flash is correct, I have confirmed it.
For APP part, some APP can run normally after downloading in, and some code will enter FaultISR () after downloading in.

About verifying the correctness of the APP program, what I am doing now is just changing the APP start address to 0x0000, and the APP part of the code will run normally.

So now I want to know, how can I solve this occasional problem?


The picture is a screenshot of my debugging, the SP and some register values, and the map of APP.

  • 0
    TI__Guru 65745 points

    Hi,

    I have already posted this issue to the related engineer. I will reply you once I got response. Thanks for your patience.

  • 0 回复 Yale Li 李耀先
    Prodigy 30 points

    Can you give me a time to reply?

  • 0
    TI__Guru 65745 points
    xxx xxx 说：
    2. Modified the communication protocol.

    This is pretty vague, what exactly is meant by this? Is it just changing from UART to SSI for the boot loader, or a wider change?

    xxx xxx 说：
    3. Added download area and APP run area.

    How is the linker configuration file for the target project configured? Can the .cmd file be either uploaded or pasted for review?

    xxx xxx 说：

    The picture is a screenshot of my debugging, the SP and some register values, and the map of APP.

    For debugging faults / stack pointer issues, recommendation would be to follow https://www.ti.com/lit/pdf/spma043 - It won't really be feasible for me to try and debug this from a single screenshot, but as you work through the steps you can report back any findings that are unclear and I should be able to further explain what you are seeing and help track down the root cause that way.