Technical discussions about Freescale Microcontrollers: M68HC11. (Freescale Semiconductor is a Subsidiary of Motorola).
|
--- In , "jackson_cp" <jackson_cp@y...> wrote: > We are very thankful to you for your kind response, > > I have experimented with the idea what you have given. But this > time also I could not succeed. I have created the assembly file > (. REC) and the file added to the macro. > > When I have rebooted the board the macro is loaded. But after that > when I have tried to load a .s19 file which has got a interrupt > vector table it gave me a message "Current value of BPROT is > ($1F) may not allowing to write to EEPROM" > > If I change the BPROT register it will write the ISR vector to > EEPROM You need to change the JBug memory-mapping settings for EEPROM. If you go to the Settings/Memory Map tab, you will see a memory range specified for EEPROM (look in lower left hand corner of the dialog). The default value for the F1 is FE00..FFFF. This setting is used by JBug to determine when it should use the EEPROM programming method (as opposed to a simple memory write) when changing/loading a given memory location. If you followed the procedure I outlined previously, your EEPROM should now be mapped to a location other than FE00..FFFF (or out of the map entirely if you set EEON=0 in CONFIG). JBug needs to be informed where the EEPROM has been relocated to. Put the correct range (as per your CONFIG settings) in the space provided, or delete the entry entirely if you've removed the EEPROM from the memory map. Don't forget to save your settings after you finish. FYI, JBug uses a prioritization mechanisim when determining which algorithmn(s) to use to program various memory types. Generally, this priority mechanisim gives precedence to internal resources (such as EEPROM, control registers, internal RAM and EPROM/OTPROM) over external resources (e.g. FLASH, external RAM). This reflects the same priority mechanisim that the HC11 uses. The PDF manual that comes with the JBug package discusses this, along with many of the other issues we've discussed recently (hint, hint ;) |