 |
 |
| View previous topic :: View next topic |
| Author |
Message |
Hans Wedemeyer
Joined: 15 Sep 2003
Posts: 226
|
| What is programmed at address 0X0020000 ? |
 Posted: Wed Sep 19, 2007 9:07 am |
 |
|
Chip PIC18F6720
What is programmed at address 0X0020000 ?
:020000040020DA
:0800000004F00EF007F000F01F
I know #rom 0X2100 is a way to put data into the chips data eeprom |
|
 |
Ttelmah
Guest
|
|
| Posted: Wed Sep 19, 2007 9:39 am |
|
|
Er. 0x2100, is _not_ the way to put data into your chip's EEPROM. Read again. 0x2100, is the address for _16_ chips....
0-0x1FFFF, is the program memory for this family
0x20000, is the start of the ID space.
0x30000, is the configuration data
0xF0000, is the EEPROM
Best Wishes |
|
|
Hans Wedemeyer
Joined: 15 Sep 2003
Posts: 226
|
|
| Posted: Wed Sep 19, 2007 9:47 am |
|
|
| Ttelmah wrote: | Er. 0x2100, is _not_ the way to put data into your chip's EEPROM. Read again. 0x2100, is the address for _16_ chips....
0-0x1FFFF, is the program memory for this family
0x20000, is the start of the ID space.
0x30000, is the configuration data
0xF0000, is the EEPROM
Best Wishes |
Thanks for the clarification.
Another question on that same subject:
My boot loader has this data at 0x20000
:020000040020DA
:0800000007F007F00CF002F01C
The application code to be loaded by the boot loader has this at 0x20000
:020000040020DA
:0800000000F00EF006F00FF015
Should the bootloader replace the data at 0x20000 with the application data ?
And will the bootloader still run ? |
|
|
Ttelmah
Guest
|
|
| Posted: Wed Sep 19, 2007 10:00 am |
|
|
ID space, is for you to put what you want. The idea is that you can put identifer data (perhaps of the code version), here. You _can_ check what is here from your code, so the bootloader, could check this, but unless there is such a 'check', the ID space has no 'functionality' as such. You can change the ID values, with the #ID directive. The default value put here, is a checksum. Unless you are using the ID for something, you might as well leave the bootloader values there.
Best Wishes |
|
|
Hans Wedemeyer
Joined: 15 Sep 2003
Posts: 226
|
|
| Posted: Wed Sep 19, 2007 10:21 am |
|
|
| Ttelmah wrote: | ID space, is for you to put what you want. The idea is that you can put identifer data (perhaps of the code version), here. You _can_ check what is here from your code, so the bootloader, could check this, but unless there is such a 'check', the ID space has no 'functionality' as such. You can change the ID values, with the #ID directive. The default value put here, is a checksum. Unless you are using the ID for something, you might as well leave the bootloader values there.
Best Wishes |
Great at least that is not the reason why my boot loader fails
I'm coming to an end with the boot loader issue, simply run out of options.
App Code that is loaded by the boot loader is 100% correct. Confirmed by comparing hex files.
The transplanted Vector is working. Confirmed by the debugger PC value and a dump of the transplanted reset vector through serial connection.
The app. interrupt vectors are in place.
With all of that the application will not start when loaded by the boot loader... Arrrrrrrrgh! so close... yet so far away.. ! |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
