will-v-pi
will-v-pi
@UKTailwind Can you provide your elf file, so I can run picotool myself to see where the bottleneck is?
This appears to be both a compiler issue and a Windows vs Linux issue - on my 13900H laptop it takes: - ~5mins when using picotool compiled with MSVC 2022...
elf2uf2 didn’t do any disassembly, the disassembly was performed by the objdump in your toolchain and still is - picotool just modifies the coprocessor lines in that disassembly file. The...
From looking into this, it seems that the MSVC regex library is just ridiculously slow on Windows, so for larger programs I think the recommendataion would be to use a...
Looks like this was fixed in the 2.0.0 release, by adding this line https://github.com/raspberrypi/pico-sdk/blob/efe2103f9b28458a1615ff096054479743ade236/cmake/pico_pre_load_toolchain.cmake#L7 Can you try the 2.0.0 release and confirm if this has fixed your issue?
1. My personal recommendation for Risc-V compilers (and what the VS Code extension uses) would be the Core-V top of tree [here](https://www.embecosm.com/resources/tool-chain-downloads/#corev), or for Pi my pico-sdk-tools one from [here](https://github.com/raspberrypi/pico-sdk-tools/releases/tag/v2.0.0-0)...
> Ah ... that's what I figured. But which PATH? `/usr/local` and it finds everything or `/usr/local/bin` or something else? The same path you’d use for `PICO_TOOLCHAIN_PATH`, which is documented...
I've made a PR to add a note about the pre-compiled binaries to the readme. But it should be possible to compile on Windows - I've just checked and had...
You need to add the `-f` flag to your picotool command `picotool reboot -f -u`, and you need to be running compatible code - basically anything that uses stdio_usb, but...
The PersistentAllocator on the next branch would be useful for your use case, provided you have enough memory, as it will avoid reallocating the buffers every time you call configure,...