|
Hi All I got a bit of a strange one. Got a T board hooked via POD12 to a NoIce debugger. After modifying the Serial monitor for operation on the DP256B (only took a week:-)loaded the S19 file from the Motorola assembler (using MCUez shell) via the NoIce Load command. Programming appeared to be going smoothly, but when trying to start NoIce afterwards it reported "ComPod cannot enter Background mode", no communication. No worries I thought, must have set something wrong in the Prot or security registers despite the warnings in this forum. Fired up Starprog and tried the bulk erase, it reports "Cannot establish Single Chip Mode" This is where I am at, the MOD pins appear all low on reset (voltmeter)and my understanding from the manual is that the BDM communication is purely hardware controlled from NoIce or Starprog and shouldn't execute my program out of reset in special single chip mode. Playing with the reset button (with Pod attached) it appears something is running riot internally when it shouldn't, evidenced by some of the lights coming on on the T board. The strange bit is that, when executing the bulk erase, the lights go of, I.e. it the Pod is talking at least for a short while, but it still reports no single chip mode available. Reread previous advise in the forum and studied the manual some more but no luck. Since there is no info for the POD I cannot write any test routine. Anybody ideas? Regards, Theo |
|
|
Lock out
Started by ●September 28, 2003
Reply by ●September 28, 20032003-09-28
|
Hi Theo, you can try my debugger/programmer package HC12ICD for unsecuring your target device with ComPOD12: http://www.krummsdorf.de/files/hc12icd.zip See instructions in http://www.krummsdorf.de/files/first.pdf To enable the device security menu in the demo version change in the "hc12icd.ini" [HC12ICD] FLBBDEMO=0. E-mail me privately if you have some other questions. Good luck and regards J.K. ------------------------------- Dipl.Ing. J.Krummsdorf Sttelner Strasse 30 04416 Markkleeberg,Germany ------------------------------- WEB : www.krummsdorf.de/hc12icd/ -------------------------------- email: -------------------------------- Am 28.09.03 09:34:29, schrieb "theobee00" <>: >Hi All > >I got a bit of a strange one. > >Got a T board hooked via POD12 to a NoIce debugger. > >After modifying the Serial monitor for operation on the DP256B (only took a week:-)loaded the S19 file from the Motorola assembler (using MCUez shell) via the NoIce Load command. > >Programming appeared to be going smoothly, but when trying to start NoIce afterwards it reported "ComPod cannot enter Background mode", no communication. > >No worries I thought, must have set something wrong in the Prot or security registers despite the warnings in this forum. > >Fired up Starprog and tried the bulk erase, it reports "Cannot establish Single Chip Mode" > >This is where I am at, the MOD pins appear all low on reset (voltmeter)and my understanding from the manual is that the BDM communication is purely hardware controlled from NoIce or Starprog and shouldn't execute my program out of reset in special single chip mode. > >Playing with the reset button (with Pod attached) it appears something is running riot internally when it shouldn't, evidenced by some of the lights coming on on the T board. > >The strange bit is that, when executing the bulk erase, the lights go of, I.e. it the Pod is talking at least for a short while, but it still reports no single chip mode available. > >Reread previous advise in the forum and studied the manual some more but no luck. >Since there is no info for the POD I cannot write any test routine. > >Anybody ideas? >Regards, > >Theo > |
|
|
Reply by ●September 28, 20032003-09-28
|
Hi Theo, seems like you have (unintentionally) secured the device. You must unsecure it to re-enable BDM communication. With ComPOD12/Pro and StarProg you can simply click on the "unsecure" icon (after setting the proper target device type). With the ComPOD12 (no /Pro) this function is not present, but StarProg prevents accessing the security word at $FF0E, so the device should always remain in unsecured state. Which pod revision do you use? You may send me your code file off-list, so I can check what happened. BTW, you can get the latest StarProg release here: http://www.elektronikladen.de/files/starprog_v200c.zip greetings! Oliver On Sun, 28 Sep 2003 07:34:29 -0000 "theobee00" <> wrote: > Hi All > > I got a bit of a strange one. > > Got a T board hooked via POD12 to a NoIce debugger. > > After modifying the Serial monitor for operation on the DP256B (only took a week:-)loaded the S19 file from the Motorola assembler (using MCUez shell) via the NoIce Load command. > > Programming appeared to be going smoothly, but when trying to start NoIce afterwards it reported "ComPod cannot enter Background mode", no communication. > > No worries I thought, must have set something wrong in the Prot or security registers despite the warnings in this forum. > > Fired up Starprog and tried the bulk erase, it reports "Cannot establish Single Chip Mode" > > This is where I am at, the MOD pins appear all low on reset (voltmeter)and my understanding from the manual is that the BDM communication is purely hardware controlled from NoIce or Starprog and shouldn't execute my program out of reset in special single chip mode. > > Playing with the reset button (with Pod attached) it appears something is running riot internally when it shouldn't, evidenced by some of the lights coming on on the T board. > > The strange bit is that, when executing the bulk erase, the lights go of, I.e. it the Pod is talking at least for a short while, but it still reports no single chip mode available. > > Reread previous advise in the forum and studied the manual some more but no luck. > Since there is no info for the POD I cannot write any test routine. > > Anybody ideas? > Regards, > > Theo > > -------------------- > > ">http://docs.yahoo.com/info/terms/ > |
|
|
Reply by ●September 28, 20032003-09-28
|
--- In , Juergen Krummsdorf <juergen@k...> wrote: > you can try my debugger/programmer package HC12ICD for unsecuring your target device with ComPOD12: Hi Juergen, Thanks for that, will report back when I have tried it. Regards, Theo |
Reply by ●September 28, 20032003-09-28
|
--- In , Oliver Thamm <othamm_yahgrp@h...> wrote: Hi Oliver Thanks for the quick reply. > seems like you have (unintentionally) secured the device. You must > unsecure it to re-enable BDM communication. That was my assesment too. > With ComPOD12/Pro and StarProg you can simply click on the "unsecure" > icon (after setting the proper target device type). The secure and unsecure buttons are greyed out, erase button is active. The status line says Compod12-com1, target MC9S12DP256B Flash (default), Modes normal(S1) paged(S2), this appears correct. Although it is clear something happens (from the lights of the CPU changing), it comes back with the message; "Can't establish Special Single Chip Mode - check MODE-Pins and clock! (ComPOD12 firmware version 1.09) This I take to mean the erase did not happen. > With the ComPOD12 (no /Pro) this function is not present, but StarProg > prevents accessing the security word at $FF0E, so the device should always > remain in unsecured state. Ah, but I programmed it with NoIce, I take it you mean no access when loading, but erase should still work? >You may send me your code file off-list, > so I can check what happened. Very kind of you, I see if I can find your e-mail address in the list > BTW, you can get the latest StarProg release here: > http://www.elektronikladen.de/files/starprog_v200c.zip I had the V200 version, but the V200c version gives the same result. Regards, Theo > On Sun, 28 Sep 2003 07:34:29 -0000 > "theobee00" <yahoodump2@o...> wrote: > > > Hi All > > > > I got a bit of a strange one. > > > > Got a T board hooked via POD12 to a NoIce debugger. > > > > After modifying the Serial monitor for operation on the DP256B (only took a week:-)loaded the S19 file from the Motorola assembler (using MCUez shell) via the NoIce Load command. > > > > Programming appeared to be going smoothly, but when trying to start NoIce afterwards it reported "ComPod cannot enter Background mode", no communication. > > > > No worries I thought, must have set something wrong in the Prot or security registers despite the warnings in this forum. > > > > Fired up Starprog and tried the bulk erase, it reports "Cannot establish Single Chip Mode" > > > > This is where I am at, the MOD pins appear all low on reset (voltmeter)and my understanding from the manual is that the BDM communication is purely hardware controlled from NoIce or Starprog and shouldn't execute my program out of reset in special single chip mode. > > > > Playing with the reset button (with Pod attached) it appears something is running riot internally when it shouldn't, evidenced by some of the lights coming on on the T board. > > > > The strange bit is that, when executing the bulk erase, the lights go of, I.e. it the Pod is talking at least for a short while, but it still reports no single chip mode available. > > > > Reread previous advise in the forum and studied the manual some more but no luck. > > Since there is no info for the POD I cannot write any test routine. > > > > Anybody ideas? > > > > > > Regards, > > > > Theo > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------- > > > > > > > > ">http://docs.yahoo.com/info/terms/ > > |
