| View previous topic :: View next topic |
| Author |
Message |
curt2go
Joined: 21 Nov 2003
Posts: 200
|
| SD Card Bootloader |
 Posted: Thu May 31, 2018 8:49 am |
 |
|
I have gotten the SD card bootloader from Brush Electronics. As a side note he is an awesome guy willing to help out with hiccups along the way.
I am using a 24EP256GP206 chip running at 140MHz. I am trying to get the SD card bootloader working on this chip but running into difficulties. The EP chips have different paging and writing compared to other 24 series chips.
The issue is that it seems to be erasing the reset vectors and not replacing them properly when writing with the boot loader. We have worked through some issues where we were overwriting a lot of stuff and not ending up with anything that resembles what its supposed to . Right now the bootloader is staying in tact and it is placing the PGM code into the correct places that it should.
It is placing the bootloader from 0x800 to 0x3FFF.
The PGM is being placed above that i have an #org in my code that is 0x400,0x47FF to make room for the bootloader.
If Brush is around he may be able to better explain than I have. But has anyone had experience with bootloader on 24EP devices? I think its something simple at this point but Brush has been able to help me so far but we are stuck right now. So just looking to see if there is any tidbits we may be missing. I know there is probably not enough info here to go on but I really need to put this to bed. Thank you as always for all your guys help. |
|
 |
temtronic
Joined: 01 Jul 2010
Posts: 9093
Location: Greensville,Ontario
|
|
| Posted: Thu May 31, 2018 8:59 am |
|
|
hmm.. maybe cause it's hot and muggy
but...
The PGM is being placed above that i have an #org in my code that is 0x400,0x47FF to make room for the bootloader.
shouldn't it be 0x4000, and not 0x400 ?
hopefully just a type here and not in the code.... |
|
|
asmallri
Joined: 12 Aug 2004
Posts: 1630
Location: Perth, Australia
|
|
| Posted: Thu May 31, 2018 9:09 am |
|
|
| temtronic wrote: | hmm.. maybe cause it's hot and muggy
but...
The PGM is being placed above that i have an #org in my code that is 0x400,0x47FF to make room for the bootloader.
shouldn't it be 0x4000, and not 0x400 ?
hopefully just a type here and not in the code.... |
Curt2go actually means he has an excluded region from 0x0400 to 0x47FF, using the org statement, to prevent the CCS compiler from putting the user application code in the space.
_________________
Regards, Andrew
http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!! |
|
|
temtronic
Joined: 01 Jul 2010
Posts: 9093
Location: Greensville,Ontario
|
|
| Posted: Thu May 31, 2018 10:24 am |
|
|
| OK, I re-read the OPost...and NOW it makes sense. It just looked to me like he'd had the PGM loaded into the same area as the bootloader. |
|
|
Ttelmah
Joined: 11 Mar 2010
Posts: 19215
|
|
| Posted: Thu May 31, 2018 1:49 pm |
|
|
what #build is being used on the code to load?.
This is what defines it's reset vectors etc.. |
|
|
asmallri
Joined: 12 Aug 2004
Posts: 1630
Location: Perth, Australia
|
| solved |
| Posted: Sat Jun 02, 2018 11:24 am |
|
|
| Ttelmah wrote: | what #build is being used on the code to load?.
This is what defines it's reset vectors etc.. |
The issue has been fixed, it was a datasheet error.
_________________
Regards, Andrew
http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!! |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
