On 30/01/2015 14:15, "M L" <maricol...@gmail.com> wrote: >Hi, >I don't really get it, why You trying (so hard) use a bootloader which >won't fit in boot block, so what? >Bootloader can be with any size, just move user code to location >after bootloader (to first free block of flash erase boundary). > >If size of user code+bootloader won't fit into device - choose another >pic with bigger flash or choose a compiler which produce smaller code >- what is the problem?
First of all, I'm talking about existing code and hardware. The existing code (without the bootloader) already pretty much fills the PIC18F4550. I can't just willy-nilly move to a bigger device, there is existing hardware on the field. I don't think there is a bigger device that is close to PIC18F4550 so the bigger device would also mean more than just pop in a new chip, likely PCB changes and more in hardware and software. Better compiler? Yeah, that is an option. However when I toyed with this idea my SDCC optimised code did not compile without mods with Microchip compilers. To get a reference point I compared the compiled size of the Free M-stack and my own HID stack and the size of the M-stack compiled with Microchip was twice the size of my own compiled with SDCC. Not a fair comparison but not an encouraging sign either. >Currently I'm using own usbbootloader with xtea encrytption, which >takes about 10kB in size and I'm pretty happy with it. The Diolan bootloader fits in the smaller 1kB boot block... >Writing such >bootloader is trivial job and it takes a couple of minutes. Seriously? >I think >You wasted more time trying to find solution how to fit it than trying >to write a new, custom bootloader, which meets all Your requirements. Seriously? I don't think I've wasted any time yet, except answering your comment. I took a Free and battle tested bootloader that fitted all my requirements and posted a message here to ask about the extended instruction set issue. I then learned that the extended instruction set usage is a non-starter so I used a few hours to convert the bootloader (see I'm not as fast as you who could have written that from scratch in the time it takes me to type this message) to non-extended instruction set and I expect to put in a few more hours to debug it to make it work. > >Other question is about extended instruction set and which compiller is >better. >As someone mention before even Microchip abandoned support of extended >instruction set, so it's not worth to use it. That was a very valuable info point, thanks again Jesse. br Kusti This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
