Project goal is to minimize boot code.
I am at the very first step of trying to make sure I am able to add a debug console, so that when I make changes to the boot code, I can track it. As there is no IDE in place for this project, this might be only way to go about it. The existing project has a Borland compiler and builds and creates the boot hex file using cmdline make builds.
the boot hex and application file are then merged together and loaded on to the target.
I have tried loading the merged hex file without any changes to boot code and it works.(loaded at offset 0x30 0000)
but, after changing the boot code to add uart setup i have only loaded the boot hex file(without merge) at the same address.
Right now I am only dealing with the boot code, and thus have avoided the boot code from launching the application.
Limitations: Using make files to build, no IDE, no breakpoints can be added. Everytime the file is built, the hex file is loaded on the chip and added to target.
Problem : I am trying to just get the UART working with may be a character or a string or anything possible to see on tera term if the first step can take effect and if its feasible. So far with the code below i have not been able to see anything on the tera term or on the oscilloscope.
I realized watchdog (hardware)which exists might be resetting the PIC and thus reconfigured the port to which watchdog is connected and tried to toggle it using software. Seems like it doesnt work too. I cannot see a toggle on the scope at this pin.
Question: 1. Could someone throw light on how feasible the method sounds? Or am I heading right direction?
2. Would merge with application and not merging be a factor?
NOte: will add source code if required
I am at the very first step of trying to make sure I am able to add a debug console, so that when I make changes to the boot code, I can track it. As there is no IDE in place for this project, this might be only way to go about it. The existing project has a Borland compiler and builds and creates the boot hex file using cmdline make builds.
the boot hex and application file are then merged together and loaded on to the target.
I have tried loading the merged hex file without any changes to boot code and it works.(loaded at offset 0x30 0000)
but, after changing the boot code to add uart setup i have only loaded the boot hex file(without merge) at the same address.
Right now I am only dealing with the boot code, and thus have avoided the boot code from launching the application.
Limitations: Using make files to build, no IDE, no breakpoints can be added. Everytime the file is built, the hex file is loaded on the chip and added to target.
Problem : I am trying to just get the UART working with may be a character or a string or anything possible to see on tera term if the first step can take effect and if its feasible. So far with the code below i have not been able to see anything on the tera term or on the oscilloscope.
I realized watchdog (hardware)which exists might be resetting the PIC and thus reconfigured the port to which watchdog is connected and tried to toggle it using software. Seems like it doesnt work too. I cannot see a toggle on the scope at this pin.
Question: 1. Could someone throw light on how feasible the method sounds? Or am I heading right direction?
2. Would merge with application and not merging be a factor?
NOte: will add source code if required