Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8093

Zephyr • Getting started

$
0
0
This should complete your installation with a total memory usage of around 4.5 Gb. That is quite slim for Zephyr!
Thanks for the guide and I'll definitely give it a go as it's about half the size of what I have -

Code:

1.2G    ./zephyr16M     ./bootloader732M    ./.venv36K     ./myzephyr20M     ./tools5.8G    ./modules8.0K    ./.west7.7G    .
I put my 'zephyr-sdk-0.17.4' outside that tree and that's another 1.5 GB, giving a grand total of 9.2 GB. I guess my SDK is smaller than yours as I am using the standard 'arm-none-eeabi' toolchain already installed by 'apt' for Pico SDK development.

The good news is it works; I have a Zephyr built 'blinky' running on my Pico.

And, even better, with a little bit of hacking I have now got it working the same way as a traditional Pico SDK build, the 'cmake' does a 'make' so that doesn't actually have to be done -

Code:

pi@Pi4B:~ $ cd ~/myzephr/blinkypi@Pi4B:~/myzephr/blinky $ mkdir buildpi@Pi4B:~/myzephr/blinky $ cd buildpi@Pi4B:~/myzephr/blinky/build $ cmake .....pi@Pi4B:~/myzephr/blinky/build $ make-- west build: generating a build systemLoading Zephyr default modules (Zephyr base).-- Application: /home/pi/myzephr/blinky...Generating files from /home/pi/myzephr/blinky/build/zephyr/zephyr.elf for board: rpi_picoConverted to uf2, output size: 35840, start address: 0x10000000Wrote 35840 bytes to zephyr.uf2

Code:

pi@Pi4B:~/myzephr/blinky/build $ mptool listExamining './zephyr/zephyr.uf2'No binary information - Only limited information availableTarget Device          : RP2040Target Chip            : Cortex-M0+Target ISA             : ARMv6-MZephyr Build Version   : v4.2.0-3011Code Execution Type    : Runs from FlashProgram Area Used      : 10000000 to 100045FF    17 KB     17,920 bytes

Code:

pi@Pi4B:~/myzephr/blinky/build $ mptool loadUploading './zephyr/zephyr.uf2' to RP2040 with 2MB FlashLoading into Flash:   [==============================]  100%The device was rebooted to start the application.The device has rebooted  Latest USB Device information found ...  usb 1-1.4: new full-speed USB device number 47 using xhci_hcd  usb 1-1.4: New USB device found, idVendor=2e8a, idProduct=0003, bcdDevice= 1  usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3  usb 1-1.4: Product: RP2 Boot  usb 1-1.4: Manufacturer: Raspberry Pi  usb 1-1.4: SerialNumber: E0C912D24340  usb-storage 1-1.4:1.0: USB Mass Storage device detected  usb 1-1.4: USB disconnect, device number 47Device is running but no '/dev/ttyACM0' is available
It's not perfect yet - like having to fix '~/myzephr' which I only just spotted - but I'm getting there. It might not be to everyone's taste but suits me fine. The 'mptool' app is my own utility for all things MicroPython, Pico SDK, and now Zephyr. It's basically a wrapper to 'picotool' or replicates its functionality.

I do have two questions -

How to put a PIco running a Zephyr program into BOOTSEL mode without having to hold the BOOTSEL button and re-plug the USB ?

Do you know what the 'mcuboot' of the 'rpi_pico/rp2040/mcuboot' board indicates by that ?

Statistics: Posted by hippy — Wed Sep 10, 2025 1:09 am



Viewing all articles
Browse latest Browse all 8093

Trending Articles