Update Program from Card

Tubeampman · Joined: 27 Feb 2006 Posts: 100 Location: Bodo

Hi

I believe as long as the fusebit for resetvector is set to bootloader, the bootloader will be persist.

Fixmann

Tubeampman · Joined: 27 Feb 2006 Posts: 100 Location: Bodo

Hi

I was thinking to make a bargraph in the lcd to tell how many percent of
the progran that has been completed/uploaded from the hex on the SD-card.
Is there some variables/information that can be used in the bootloader for this task? (read the total size of the hex minus a counter of some sort?)

regards
Tubeampman

reinhars · Joined: 29 Nov 2009 Posts: 114

There is a Bargraph function in the aes bootloader:
http://mcselec.com/index2.php?option=com_forum&Itemid=59&page=viewtopic&t=9672

njepsen · Joined: 13 Aug 2007 Posts: 469

I have an SD card connected as per the docs ( MOSI,MISO, ck & SS to cs ) to a 1284P.
The bootloader appears to be running and I get an err MSG: BCeE1M which I am at a loss to understand.
The hardware is OK because I have been reading and writing to the SD card for several months, every 15minutes.

I'll post my settings & connections.

I don't seem to be allowed to cut & paste my code ?? Serve meg = post2 not allowed or similar.
What do the code, quote and list icons do?

]

njepsen · Joined: 13 Aug 2007 Posts: 469

Ajaxelectronic · Joined: 22 Nov 2009 Posts: 171 Location: Iran

Hi

i try DOS_Boot2 project with ATMega128 and all things was ok.

now i want to use INT0 or other INTs for Starting Bootloading but i can't write a correct program that work nice.

how can i use INTs for update my firmware?

Evert :-) · Joined: 18 Feb 2005 Posts: 2156

Something like this;

Ajaxelectronic · Joined: 22 Nov 2009 Posts: 171 Location: Iran

thanks Evert

i tested it and work nice. Smile

toto · Posted: Sat Mar 23, 2013 2:44 pm Post subject:

Hello,

I using the Bootloader from Josef to update the firmware trough SD card. I can compile it and works fine if i use $include "Config_MMC.bas"

But now i need to use 4 Gb card, so i changed on the bootloader code to $include "Config_MMCSD_HC.bas"
The compiler show the folling error lines:
Error:344 line: 521 Program will overwrite bootloader [36 to long]
Error: 61 Line: 521 Label not found [_RAMPZ4 ]

This is what i have in the code to define
$regfile = "m2560def.dat"
Const Loaderchip = 2560
#if Loaderchip = 2560 ' Mega2560
$baud = 9600
$loader = &H1F000 ' 4096 words
Const Maxwordbit = 7 'Z7 is maximum bit '
Const Loadsize = &H1F000 * 2 ' <=== modified, it is ok.?? highest Number of bytes to load
#endif

$crystal = 8000000
$hwstack = 128
$swstack = 128
$framesize = 128

Joseph can help? or anyone else know what i make wrong?

Thanks in advance
Best regards
toto

toto · Posted: Mon Mar 25, 2013 5:36 pm Post subject:

Hello,

I have shrink the bootloader. Delete a few writeeprom lines that not comes with the bootloader, and it compile fine 99% again
With sd card of 256kb it works great but not with 4gb sd card.
It shows always Gbdriveerror value 233

This is a config_MMCSD_HC.bas that i use for Atmega2560
Const Cmmc_soft = 0
#if Cmmc_soft = 0
' --------- Start of Section for HW-SPI ----------------------------------------
''Portd_pin6ctrl = &B00_011_000
' define Chip-Select Pin
Config Pinf.1 = Output
Mmc_cs Alias Portf.1
Set Mmc_cs
Config Portb.0 = Output
Spi_ss Alias Portb.0
Set Spi_ss

'FOR XMEGA DEVICES
#if _xmega = 1
#else

' HW-SPI is configured to highest Speed
' Config Spi = Hard , Interrupt = Off , Data Order = Msb , Master = Yes , Polarity = High , Phase = 1 , Clockrate = 4 , Noss = 1
Config Spi = Hard , Interrupt = Off , Data Order = Msb , Master = Yes , Polarity = High , Phase = 1 , Clockrate = 16 , Noss = 1
'Spsr = 1 ' Double speed on ATMega128
Spiinit
#endif
' --------- End of Section for HW-SPI ------------------------------------------
#else
#if _xmega
' Portd_pin6ctrl = &B00_011_000
#endif
#endif
'========== End of user definable range

Any idea why not works?

Thanks in advance
toto

njepsen · Joined: 13 Aug 2007 Posts: 469

Hi Adrian,
you said a long time ago

Paulvk · Joined: 28 Jul 2006 Posts: 1257 Location: SYDNEY

Could you number the image files , you update a eeprom entry to that number and set another eeprom byte to indicate ok for that number so if it fails you can see the number with no ok flag so load present ok file, you will also need an entry for present ok .

Needs a bit more logic but I hope you get my thinking

Regards Paul

njepsen · Joined: 13 Aug 2007 Posts: 469

Hi Paul
If it fails, I lose sms contact with the remote unit. If the bootload works OK, I have a raft of sms commands and questions I can ask it ( including starting a bootload) but if the bootload were to fail, then i am blind. But worse than that, the program will also be corrupt, and the only code that would run is the bootloader.
Perhaps ... no that wont work.

AdrianJ · Joined: 16 Jan 2006 Posts: 2483 Location: Queensland

@njepsen
What I originally meant was that you should always go to the bootloader on a reset - eg on power up. That way, if the main program totally fails, you can still activate the bootloader and get a new program to load. Many people just put a jump to the bootloader within the main program, triggered by some event, eg a serial command, or switch closure. But then if the main fails, that jump can never be executed.

That is not the same as your scenario though. I know of no really secure way to load a new program, and recover from a failed load. The problem is that there is nowhere within the processor to hold a full copy of the new code as it comes in, and verify that it is valid, before installing it in Flash. The best I have ever managed is to put a very good checksum on the program, and verify that it is valid before starting the flash load.

I use a SHA1 512 bit hash key for the checking and validation, which seems pretty foolproof. The procedure is to create ( and in my case also encrypt ) the program hex file and append the hash to that. Then the bootloader reads that file from the SD card, decrypts it, and computes its own hash and checks that it matches the embedded hash. If that matches, we go ahead to upload the file to flash. I also change the filename on card, so that we dont reload it again. But much later I realised that can lead to your problem too. What I do now is to save the program file system date in eeprom, and compare any files on the card with that date. If the card contains a later date, I load that program into flash. That way I can just simply issue a new program, and all devices will update themselves with no other intervention. Never had that fail yet. But I can see that if a user screws something up, like remove the card or power down during an upload, bad things could still happen. In that case, the user incurs the cost of a service.