Sign in

username:

password:



Not a member?

Search 68hc12



Search tips

Subscribe to 68hc12



68hc12 by Keywords

68HC1 | 812A4 | 9S12DP256 | Bootloader | CodeWarrior | D60A | Debugger | DP256 | ECT | EEPROM | EVB | Flash | HC1 | HCS12 | I2C | IAR | ICC1 | Interrupts | LCD | M68KIT912DP256 | MC9S12DP256 | MC9S12DP256B | Metrowerks | Motor | MSCAN | Multilink | PLL | Quadrature | SDI | SPI | Transceiver | XFC

Ads

Discussion Groups

Discussion Groups | 68HC12 | detecting the debugger?

Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).

Re: detecting the debugger? - Edward Karpicz - Oct 27 16:40:12 2007

Hi,

usually we debug in special single chip mode and run in normal single chip
mode. MODE register should tell you what mode is your chip in.

Regards

Edward
----- Original Message -----
From: "James M. Knox"
To: <6...@yahoogroups.com>
Sent: Saturday, October 27, 2007 22:42
Subject: [68HC12] detecting the debugger?
>
> This may be a simple question, but I've just never needed to do it
> before. Is there a way for the software (HCS processor, specifically
> an S12A64 if that matters) to detect that the debugger BDM cable is
> attached? I would like to maintain only one version, but the P&E BDM
> debugger won't run across a switch from 4 MHz to 48 MHz. So I am
> having to run at a maximum of 8 MHz with the BDM cable attached, then
> switch to full speed when I am not debugging.
>
> I know I could probably rig an unused discrete and jumper, but I
> would rather not have to do that. So I'm hoping there is a status
> bit in a register somewhere that says it is under BDM control.
>
> tnx,
>
> jmk
>
> -----------------------------------------------
> James M. Knox
> TriSoft ph 512-385-0316
> 1300 Koenig Lane West fax 512-371-5716
> Suite 200
> Austin, Tx 78756 j...@trisoft.com
> -----------------------------------------------
>



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )


Re: detecting the debugger? - Oliver Betz - Oct 29 12:29:16 2007

James M. Knox wrote:

[...]

> >I suggest to drop the incapable debugger and use NoICE - it's not
> >expensive and works very well (didn't test the HC12 variant but used
> >it for HC08 development some time ago).
>
> When I first started running into these PLL problems I got the same
> suggestion. I looked at NoICE, and agree that it is well worth
> investigating. But in the middle of a high-pressure-schedule project
> doesn't seem like a good time to switch horses. So I need to get

I see no problems by doing so. NoICE isn't hard to understand, you
should get it working in a couple of hours. Maybe it's less effort
than debugging at different speed. Give it a try!

Another idea: use another 9S12 derivative (without the PLL bug), and
a superset of peripherals. I don't know whether for the A64 exists a
compatible "superset" derivative. And likely it's more expensive and
more work than using NoICE.

Oliver
--
Oliver Betz, Muenchen



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Re: detecting the debugger? - "James M. Knox" - Oct 29 14:54:14 2007

At 17:25 10/29/2007 +0100, you wrote:

>Another idea: use another 9S12 derivative (without the PLL bug), and
>a superset of peripherals. I don't know whether for the A64 exists a
>compatible "superset" derivative. And likely it's more expensive and
>more work than using NoICE.

I'm shipping prototypes on Thursday, and pre-production units in 30
days. I *really* want to minimize changes until then.

jmk
-----------------------------------------------
James M. Knox
TriSoft ph 512-385-0316
1300 Koenig Lane West fax 512-371-5716
Suite 200
Austin, Tx 78756 j...@trisoft.com
-----------------------------------------------



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )