What is the purpose of the reset_fwrd vs reset_no_fwrd #802
-
I'm looking to make a Dip Dap clone and was just browsing the HIC specific source for the LPC11U35 and saw some odd things in the source regarding the "forwarded reset". It looks like both functions are defined (fwrd & no fwrd) and in the HDK both of these pins are hooked up and driven from the Reset PB on the board (Referencing the HDK repository schematics). My question is: what's the practical use of having both of these defined in the source as inputs when the Follow-up question: Is that the intention? For the Dip Dap hardware to use the ROM bootloader and only run the DAPLink interface FW? gpio.cuint8_t gpio_get_reset_btn_no_fwrd()
{
return LPC_GPIO->PIN[PIN_RESET_IN_PORT] & PIN_RESET_IN ? 0 : 1;
}
uint8_t gpio_get_reset_btn_fwrd()
{
return LPC_GPIO->PIN[PIN_RESET_IN_FWRD_PORT] & PIN_RESET_IN_FWRD ? 0 : 1;
} gpio.hstatic inline uint8_t gpio_get_reset_btn(void)
{
return gpio_get_reset_btn_no_fwrd() || gpio_get_reset_btn_fwrd();
} |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
DAPLink for LPC11U35 does not use a bootloader (there is no AFAIK, there are 3 uses of the reset buttons:
The bootloader does not need two buttons (both perform the same operations). With two buttons, the interface would have one ( |
Beta Was this translation helpful? Give feedback.
DAPLink for LPC11U35 does not use a bootloader (there is no
lpc11u35_bl
).AFAIK, there are 3 uses of the reset buttons:
gpio_get_reset_btn()
insource/daplink/drag-n-drop/vfs_user.c
for file automation in both bootload and interface.gpio_get_reset_btn()
insource/daplink/bootloader/main_bootloader.c
to stop bootloader from starting interface.gpio_get_reset_btn_fwrd()
insource/daplink/interface/main_interface.c
to reset the target.The bootloader does not need two buttons (both perform the same operations). With two buttons, the interface would have one (
gpio_get_reset_btn_fwrd()
) that reset the target and performs file automation and one that only does the latter (gpio_get_reset_btn_…