Debugging Bootloader and Application

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Debugging Bootloader and Application

ソリューションへジャンプ
1,395件の閲覧回数
rnicolls
Contributor III

Hi,

I'm running a bootloader in a debug session and jumping to an application. I'd like to load symbols for the application so that I can step through the application's code. Is there a way that I can do this?

The application and the bootloader are two separate projects. 

I'm using the LinkServer debugger

Thanks

0 件の賞賛
1 解決策
1,390件の閲覧回数
ErichStyger
Senior Contributor V

See an article I wrote here: https://mcuoneclipse.com/2020/11/03/debugging-bootloader-and-application-with-one-debug-session/

Same principle works with LinkServer connection.

I hope this helps,

Erich

元の投稿で解決策を見る

0 件の賞賛
4 返答(返信)
1,391件の閲覧回数
ErichStyger
Senior Contributor V

See an article I wrote here: https://mcuoneclipse.com/2020/11/03/debugging-bootloader-and-application-with-one-debug-session/

Same principle works with LinkServer connection.

I hope this helps,

Erich

0 件の賞賛
1,367件の閲覧回数
rnicolls
Contributor III

Hi Erich,

Thank you for the article, it was helpful. I have the bootloader running on the target and was able to connect with the application's debug configuration and see the bootloader code. It worked well a couple of times but now I'm consistently getting the attached error. Is this something you've experienced before?

0 件の賞賛
1,362件の閲覧回数
ErichStyger
Senior Contributor V

Yes, I have seen these in other contexts. To my understanding, it indicates a problem between the debug probe and the target. It could be the cable or some noise on the connection line.

What helped on my case was using a different debug probe, e.g. J-Link or P&E.

0 件の賞賛
1,355件の閲覧回数
rnicolls
Contributor III

Great, thank you for the help. I'll see if switching up the debug probe helps with the issue. 

0 件の賞賛