2011-02-14, 22:06:50
I am working through some of the same minor issues while integrating the ds30 bootloader into my dsPIC33 project.
I had some issues with clock speed and baud rate, so for debugging purposes, I built a little test loop to generate some serial output:
.equ TESTCHAR, 'A'
testloop: SendL TESTCHAR /*endless loop to test UART output*/
goto testloop
Now I ask the question: Why not just use the bootloader as a standalone project, and then load the application? What are the reasons to integrate the bootloader into a project? I am wondering what the pros and cons of integration are?
I find the combined assembly and C code a big hassle, especially sharing constants and variables.
BTW the bootloader works great and I really appreciate the effort put into the development and support.
I had some issues with clock speed and baud rate, so for debugging purposes, I built a little test loop to generate some serial output:
.equ TESTCHAR, 'A'
testloop: SendL TESTCHAR /*endless loop to test UART output*/
goto testloop
Now I ask the question: Why not just use the bootloader as a standalone project, and then load the application? What are the reasons to integrate the bootloader into a project? I am wondering what the pros and cons of integration are?
I find the combined assembly and C code a big hassle, especially sharing constants and variables.
BTW the bootloader works great and I really appreciate the effort put into the development and support.