Closed tomdean1939 closed 2 months ago
Could you provide the UF2 file you're using, and what platform you're running picotool on? Also, make sure your 99-picotool.rules file is up to date, as it was updated for RP2350, and you've rebooted since changing it - it should include the 0x0009
and 0x000F
PIDs, which are for the RP2350
No application should ever segfault. However, I did not reboot. I used 'sudo udevadm trigger' which should have reloaded 99-picotool.rules , which is the latest from github, after the RP2350 update. Rebooting fixed the problem. Again, there is the problem of segfault, which should never occur. Sorry for the noise.
@tomdean1939 Just to clarify: are you saying that since you rebooted, you've not been able to reproduce this segfault?
On 8/27/24 11:48, Andrew Scheller wrote:
@tomdean1939 https://github.com/tomdean1939 Just to clarify: are you saying that since you rebooted, you've not been able to reproduce this segfault?
Yes, that is correct, rebooting corrected the issue and I am not able to reproduce the segfault.
tomdean
Thanks for the confirmation. Closing this issue then.
To load a pico2, picotool needs sudo - yes, I copied 99-picotool.rules
====== with pico ===================================
built with set(PICO_BOARD pico)