You do not really need a bootloader section to have a bootloader, if the avr has self programming modify the reset vector should do the trick. Have a look at this; http://jtxp.org/tech/tinysafeboot_en.htm Don't say it's easy or user friendly, but it works.
Thx for advice. I removed all commands in relation to the LEDs in the bootloader, recompiled and loaded into flash memory via ISP. Message from uploading of the bootloader see MCSBootL_Message.jpg. Does it matter when the message says that 15872 bytes are written and a bit earlier 15818 bytes are loaded into FLASH buffer ? Checked again content vs. buffer result o.k.
MCSBootLoad1.jpg shows the setting of the bootloader. ARE THE FUSES SET CORRECTLY: ESP: FUSEBIT EXTENDED Q
It looks that the bootloader code is stored at H3800. In the MCS bootloader I indicated Loaderchip =168 and $Loader =$1c00. (see MCSBootLoad2.jpg) The used $regfile is m168def.dat. Fits to the chipID. The parameters for the MCS bootloader are set to bootsize =1924 and reset = NONE. Then uploaded application program via MCS bootloader. Uploading seems o.k. Downloading the Flash memeory via the ISP Programme showed that th flah meory has a new content. Message from uploading was Loader returned: 123 Uploading Finish code:0 Trying to run the application program -> no success.
Long time ago i have problem with MCS Bootloader with M328P (simillar to smaller 168P) Problem was that MCS Bootloader uses two or three LED`s for showing the progress.. It was some of the INT0 pins if I remember fine. To solve this problem I must comment using those LED`s in the Bootloader or config ports again in my aplication after Boot.
Dear All, I loaded my application program via the MCS bootloader into ATMEGA168. Successfully But: My application program did not start. After loading the application program via the ISP programmer the application programs started well. I want to keep the processor in it environment and modify the software via RS232.
My assumption is that there is something wrong with the fusebits or the boot vector. In the application program I set the fuse bits to
$prog &HFF , &HE7 , &HDF , &HF8 With &HF8 I set the bootsize to 1024 words and Fusebit extended Q to select Boot vector.
For the MCS loader I put the parameters for boot size to 1024, Reset NONE
What may be wrong ? Pls be so kind to advice. BR Chris
[b:a9e21d4248][color=red:a9e21d4248](BASCOM-AVR version : 188.8.131.52 , Latest : 184.108.40.206 )[/b:a9e21d4248][/color:a9e21d4248]
[quote="Evert "]Max default clock speed for a sd card is 48Mhz. If you power up an sd-card it will always work on 3.3V, 1 bit bus and max. 45mhz clock. This to make all the new fast cards downwards compatible. If you want a higher clock speed, lower voltage (1.8V) or change bus width you have to negotiate with the card to change the settings. Ask the card what he (or she) is capable of and then change the settings.
I did it in C, but never in Bascom. Hope you can find some examples else it's a long way to go.
Hi evert, thanks for your advice, i will try to replace the logic converter for sd card.