Codewarrior Debug u-boot (Documentation confusion)

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

Codewarrior Debug u-boot (Documentation confusion)

1,299件の閲覧回数
reginaldstjohn
Contributor III

We have tried, unsucessfully, to debug the Linux Kernel on our custom LS1012A board after much attempted help from @yipingwang. We have now moved on to trying to just debug u-boot and are having problems with the instructions given by @yipingwang  in his document pointed to by the following forum link:

https://community.nxp.com/t5/CodeWarrior-for-QorIQ-Knowledge/Use-CodeWarrior-for-ARMv8-to-Debug-U-bo...

The main trouble we are having is this:

The instructions want you to attatch to a running u-boot

"In the Startup panel, configure “Reset and Delay” as 0, uncheck “Load image” to use CodeWarrior to attach to the running software on the target board."

However, How can the process be stopped at _start if it is already running and past the _start method? 

Does the debug connection reset the processor?  On our system it never hits the breakpoint but if we suspend (pause). we can see that we are running u-boot, we can see the asembly etc. but we are well past the _start method.

 

0 件の賞賛
返信
1 返信

1,270件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

If you configure “Reset and Delay” as 0, when CodeWarrior connects to the target board, it will reset the target board.

After suspending CodeWarrior, you could try to click "reset" button in CodeWarrior IDE to reset the target board manually.

0 件の賞賛
返信