Distribute pioasm as a package/executable #1345
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#1345
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be very convenient to have
pioasmdistributed as a package, in addition to the current state where it's distributed as source code that should be compiled as part of the project. This was mentioned in #396 but that issue seemed to drift to other areas.By "package" I mean a standalone application that can be installed with the user's package manager, e.g.
apt install pioasm.Other options are a downloadable executable, or even a python wrap that could be installed with
pip install pioasm.Context: I'm porting the PIO to Zephyr, which does not use
pico-sdk's build system. We would prefer to have pioasm installed once as part of the installation process, rather than building it as part of the main build.We now have downloadable executables for pioasm (the zip is named pico-sdk-tools) and picotool available from the pico-sdk-tools repository. Currently these are built for Windows x64, MacOS x64 and arm64, and Linux x64 (Ubuntu) and arm64 (Raspberry Pi OS).
These include cmake config files, so if you're using CMake to find the packages then you can simply download and unzip the file, then add
to your CMakeLists.txt.
See the
pico_init_pioasmandpico_init_picotoolfunctions in tools/CMakeLists.txt for how the SDK does this