RESET on MC9S12XDP512 without BDM

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

RESET on MC9S12XDP512 without BDM

ソリューションへジャンプ
2,482件の閲覧回数
tnriley
Contributor III

I am having issue with the board working as expected when running under codeWarrior with PE Micro BDM pod but continually resets itsself with pod detached. The RESET pulse width is ~8.3 uSecs (with 24Mhz PLLCLK about 199 cycles) so internal source for cause.

I have checked all the usual suspects, GNDS, 5vPWR, both LVR and POR, ILAF, COP, CME.

I am confused as to why code executes with BDM but fails without. Any ideas

0 件の賞賛
返信
1 解決策
2,472件の閲覧回数
lama
NXP TechSupport
NXP TechSupport

Hi,

In this case I would focus on the SW. There are registers or bits which are write once only in the normal mode but writeable anytime in BDM mode. It is possible that something is already set somewhere and you try to do it again but it is ignored in the normal mode.
Have you observed the same behavior when you used the software containing only for(;;); or toggling some port/pin in the cycle?

Best regards,
Ladislav

 

元の投稿で解決策を見る

2 返答(返信)
2,434件の閲覧回数
tnriley
Contributor III

Ladislav,

Thanks for the info. I was able to trace the problem back to an external Real Time Clock connected to IRQ pin. RTC outputs a 1Hz square wave which I use as a timing pulse on the falling edge. I was writing IRQE more than once, first time @ startup to clear out IRQCR, then later to set IRQE as edge triggered and enable the IRQEN. Obviously the second write wasn't accepted for IRQE, since its write once in normal mode. But what I am still unsure of is why the RESET. I can understand multiple IRQ interrupts because the RTC is LOW for 500mSecs. So I get back in as soon as I exit. The BDM is no help in cases such as this because it was happily running with no issues.

0 件の賞賛
返信
2,473件の閲覧回数
lama
NXP TechSupport
NXP TechSupport

Hi,

In this case I would focus on the SW. There are registers or bits which are write once only in the normal mode but writeable anytime in BDM mode. It is possible that something is already set somewhere and you try to do it again but it is ignored in the normal mode.
Have you observed the same behavior when you used the software containing only for(;;); or toggling some port/pin in the cycle?

Best regards,
Ladislav