You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a strange problem. I've yet only build the digital part of PicoRX: the rpi pico, rotary encoder, display and buttons.
I compiled and uploaded pico2rx.uf2. When connected to a Linux MX computer USB port it hangs and the display is showing the PicoRX splash screen halfways. When I just connect it to a phone charger it works ok. I then see the frequency and it changes when turning the rotary encoder. Command lsusb gives a line, so it is connected:
Bus 003 Device 024: ID cafe:4011 dawsonjon PicoRX
When using the pre-compiled uf2 files, it works also ok, both of them. When I compare the downloaded pico2rx.uf2 and the compiled pico2rx.uf2, they both are of the same size. The contents is different.
I see this problem only when connecting to Linux MX. Connecting to Windows 10 is ok.
Anyone an idea what could be the problem?
The text was updated successfully, but these errors were encountered:
I have a very similar issue if I compile with the latest version of SDK. I'm working through it, but don't have a solution yet. For now, the best workaround is probably to roll back to an earlier version of SDK.
I have a strange problem. I've yet only build the digital part of PicoRX: the rpi pico, rotary encoder, display and buttons.
I compiled and uploaded pico2rx.uf2. When connected to a Linux MX computer USB port it hangs and the display is showing the PicoRX splash screen halfways. When I just connect it to a phone charger it works ok. I then see the frequency and it changes when turning the rotary encoder. Command lsusb gives a line, so it is connected:
Bus 003 Device 024: ID cafe:4011 dawsonjon PicoRX
When using the pre-compiled uf2 files, it works also ok, both of them. When I compare the downloaded pico2rx.uf2 and the compiled pico2rx.uf2, they both are of the same size. The contents is different.
I see this problem only when connecting to Linux MX. Connecting to Windows 10 is ok.
Anyone an idea what could be the problem?
The text was updated successfully, but these errors were encountered: