2010-11-08, 18:17:39
(This post was last modified: 2012-12-22, 13:36:51 by Mikael Gustavsson.)
Hi all,
I have an application with dsPIC33FJ128GP708A and it is working at 40 MHz(internal clock with PLL and tunning), UART2 for bootload, and data initialization support(crt0.s from C30).
I have ds30 loader working perfectly in my application. I defined 5 seconds delay in the firmware and when I reset the device it waits 5 seconds before jumping (if there is not a bootload command from the GUI), and it has this behaviour repeateadly.
Something strange happens
when RX of UART2 is floating or pulldown to GND: on power-up it jumps directly to the application without waiting the 5 seconds. If RX is pulluped to VDD the behaviour gets normal: it waits 5 seconds for a bootload command from the GUI before jumping to the application.
Was it designed to work like this? Is it possible to disable this? A this moment it is a bit expensive to change the hardware of the application.
Kind regards,
Vitor
I have an application with dsPIC33FJ128GP708A and it is working at 40 MHz(internal clock with PLL and tunning), UART2 for bootload, and data initialization support(crt0.s from C30).
I have ds30 loader working perfectly in my application. I defined 5 seconds delay in the firmware and when I reset the device it waits 5 seconds before jumping (if there is not a bootload command from the GUI), and it has this behaviour repeateadly.
Something strange happens
when RX of UART2 is floating or pulldown to GND: on power-up it jumps directly to the application without waiting the 5 seconds. If RX is pulluped to VDD the behaviour gets normal: it waits 5 seconds for a bootload command from the GUI before jumping to the application.Was it designed to work like this? Is it possible to disable this? A this moment it is a bit expensive to change the hardware of the application.
Kind regards,
Vitor