27c256 | 4K81H | 68HC11A1 | 68HC11P1 | 68hc24 | 68HC711E9 | 68HC811 | 8255 | A2D | ADC | ADC12138 | Am85C30 | BRCLR | Buffalo | CMOS | EEPROM | EPROM | Ethernet | EVB | EVBU | HC11E1 | HC11E9 | HC711E9 | Horray | ImageCraft | IRQ | Keypad | LCD | MC68HC11D0FN | MC68HC11E1CFU3 | MC68HC11F1 | MC68HC711E9 | MC68HC711E9CFN2 | Microcore11 | Microstamp11 | Minikit | NVRAM | PSD | PSD8xx | PSD9xx | PT1000 | RS232 | RTS | RXD | SPI | SRAM | TXD | Watchdogs | XIRQ

I have a 68HC11A1FN microcontroller running at 8Mhz on a MRC-11 board by www.mekatronix.com with 64K ram. Trying to get programs compiled with GNU, loading them, and them getting them to run has been to say the least a pain. I'm about ready to just stick with assembler as I know what it's going to do and when. They work fine in the GNU debugger but loading and running is another story. I've tried loading them using HCload and JBug11 which others seem to be using but the program doesn't want to run. When you intermix all the command line options in GNU, your loader program quirks, and then your board quirks it's fun. I wondered if anyone else was using GNU with something like JBug? If so got any ideas? Michael

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


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

Have you looked at your listing and/or .s19 files to make sure they look reasonable? Emmett Redd Ph.D. mailto: Associate Professor (417)836-5221 Department of Physics, Astronomy, and Materials Science Southwest Missouri State University Fax (417)836-6226 901 SOUTH NATIONAL Dept (417)836-5131 SPRINGFIELD, MO 65804 USA > -----Original Message----- > From: Michael Monteith [mailto:] > Sent: Tuesday, October 26, 2004 2:18 PM > To: > Subject: [m68HC11] Anyone Using Gnu 68HC11 with 68HC11A1 w/64k? > > > I have a 68HC11A1FN microcontroller running at 8Mhz on a MRC-11 > board by www.mekatronix.com with 64K ram. Trying to get programs > compiled with GNU, loading them, and them getting them to run has > been to say the least a pain. I'm about ready to just stick with > assembler as I know what it's going to do and when. > > They work fine in the GNU debugger but loading and running is > another story. I've tried loading them using HCload and JBug11 which > others seem to be using but the program doesn't want to run. > > When you intermix all the command line options in GNU, your loader > program quirks, and then your board quirks it's fun. > > I wondered if anyone else was using GNU with something like JBug? > If so got any ideas? > > Michael > ------------------------ Yahoo! Groups Sponsor > Yahoo! Groups Links

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

Emmett, Yeah, I compared it to a similar program that does work and it looks like what I would expect. I'll just have to sit down and look at the listing and the s.19 to see what might be going on. I hope it's something simple and a one-time duhhh type thing. Just didn't want to reinvent the wheel if someone has already been this route. Thanks Michael --- In , "Redd, Emmett R" <err557f@s...> wrote: > Have you looked at your listing and/or .s19 files to make sure they look > reasonable? > > Emmett Redd Ph.D. mailto:EmmettRedd@s... > Associate Professor (417)836-5221 > Department of Physics, Astronomy, and Materials Science > Southwest Missouri State University Fax (417)836-6226 > 901 SOUTH NATIONAL Dept (417)836-5131 > SPRINGFIELD, MO 65804 USA

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

> Yeah, I compared it to a similar program that does work and it > looks like what I would expect. I'll just have to sit down and look > at the listing and the s.19 to see what might be going on. I hope > it's something simple and a one-time duhhh type thing. Just didn't > want to reinvent the wheel if someone has already been this route. You mentioned that you were testing your target using JBug - bear in mind that this application uses bootstrap mode, and in bootstrap mode, interrupt and reset vectors are handled differently. I have only just started looking at the GNU tools for the HC11, but one thing I have noted is that there are different includes and build options depending on whether you are building your app for normal, special test, or bootstrap/pseudovector mode. Unfortunately, I have not done sufficient experimentation/research yet to tell you exactly what must be done in terms of invocation or build options, but I do know that /something/ has to be done... I do not know if it is possible to set up the compile environment in such a way as to support all three interrupt vectoring variants (normal vector table at FFC0, special test vector table at BFC0, pseudovector jump table in RAM for bootstrap/monitor mode) but it would be nice if one could enable support for generating appropriate code for all three - this way one's app would work regardless of run mode. I guess I'll find out when I have a chance to work with the GNU HC11 tools some more. -- Mark

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