Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).
|
Hi All, Does anyone have an URL/Contact for anyone in Australia who supplies developmant boards or chips for the 68HC12? Does anyone have any preference for Metrowerks V ICC12 IDE's? Thanks for any assistance. Christine [Non-text portions of this message have been removed] |
|
|
|
www.sensair.com ----- Original Message ----- From: Christine Whybrow To: 68HC12 Sent: Monday, September 02, 2002 12:53 PM Subject: [68HC12] Development boards in Australia Hi All, Does anyone have an URL/Contact for anyone in Australia who supplies developmant boards or chips for the 68HC12? Does anyone have any preference for Metrowerks V ICC12 IDE's? Thanks for any assistance. Christine [Non-text portions of this message have been removed] Yahoo! Groups Sponsor ADVERTISEMENT -------------------------------------------------------- To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit http://www.motorola.com/mcu Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed] |
|
Christine Australian Motorola agents... I purchased M68KIT912DP256 from the latter when it was on special... not sure if it still is. This is the Metrowerks/ICC12 packaged with a S12 prototyping board. Documentation needs some work, but once up & running works fine. Don't be afraid to go with 3rd party suppliers. Many will take credit card & ship to your door. Bruce (sydney) _____________________________________ Christine Whybrow wrote: > Hi All, > > Does anyone have an URL/Contact for anyone in Australia who supplies developmant boards or chips for the 68HC12? > > Does anyone have any preference for Metrowerks V ICC12 IDE's? > > Thanks for any assistance. > > Christine > [Non-text portions of this message have been removed] > > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu > > . -- Bruce McMillan www.Pocket-Neurobics.com Tools for the Mind a division of Minder Labs PL ACN 093279915 ..pocket-sized, integrated 4ch neurofeedback and light & sound |
|
Bruce McMillan wrote: > This is the Metrowerks/ICC12 packaged with a S12 prototyping board. Of course I meant to say Metrowerks/P&E Multilink BDM cable... sorry. -- Bruce McMillan |
|
Christine I wasn't sure from your email if you were only interested in Metrowerks or other similiar systems. Here are my recommendations if you are considering more then Metorwerks... I have no affliation with any of the companies. www.imagecraft.com <http://www.imagecraft.com> - ImageCraft compiler ICC12 - has symbolic debugging for structures and very good on-line support. I have received support, even on weekends and up to 23:00 at night within an hour of posting a question. This is not something guaranteed as an after hours support contract, but if you ask a question, Richard always helps out. I have found the product and support excellent. All the popular processors are supported by imagecraft. You do need separate licenses for each compiler, however if you are working with the HC12 you would just use one license. www.noicedebugger.com <http://www.noicedebugger.com> - Noice, symbolic debugger with flash program - another excellent product. The cost is very reasonable, the GUI is well designed, and the code never crashes. Symbolic debugging for many compilers is supported. The IDE will also flash all the current HC12 products (the only exception I am aware of is the DP256, but that code is licensed from www.elektronicladen.de <http://www.elektronicladen.de> and is due out in the immediate future). John Hartman also provides excellent support and is willing to add features to the product if they are useful. He added a simple request I had on displaying address's in the memory window. The same debugger works for a very large number of processors and without any add on licensing. www.componentsoftware.com <http://www.componentsoftware.com> - Free code managaement software for single user use. I find it indespensible for keeping track of changes, and rolling back to various points to recheck operations (code that used to work, and now doesn't). Very simple to learn and implement. www.boxersoftware.com <http://www.boxersoftware.com> - Mulit-window editor written for programmers, the best editor I have used and again completely stable with no crashes. Supports many languages with color coding, really a professional product. Probably the best feature of the above products is the ease of use; it does not take days of setup to learn the environment. Metrowerks is also very good product if you need the HC05, HC08, HC12 as a common environment and have a team of people to integrate, the setup and number of features can be extensive. I tried Metrowerks, but found for my work on a single processor the above products have worked very well for me. Bob Lewis -----Original Message----- From: bobi [mailto:] Sent: Sunday, September 01, 2002 7:53 PM To: Subject: Re: [68HC12] Development boards in Australia www.sensair.com ----- Original Message ----- From: Christine Whybrow To: 68HC12 Sent: Monday, September 02, 2002 12:53 PM Subject: [68HC12] Development boards in Australia Hi All, Does anyone have an URL/Contact for anyone in Australia who supplies developmant boards or chips for the 68HC12? Does anyone have any preference for Metrowerks V ICC12 IDE's? Thanks for any assistance. Christine [Non-text portions of this message have been removed] Yahoo! Groups Sponsor ADVERTISEMENT -------------------------------------------------------- To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit http://www.motorola.com/mcu <http://www.motorola.com/mcu > . [Non-text portions of this message have been removed] |
|
|
|
Hi Bob, I finally gave up trying to make CodeWarrior work. Now I'm an ICC/NoICE devotee. I downloaded the Boxer editor and really like it. Thanks. It made it easy to change my code to be ICC compatible. I mostly like that it allows global searches other than before or after the cursor. The cursor-centric search always bites me. Do you integrate RCS and/or Boxer into ICC12? Bob White ----- Original Message ----- From: "Lewis, Bob" <> To: <> Sent: Tuesday, September 03, 2002 12:53 PM Subject: RE: [68HC12] Development boards in Australia > Christine > > I wasn't sure from your email if you were only interested in Metrowerks or > other similiar systems. Here are my recommendations if you are considering > more then Metorwerks... I have no affliation with any of the companies. > www.imagecraft.com <http://www.imagecraft.com> - ImageCraft compiler ICC12 > - has symbolic debugging for structures and very good on-line support. I > have received support, even on weekends and up to 23:00 at night within an > hour of posting a question. This is not something guaranteed as an after > hours support contract, but if you ask a question, Richard always helps out. > I have found the product and support excellent. All the popular processors > are supported by imagecraft. You do need separate licenses for each > compiler, however if you are working with the HC12 you would just use one > license. > > www.noicedebugger.com <http://www.noicedebugger.com> - Noice, symbolic > debugger with flash program - another excellent product. The cost is very > reasonable, the GUI is well designed, and the code never crashes. Symbolic > debugging for many compilers is supported. The IDE will also flash all the > current HC12 products (the only exception I am aware of is the DP256, but > that code is licensed from www.elektronicladen.de > <http://www.elektronicladen.de> and is due out in the immediate future). > John Hartman also provides excellent support and is willing to add features > to the product if they are useful. He added a simple request I had on > displaying address's in the memory window. The same debugger works for a > very large number of processors and without any add on licensing. > > www.componentsoftware.com <http://www.componentsoftware.com> - Free code > managaement software for single user use. I find it indespensible for > keeping track of changes, and rolling back to various points to recheck > operations (code that used to work, and now doesn't). Very simple to learn > and implement. > > www.boxersoftware.com <http://www.boxersoftware.com> - Mulit-window editor > written for programmers, the best editor I have used and again completely > stable with no crashes. Supports many languages with color coding, really a > professional product. > > Probably the best feature of the above products is the ease of use; it does > not take days of setup to learn the environment. Metrowerks is also very > good product if you need the HC05, HC08, HC12 as a common environment and > have a team of people to integrate, the setup and number of features can be > extensive. I tried Metrowerks, but found for my work on a single processor > the above products have worked very well for me. > > Bob Lewis > > -----Original Message----- > From: bobi [mailto:] > Sent: Sunday, September 01, 2002 7:53 PM > To: > Subject: Re: [68HC12] Development boards in Australia > www.sensair.com > ----- Original Message ----- > From: Christine Whybrow > To: 68HC12 > Sent: Monday, September 02, 2002 12:53 PM > Subject: [68HC12] Development boards in Australia > Hi All, > > Does anyone have an URL/Contact for anyone in Australia who supplies > developmant boards or chips for the 68HC12? > > Does anyone have any preference for Metrowerks V ICC12 IDE's? > > Thanks for any assistance. > > Christine > [Non-text portions of this message have been removed] > Yahoo! Groups Sponsor > ADVERTISEMENT > > > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu <http://www.motorola.com/mcu > > . > > > [Non-text portions of this message have been removed] > > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu |
|
|
|
> I finally gave up trying to make CodeWarrior work. Now I'm an ICC/NoICE > devotee. How odd. I could not get the new version of ICC12 working and am now being productive with CodeWarrior. I wonder what the differences are in each case. Regards, Paul |
|
Hi Paul, I'm glad you asked. I've been suppressing a rant for weeks now. I worked my way through CW, and it does have some nice features, once you figure out how to use them. Like a good map file, once you figure out how to turn it on, and if you don't have any errors (errors disable the map file - handy). My final problem is where I was trying to make my A/D converters come up, and discovered that the debugger was changing my DDRE register, where I am using a pin to control my sensor power supply. It was my final problem because it was the last straw. I've been fighting this battle for two months. CW help said to try disabling my interrupts to make the problem go away. It makes more sense to make the debugger go away. I left the code burned into the flash on my target hardware and booted up the NoICE debugger. Worked fine. It leaves my DDRE alone while debugging. It didn't take me two months to figure out how to use ICC and NoICE. I had both ICC12 and NoICE up and running in two days, most of this time spent editing my code to make it compatible with ICC12 conventions, mostly labels and assembler directives. This is quoted from Metrowerks customer support: " Please check that no external devise disturbs your board. Well, in BDM debugging mode, when you stop the application, the interrupts are still activated and you are no more in real-time. The problem you encountered seems to be a side effect of this limitation of debugging in BDM mode. What I suggest is in a first time debug your application without the interrupts. While debugging with the interrupts, you may have to adapt your code i.e. disabling the interrupts (macro Disableinterrupts in hidef.h) immediately after entering the interrupt routine and set the breakpoint at the next instruction. " The only interrupt I had enabled was the RTI. I've wasted about two months trying to use CW on old code. I kept trying because CW speaks the old HC11 assembly language and C that I am stuck with. I have a 1 inch notebook full of correspondence working through problems. I suppose I should say 25.4 mm., since it is Metrowerks data. If I didn't have a ton of code that I'm updating the hardware for, I'd never use a Motorola anything anymore. They cost too much, are in continual beta test, and are apparently designed by committee in various European countries. Maybe if I were starting a new project all in C and didn't care about the automatically generated code (and didn't need to use interrupts), CW would have worked for me. Best regards, Bob White ----- Original Message ----- From: "Paul Johnson" <> To: <> Sent: Tuesday, September 10, 2002 8:56 AM Subject: RE: [68HC12] Development boards in Australia > > I finally gave up trying to make CodeWarrior work. Now I'm an ICC/NoICE > > devotee. > > How odd. I could not get the new version of ICC12 working and am now being > productive with CodeWarrior. I wonder what the differences are in each > case. > > Regards, > > Paul > > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu |
|
|
|
> Probably the best feature of the above products is the ease of > use; it does > not take days of setup to learn the environment. Metrowerks is also very > good product if you need the HC05, HC08, HC12 as a common environment and > have a team of people to integrate, the setup and number of > features can be > extensive. I tried Metrowerks, but found for my work on a single processor > the above products have worked very well for me. This is very misleading. I do not have a team of people to integrate and I work on a single processor, yet I was being productive with Metrowerks within a couple of days. Also, the support for Metrowerks has been very good. The number of features is a good thing, but you don't need to know all the features to use the product. They do have significant problems with their documentation, and there are a couple of annoying bugs in the software, but the code quality is excellent. There is, of course, a BIG difference in price. If you can afford it, I think Metrowerks is worth the money. Regards, Paul Johnson |
|
Hi Bob, I'm glad you got that off your chest. I just think it's odd that our situations are so different. In my case, I wasted two or more months trying to get ICC12 and some debugger work with my 912DT128A. I never got it working. The final straw was that the copy protection on ICC12 Pro kept kicking in, even though I had a valid serial number, and it wouldn't let me run the program. The program would start up and then just disappear. I gave up and got Metrowerks, and I had a working system in under a week. It was painful converting all the ICC12 code to Metrowerks, there are some killer differences, but now that it's done everything is working great. BTW, you're right that BDM debugging with external interrupts (like msCAN) can be difficult. I wonder if this is a function of BDM programming or just of Metrowerks. Regards, Paul > -----Original Message----- > From: Bob White [mailto:] > Sent: Tuesday, September 10, 2002 12:17 PM > To: > Subject: Re: [68HC12] Development boards in Australia > Hi Paul, > > I'm glad you asked. I've been suppressing a rant for weeks now. > > I worked my way through CW, and it does have some nice features, once you > figure out how to use them. Like a good map file, once you figure out how > to turn it on, and if you don't have any errors (errors disable the map > file - handy). My final problem is where I was trying to make my A/D > converters come up, and discovered that the debugger was changing my DDRE > register, where I am using a pin to control my sensor power > supply. It was > my final problem because it was the last straw. I've been fighting this > battle for two months. > > CW help said to try disabling my interrupts to make the problem > go away. It > makes more sense to make the debugger go away. I left the code > burned into > the flash on my target hardware and booted up the NoICE debugger. Worked > fine. It leaves my DDRE alone while debugging. It didn't take me two > months to figure out how to use ICC and NoICE. I had both ICC12 and NoICE > up and running in two days, most of this time spent editing my > code to make > it compatible with ICC12 conventions, mostly labels and assembler > directives. > > This is quoted from Metrowerks customer support: > " > Please check that no external devise disturbs your board. Well, in BDM > debugging mode, when you stop the application, the interrupts are still > activated and you are no more in real-time. The problem you encountered > seems to be a side effect of this limitation of debugging in BDM mode. > What I suggest is in a first time debug your application without the > interrupts. While debugging with the interrupts, you may have to > adapt your > code i.e. disabling the interrupts (macro Disableinterrupts in hidef.h) > immediately after entering the interrupt routine and set the breakpoint at > the next instruction. > " > The only interrupt I had enabled was the RTI. > > I've wasted about two months trying to use CW on old code. I kept trying > because CW speaks the old HC11 assembly language and C that I am > stuck with. > I have a 1 inch notebook full of correspondence working through > problems. I > suppose I should say 25.4 mm., since it is Metrowerks data. If I didn't > have a ton of code that I'm updating the hardware for, I'd never use a > Motorola anything anymore. They cost too much, are in continual > beta test, > and are apparently designed by committee in various European countries. > > Maybe if I were starting a new project all in C and didn't care about the > automatically generated code (and didn't need to use interrupts), CW would > have worked for me. > > Best regards, > Bob White > > ----- Original Message ----- > From: "Paul Johnson" <> > To: <> > Sent: Tuesday, September 10, 2002 8:56 AM > Subject: RE: [68HC12] Development boards in Australia > > > I finally gave up trying to make CodeWarrior work. Now I'm > an ICC/NoICE > > > devotee. > > > > How odd. I could not get the new version of ICC12 working and am now > being > > productive with CodeWarrior. I wonder what the differences are in each > > case. > > > > Regards, > > > > Paul > > > > > > > > -------------------------------------------------------- > > To unsubscribe from this group, send an email to: > > > > > > To learn more about Motorola Microcontrollers, please visit > > http://www.motorola.com/mcu > > > > > -------------------------------------------------------- To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit http://www.motorola.com/mcu |
|
|
|
Paul, I think I have the answer to your question; "BTW, you're right that BDM debugging with external interrupts (like msCAN) can be difficult. I wonder if this is a function of BDM programming or just of Metrowerks." I believe this is due solely to the BDM. When in BDM, the target is essentially in a STANDBY, or pseudo-RUN mode, which causes program execution cycles to be spaced out by BDM instructions in between. This makes program instruction execution occur at a rate far less than normal -- appearing to the outside as if the clock were slowed down substantially. However, all the real-time interfaces are running full speed, as are outside devices. Thus, it is nearly impossible to debug in real time, since the RTI occurs after significantly fewer program instruction cycles than it would in normal operation -- same goes for outside interrupts; MsCAN, SPI, SCI etc. I am working with an application that requires a 200ms response timeout on the SCI, so in BDM mode the external device always timesout before it receives the response. Anyway, I hope that answers your question, even if it was rhetorical. --Adam ----- Original Message ----- From: Paul Johnson To: Sent: Wednesday, September 11, 2002 12:18 PM Subject: RE: [68HC12] Development boards in Australia Hi Bob, I'm glad you got that off your chest. I just think it's odd that our situations are so different. In my case, I wasted two or more months trying to get ICC12 and some debugger work with my 912DT128A. I never got it working. The final straw was that the copy protection on ICC12 Pro kept kicking in, even though I had a valid serial number, and it wouldn't let me run the program. The program would start up and then just disappear. I gave up and got Metrowerks, and I had a working system in under a week. It was painful converting all the ICC12 code to Metrowerks, there are some killer differences, but now that it's done everything is working great. BTW, you're right that BDM debugging with external interrupts (like msCAN) can be difficult. I wonder if this is a function of BDM programming or just of Metrowerks. Regards, Paul subject to the Yahoo! Terms of Service. |
|
|
|
At 09:18 AM 9/11/2002 -0700, Paul Johnson wrote: >Hi Bob, > >I'm glad you got that off your chest. I just think it's odd that our >situations are so different. In my case, I wasted two or more months trying >to get ICC12 and some debugger work with my 912DT128A. I never got it >working. The final straw was that the copy protection on ICC12 Pro kept >kicking in, even though I had a valid serial number, and it wouldn't let me >run the program. The program would start up and then just disappear. >... Paul, please allow me to butt in. We have lots and lots of customers. In fact, I bet we have at least 10x the customers of Metrowerks on the HC12. Once in a while, we have customers who are very experienced in the industry, and are very bright, etc. but just for whatever reasons, have problems with our products. We try our best to help, but sometimes it just cannot be help that there are unsatisfied customers. We learn our lessons and try to improve our products so it won't happen again. We offer generous refund policy. After all, happy customers are our best marketing tool, and it is no good to have unhappy ex-customers. So to the point, I am happy that you are happy with Metrowerks, but I can assure that we have sold many many copies ICC12 PRO and most people do use our products and not just sit them on the shelves, and they are happy as well. As I recall, the DG128/DT128 were new when you were started using them, and besides any issues with the ICC12 compiler, there were issues that were beyond our control: 1) NoICE12 was just getting the features to burn FLASH directly... 2) I forgot which vendor of the BDM-12 Pod you were using, but there were some issues with the S-records generated and the ones expected by some vendors. Don't get me started on this one :-) I must have vented about the whole fiasco of S-record types and paging on the HC12 thousands of times, even on this list :-) The upside is that now there are several converters, from Motorola and from P&E, and that we support BOTH linear and banked S2, and all sort of funky mappings of last pages to S2, all because,... well, I shouldn't vent again :-) // richard http://www.imagecraft.com [ For technical support, please include all previous replies in your msgs. ] |
|
|
|
Richard, I try to be very careful not to imply that there is anything wrong with ICC12, or any ImageCraft products. That's why I said that Bob's situation and mine was odd, and kind of interesting. You're absolutely right about the issues that I was dealing with at the time. I know that you have many happy customers and the combination of tools (ICC12, NoIce, Somebody's BDM) is an effective tool. I never meant to imply otherwise. Still, I am happy with the Metrowerks toolset and find the support very responsive. Each tool has a legitimate place in the market. Best regards, Paul Johnson > -----Original Message----- > From: Richard F. Man [mailto:] > Sent: Wednesday, September 11, 2002 1:11 PM > To: ; > Subject: [68HC12] RE: Metrowerks vs. ImageCraft, Again [was Development > boards... > At 09:18 AM 9/11/2002 -0700, Paul Johnson wrote: > >Hi Bob, > > > >I'm glad you got that off your chest. I just think it's odd that our > >situations are so different. In my case, I wasted two or more > months trying > >to get ICC12 and some debugger work with my 912DT128A. I never got it > >working. The final straw was that the copy protection on ICC12 Pro kept > >kicking in, even though I had a valid serial number, and it > wouldn't let me > >run the program. The program would start up and then just disappear. > >... > > Paul, please allow me to butt in. We have lots and lots of customers. In > fact, I bet we have at least 10x the customers of Metrowerks on the HC12. > Once in a while, we have customers who are very experienced in the > industry, and are very bright, etc. but just for whatever reasons, have > problems with our products. We try our best to help, but > sometimes it just > cannot be help that there are unsatisfied customers. We learn our lessons > and try to improve our products so it won't happen again. We > offer generous > refund policy. After all, happy customers are our best marketing > tool, and > it is no good to have unhappy ex-customers. > > So to the point, I am happy that you are happy with Metrowerks, but I can > assure that we have sold many many copies ICC12 PRO and most > people do use > our products and not just sit them on the shelves, and they are happy as > well. As I recall, the DG128/DT128 were new when you were started using > them, and besides any issues with the ICC12 compiler, there were issues > that were beyond our control: > > 1) NoICE12 was just getting the features to burn FLASH directly... > 2) I forgot which vendor of the BDM-12 Pod you were using, but there were > some issues with the S-records generated and the ones expected by some > vendors. Don't get me started on this one :-) I must have vented > about the > whole fiasco of S-record types and paging on the HC12 thousands of times, > even on this list :-) The upside is that now there are several > converters, > from Motorola and from P&E, and that we support BOTH linear and > banked S2, > and all sort of funky mappings of last pages to S2, all > because,... well, I > shouldn't vent again :-) > // richard http://www.imagecraft.com > [ For technical support, please include all previous replies in > your msgs. ] > > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu |
|
|
|
If the BDM on the HC12 is issued a GO command, the processor runs at full speed. The exception to this is real time memory reads/writes, while the HC12 is running. In this case the BDM Hardware (no software involved) tries to grab an unused memory cycle to do the read/write. If it can not find a dead cycle within 128 cycle, it steals a cycle. This can slow the cpu down slightly. All the BDM hardware based commends operate without slowing down the cpu with the exception of cycle stealing for memory reads and writes. If you halt the processor, i.e., when BDM ie active. Then no user instructions are executed. BDM software commands are then usable. However, autonomous peripherals keep running such as the SCI, etc., since you can not stop a transfer in the middle of a character. Other hardware peripherals, such as the timer, may be stopped when making BDM software commands active. There are control bits in the peripheral registers for doing this such as the TSFRZ bit in the Timer control register for the 9S12DP512. Regards Dave Perreault Adam Wofford wrote: > Paul, > > I think I have the answer to your question; "BTW, you're right that BDM > debugging with external interrupts (like msCAN) can be difficult. I wonder > if this is a function of BDM programming or just of Metrowerks." > > I believe this is due solely to the BDM. When in BDM, the target is > essentially in a STANDBY, or pseudo-RUN mode, which causes program execution > cycles to be spaced out by BDM instructions in between. This makes program > instruction execution occur at a rate far less than normal -- appearing to > the outside as if the clock were slowed down substantially. However, all > the real-time interfaces are running full speed, as are outside devices. > Thus, it is nearly impossible to debug in real time, since the RTI occurs > after significantly fewer program instruction cycles than it would in normal > operation -- same goes for outside interrupts; MsCAN, SPI, SCI etc. I am > working with an application that requires a 200ms response timeout on the > SCI, so in BDM mode the external device always timesout before it receives > the response. > > Anyway, I hope that answers your question, even if it was rhetorical. > > --Adam > > ----- Original Message ----- > From: Paul Johnson > To: > Sent: Wednesday, September 11, 2002 12:18 PM > Subject: RE: [68HC12] Development boards in Australia > > Hi Bob, > > I'm glad you got that off your chest. I just think it's odd that our > situations are so different. In my case, I wasted two or more months trying > to get ICC12 and some debugger work with my 912DT128A. I never got it > working. The final straw was that the copy protection on ICC12 Pro kept > kicking in, even though I had a valid serial number, and it wouldn't let me > run the program. The program would start up and then just disappear. > > I gave up and got Metrowerks, and I had a working system in under a week. > It was painful converting all the ICC12 code to Metrowerks, there are some > killer differences, but now that it's done everything is working great. > > BTW, you're right that BDM debugging with external interrupts (like msCAN) > can be difficult. I wonder if this is a function of BDM programming or just > of Metrowerks. > > Regards, > > Paul > > subject to the Yahoo! Terms of Service. > -------------------------------------------------------- > To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit > http://www.motorola.com/mcu |
|
|
|
At 01:37 PM 9/11/2002 -0700, Paul Johnson wrote: >Richard, > >I try to be very careful not to imply that there is anything wrong with >ICC12, or any ImageCraft products. That's why I said that Bob's situation >and mine was odd, and kind of interesting. ... Understood, and actually Bob would normally be a "problem case" since he is converting lots of assembly code over. That always gives me an un-fuzzy feeling since different assembly/linker have different syntax and assumptions etc. I am glad that he got it working to his satisfactions. // richard http://www.imagecraft.com [ For technical support, please include all previous replies in your msgs. ] |