Sign in
Search 68hc12
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
Sponsor
Ads
Discussion Groups
See Also
Discussion Groups | 68HC12 | .eeprom segment
Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).
.eeprom segment - Steve Henck - Sep 20 19:45:00 2004
|
Hello. I finally got my serial bootloader to work on the mc9s12a256b. OK. So I take the application that I'm trying to load, move the vectors, recompile and run it through SRecCvt. SRecCvt doesn't like the ".eeprom" segment created by the linker because it's outside the c0000 to fffff address space. Now, the program to be loaded is in C and uses the Cosmic "@eeprom" to define some variables in eeprom (hence the ".eeprom" segment), but doesn't actually load anything into eeprom when loaded with the BDM, so I tried moving the ".eeprom" segment to Flash and I also tried excluding it from processing by SRecCvt by naming all the segments except it with the -n option. In both cases, the program loads with the bootloader and runs fine after loading, but none of the variables defined with @eeprom get stored to eeprom. I know the bootloader only programs flash, but since the variables defined with @eeprom are just variables with no value at compile time is there any workaround? I know I can change the program to be loaded to write to eeprom directly instead of using @eeprom variables but it's an application which has been validated for a medical instrument and would have to undergo new validation. Any suggestions? Regards, Steve Henck |
(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )