Thanks! I actually successfully used the .ld file from the mpide directory in mplab and it worked fine (using the mplab linker).
It seems that's exactly what I'm trying to do!
Can you attach a mplab skeleton project with the linker script?
If I'm right, you can write code in mplab, create a .hex file with the proper linker script (in order not to override the bootloader flash space) and transfer via avrdude to the board. Isn'it.
I'd like to do this with my uno32 board for 2 reasons:
- while I'm debugging, I keep using pickit3 for breakpoints and other stuffs
- I'd like to update my firmware via USB, because the board is in a waterproof case with only USB available (not the icsp connector) and i cannot open it for firmware updates.
Do you know if there is a wiki page or a tutorial on that? (my google searchs aren't very successful on that point...)
It seems that the linker script file chipKIT-UNO32-application-32MX320F128L.ld doesn't properly work with MPLAB 8.80 and my uno32 board:
Avrdude is ok until it checks fuses then I have a bad checksum error.
If I uncheck the linker option "don't link startup code", avrdude is ok but I cannot start the application, of course.
I will check and compare hex files to see if something is missing, but at the time nothing obvious.
I probably have to switch to MPLAB X.
An other path to explore:
Maybe it would be easier to learn how to write my code under mpide in plain C rather than writing my application in MPLAB and try to link it with the pre-programmed bootloader.
What do you think about that?