Ethernet based bootloader on w55rp20 using pico sdk

Question

Hello Everyone, I am using w55RP20-EVB_Pico for my application. I am trying to implement ethernet based bootloader using pico-sdk. I have written one app where LED blinks at 3 seconds and bootloader main file that check for any update, if not then it jumps to main led blink program. Now in my case, after flashing boot.uf2 via BOOTSEL method, then flashing app.uf2 i am not getting any printf outputs that i printed in my program (it even not generating any usb com port). But if I only flash boot.uf2 then it shows me printf outputs on usb com port that it switches to main app but then gets hang. Please check my files and suggest me if there are any problems. app.c: #include "pico/stdlib.h" #include <stdio.h> #include "hardware/regs/m0plus.h" #include "hardware/structs/scb.h" #define LED_PIN 25 int main() { stdio_init_all(); sleep_ms(2000); gpio_init(LED_PIN); gpio_set_dir(LED_PIN, GPIO_OUT); printf("
--- W55RP20 Application (LED Blink) ---
"); while (1) { gpio_put(LED_PIN, 1); printf("LED ON
"); sleep_ms(500); gpio_put(LED_PIN, 0); printf("LED OFF
"); sleep_ms(500); } } App CMakeList.txt add_executable(led_app App.c ) target_link_libraries(led_app pico_stdlib) pico_enable_stdio_usb(led_app 1) pico_enable_stdio_uart(led_app 0) # Use custom linker script pico_set_linker_script(led_app ${CMAKE_CURRENT_LIST_DIR}/app_linker.ld) pico_add_extra_outputs(led_app) app_linker.ld /* Application linker script for W55RP20 app slot (at 0x10100000) */ /* MEMORY { FLASH(rx) : ORIGIN = 0x10100000, LENGTH = 0x100000 RAM(rwx) : ORIGIN = 0x20000000, LENGTH = 256K } */ MEMORY { FLASH(rx) : ORIGIN = 0x10004000, LENGTH = 0x200000 - 0x4000 /* 2MB flash total, minus bootloader size */ RAM(rwx) : ORIGIN = 0x20000000, LENGTH = 256K } ENTRY(_entry_point) /* Stack configuration */ __StackTop = ORIGIN(RAM) + LENGTH(RAM); __StackBottom = __StackTop - 0x1000; PROVIDE(__StackTop = __StackTop); PROVIDE(__StackBottom = __StackBottom); SECTIONS { /* Start from beginning of app slot */ . = ORIGIN(FLASH); /* ---------------- Interrupt vectors ---------------- */ .vectors : { KEEP(*(.vectors)) } > FLASH /* ---------------- Reset handler ---------------- */ .reset : { KEEP(*(.reset)) } > FLASH /* ---------------- Code and constants ---------------- */ .text : { *(.text*) *(.rodata*) KEEP(*(.init)) KEEP(*(.fini)) } > FLASH /* ---------------- C++ constructors/destructors ---------------- */ .preinit_array : { . = ALIGN(4); __preinit_array_start = .; KEEP(*(.preinit_array)) __preinit_array_end = .; } > FLASH .init_array : { . = ALIGN(4); __init_array_start = .; KEEP(*(SORT(.init_array.*))) KEEP(*(.init_array)) __init_array_end = .; } > FLASH .fini_array : { . = ALIGN(4); __fini_array_start = .; KEEP(*(SORT(.fini_array.*))) KEEP(*(.fini_array)) __fini_array_end = .; } > FLASH /* ---------------- Binary Info Section ---------------- */ .binary_info : { . = ALIGN(4); __binary_info_start = .; KEEP(*(.binary_info*)) __binary_info_end = .; . = ALIGN(4); __etext = .; __flash_binary_end =…

Lihan__ · Answer

The information you provided is too limited. I roughly understand what kind of bootloader and firmware you intend to build. However, based on the code you’ve shared so far, it seems that many essential parts are missing. From what I can tell, you’ve just started developing the bootloader and firmware, and are currently testing a simple architecture where the bootloader jumps to the application. If that’s correct, The problem you’re facing now seems to be that the program jumps to the wrong address during the jump process. There’s one part I don’t quite understand. You mentioned, “in my case, after flashing boot.uf2 via BOOTSEL method, then flashing app.uf2.” But if you flash two UF2 files this way, the second upload will overwrite and erase the previously flashed UF2 file. Did I understand correctly?