|
Hi Guillermo and people who had same problems! ...provided that we did all the setups Gilles and the archives told us we have to contact ' to get this newer? "icd-12.tgt" file which probably should fix our very hard-to- find problem with ECKLs going beyond the 8MHz border got from a fixed 16MHz oscillator clock and now extending this by selecting a higher PLLCLK, for e.g. 48MHz for generation of a <bus clock>K$MHz! So taking into consideration that Gilles carbon-copied his posting before to the support team we have to wait for an official answer from them! This problem probably is dedicated more to support teams than R&Ds as we now surely could assume... :) Ok, and I am not sure - probably you have to contact ' for the south americas - but look at your contract documents which is the right email address to contact the right location!-) Best regards and happy developing Christian --- In , "Guillermo F. Molina" <gmolina@m...> wrote: > Hi Christian , Gilles and Metrowerks support > > I'm having exactly the same problem with the DP256 / Metrowerks V1.2 and P&E > Multilink Cable 12 (HS). At 8 Mhz everything goes wright, but when I use the PLL to > bring the clock up to 24 Mhz I can't debug anymore... > Please forward me any reply / solution (if there is one.) > > Thank you very much for your help. > Regards, > > Guillermo F. Molina > gmolina@m... > Buenos Aires > ARGENTINA. > > On 13 Feb 2003 at 11:06, Gilles Blanquin wrote: > > > > > Hi Christian. > > > > For sure, the Metrowerks v1.2 IDE was released to support the DP256, > > including bus speed change via PLL. > > However, the P&E multilink\Cable12(HS) target interface (called ICD12) has > > been upgraded due to PLL synchronization problem. > > The Metrowerks support team has the upgraded "icd12.tgt" file you need, I > > will forward this email to them (in CC), so they can contact you. > > Note that if you use a Motorola SDI cable, it is not possible to debug with > > a bus speed higher than 8 MHz (16 MHz osc). > > If you already have this upgrade, make sure that the "set CLKSW bit in > > BDM..." checkbox is checked in the "Communication Device Specification" dialog. > > > > Regards, > > Gilles > > > > At 06:27 PM 2/12/2003, you wrote: > > >Hi Michael, > > > > > >...as I come across your posting I wonder if the "BDM looses > > >sync..." problem is why I have the problem to debug my same EvalKit > > >target using the Metrowerks v1.2 IDE on the DP256 controller as if I > > >choose the: > > > > > >1) PLL divider/multiplier REFDV=8, SYNR=6 I can halt and break the > > >code within the debugger, but choosing > > > > > >2)PLL ... REFDV=1, SYNR=2 for my needed 24MHz ECLK I can't look at > > >any RAM/Flash symbols within the debugger anymore... and this errata > > >says that multiplier shouldn't be equal or greater than 2! Is this > > >the SYNR reg? Than I have a problem 'cause how you can synthesize > > >24MHz ECLK for a mask 3 (1k79x)with what kind of PLL params??? > > > > > >And this problem is directly coupled to the last "Reading > > >permanently '0's..." problem I posted several times! I can't look at > > >if my serial interface output over SCI subsystem on my terminal is > > >writing the right samples I got or not in my char array out there!!! > > > > > >Hope that now you better understand my problem dedicated with reading > > >the port inputs every 1us! Any idea, hint? > > > > > > > > >Hope you can help hereby or telling me some test workaround or > > >something else to get on... ): > > > > > >Christian > > > > > > > > >--- In , Mike Burns <mjb@c...> wrote: > > > > Hi Bruce, > > > > > > > > HCS12 parts are supposed to derive the BDM communications clock > > >directly > > > > from the crystal so changes in the bus speed via the PLL should > > >have no > > > > affect on BDM SYNC. This worked fine in earlier versions of the > > >DP256 and I > > > > believe it works fine in all of the other HCS12 parts. > > > > > > > > However, MCS912DP256 (and DT256, DJ256, DG256) mask 2 (0K79X) and 3 > > >(1K79X) > > > > a new problem was introduced (2001) and errata was issued "BDM > > >LOSES SYNC > > > > WHEN USING PLL AT HIGH FREQUENCIES" > > > > http://e- www.motorola.com/brdata/PDFDB/docs/MC9S12DP256BMSE3.pdf > > > > > > > > As a result of this errata, both Cosmic and P&E modified their > > >tools. The > > > > Cosmic ZAP BDM debugger includes an option for chips with this > > >errata that > > > > allows transparent debugging through a PLL bus speed change. The > > >SYNC > > > > option has actually been in use for over a year. The > > >debugger/cable also > > > > work with the more standard BDM SYNC which is the default out of > > >reset. > > > > > > > > > > > > Best Regards, > > > > Michael Burns > > > > Cosmic Software > > > > > > > > > > > > -----Original Message----- > > > > From: Bruce McMillan [mailto:bruce.mcmillan@P...] > > > > Sent: Thursday, January 09, 2003 10:31 PM > > > > To: > > > > Subject: Re: [68HC12] M68KIT912DP256 > > > > > > > > > > > > John, > > > > thanks for the survey. > > > > We also need the debuggers to support the s12 PLL running faster > > >than > > > > 8MHz. (Motorola bugs 'n all.) > > > > cheers. Bruce > > > > > > > > John Hartman (NoICE) wrote: > > > > > > > > >>Well, there are other BDM emulators for the HC12/HCS12 available > > >in the > > > > >>market. And guess what? They don't have any of the reported > > >problems here. > > > > >>Nohau is selling a BDM for $1990, plugging to either USB, LPT > > >port or a > > > > >> > > > > > > > > > > Doron is right. Here are some that have worked well for me > > >(supported by > > > > > NoICE), all costing less than ($full featured)/10. > > > > > > > > > > Elektronikladen ComPOD12, available from MCT > > >Elektronikladen GbR > > > > > (http://www.elektronikladen.de/noicebdm12.html) > > > > > Technological Arts microBDM12SX, available from > > >Technological Arts > > > > > > > > > (http://www.technologicalarts.com) > > > > > Kevin Ross BDM12, available from Kevin Ross > > > > > (http://www.nwlink.com/~kevinro/bdm.html) > > > > > P&E CABLE12 and MULTILINK, available from P&E > > >Microcomputer > > > > Systems > > > > > (http://pemicro.com) > > > > > Axiom AX-BDM12, available from Axiom Manufacturing > > >Company > > > > > (http://www.axman.com) > > > > > > > > > > The first three are serial devices. Slower than parallel port, > > >but happy > > > > > with longer cables from the PC, and no driver voodoo or port > > >compatibility > > > > > > > > > issues. > > > > > > > > > > The parallel ports ones generally work well, but Billy G. keeps > > >making it > > > > > harder to connect widgets to parallel ports, and has decreed the > > >eventual > > > > > end of both parallel and serial ports on PCs. > > > > > > > > > > There is a crying need for a USB BMD pod for under $300, but I > > >don't know > > > > > of any. Has anyone else heard of one? > > > > > > > > > > Best regards, John Hartman > > > > > john@n... > > > > > NoICE Debugging Tools > > > > > http://www.noicedebugger.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------- > > > > > > > > > > > > > > > > ">http://docs.yahoo.com/info/terms/ > > > > > > > > >-------------------- > > > > > > > > > > > >">http://docs.yahoo.com/info/terms/ > > > > > > > > -------------------- > > > > > > > > ">http://docs.yahoo.com/info/terms/ > > > > |
M68KIT912DP256
Started by ●January 7, 2003
Reply by ●February 14, 20032003-02-14
