question about the pi pico 2w

[RaveProv]

hey there,
it seems the pico code from meshtastic cant run on my RP2350 (pi pico 2) is there a way to change the code or make pi pico 2 run the meshtastic code?

[mverch67]

It is already supported. Choose the build target pico2 or pico2w.

[RaveProv]

Do you have a link or something because I can't seem to find it

[mverch67]

Do you have a link or something because I can't seem to find it

https://github.com/meshtastic/firmware/blob/d663d4464744e10e89e01eff7c62db1d94315414/variants/rpipico2/platformio.ini#L1

[AKopytenko]

I flashed a Pico 2W with a Waveshare LoRa shield using PlatformIO.

In the variant/rp2350 config file, the following parameters were set in platformio.ini:

upload_protocol = picotool
...
DHAS_WIFI=1

After flashing, the device is not visible on the Wi-Fi network.

I opened the serial port monitor and rebooted the device.

One of the lines showed:

INFO | ??:??:?? 2 Not using WIFI

Can you tell me which direction to look? How do I enable Wi-Fi?

[mverch67]

try enabling +<mesh/wifi> here, or use env:pico2w as a target.

[AKopytenko]

try enabling +<mesh/wifi> here, or use env:pico2w as a target.

It didn't change the symptom at all. It still says "Wifi not using."

[User643631]

Same problem.
LoRa shield power on.

Log from serial port:

DEBUG | ??:??:?? 2 Filesystem files:
DEBUG | ??:??:?? 2  channels.proto (57 Bytes)
DEBUG | ??:??:?? 2  device.proto (62 Bytes)
DEBUG | ??:??:?? 2  nodes.proto (245 Bytes)
DEBUG | ??:??:?? 2 Power::lipoInit lipo sensor is not ready yet
DEBUG | ??:??:?? 2 Use analog input 26 for battery level
INFO  | ??:??:?? 2 Scan for i2c devices
DEBUG | ??:??:?? 2 Scan for I2C devices on port 1
INFO  | ??:??:?? 2 No I2C devices found
DEBUG | ??:??:?? 2 acc_info = 0
INFO  | ??:??:?? 2 S:B:79,2.7.17.*********,pico2w,meshtastic/firmware
INFO  | ??:??:?? 2 Build timestamp: 1765486800
INFO  | ??:??:?? 2 Init NodeDB
INFO  | ??:??:?? 2 Load /prefs/nodes.proto
INFO  | ??:??:?? 2 Loaded /prefs/nodes.proto successfully
INFO  | ??:??:?? 2 Loaded saved nodedatabase version 24, with nodes count: 1
INFO  | ??:??:?? 2 Load /prefs/device.proto
INFO  | ??:??:?? 2 Loaded /prefs/device.proto successfully
INFO  | ??:??:?? 2 Loaded saved devicestate version 24
ERROR | ??:??:?? 2 Could not open / read /prefs/config.proto
INFO  | ??:??:?? 2 Install default LocalConfig
INFO  | ??:??:?? 2 Set default channel and radio preferences!
DEBUG | ??:??:?? 2 Expand short PSK #1
INFO  | ??:??:?? 2 Wanted region 0, using UNSET
ERROR | ??:??:?? 2 Could not open / read /prefs/module.proto
INFO  | ??:??:?? 2 Install default ModuleConfig
INFO  | ??:??:?? 2 Load /prefs/channels.proto
INFO  | ??:??:?? 2 Loaded /prefs/channels.proto successfully
INFO  | ??:??:?? 2 Loaded saved channelFile version 24
ERROR | ??:??:?? 2 Could not open / read /prefs/uiconfig.proto
DEBUG | ??:??:?? 2 cleanupMeshDB purged 0 entries
DEBUG | ??:??:?? 2 Use nodenum 0x7975d508 
DEBUG | ??:??:?? 2 Expand short PSK #1
INFO  | ??:??:?? 2 Wanted region 0, using UNSET
DEBUG | ??:??:?? 2 Coerce telemetry to min of 30 minutes on defaults
INFO  | ??:??:?? 2 Sort took 0 milliseconds
DEBUG | ??:??:?? 2 Save to disk 0
WARN  | ??:??:?? 2 Packet History - Invalid size -1, using default 200
DEBUG | ??:??:?? 2 Use compiled/slipstreamed tzplaceholder                                         
DEBUG | ??:??:?? 2 Set Timezone to GMT0
DEBUG | ??:??:?? 2 Read RTC time as 2
DEBUG | ??:??:?? 2 Start multicast thread
DEBUG | ??:??:?? 2 Rescan for I2C keyboard
DEBUG | ??:??:?? 2 Scan for I2C devices on port 2
DEBUG | ??:??:?? 2 Scan address 0x1f
DEBUG | ??:??:?? 2 Scan address 0x34
DEBUG | ??:??:?? 2 Scan address 0x55
DEBUG | ??:??:?? 2 Scan address 0x5a
DEBUG | ??:??:?? 2 Scan address 0x5f
DEBUG | ??:??:?? 2 Scan for I2C devices on port 1
DEBUG | ??:??:?? 2 Scan address 0x1f
DEBUG | ??:??:?? 2 Scan address 0x34
DEBUG | ??:??:?? 2 Scan address 0x55
DEBUG | ??:??:?? 2 Scan address 0x5a
DEBUG | ??:??:?? 2 Scan address 0x5f
ERROR | ??:??:?? 2 Could not open / read /prefs/cannedConf.proto
INFO  | ??:??:?? 2 CannedMessageModule is enabled
INFO  | ??:??:?? 2 External Notification Module Disabled
DEBUG | ??:??:?? 2 SX126xInterface(cs=3, irq=20, rst=15, busy=2)
DEBUG | ??:??:?? 2 SX126X_DIO3_TCXO_VOLTAGE defined, using DIO3 as TCXO reference voltage at 1.800000 V
INFO  | ??:??:?? 2 Start meshradio init
INFO  | ??:??:?? 2 Radio freq=906.875, config.lora.frequency_offset=0.000
INFO  | ??:??:?? 2 Set radio: region=UNSET, name=LongFast, config=0, ch=19, power=30
INFO  | ??:??:?? 2 myRegion->freqStart -> myRegion->freqEnd: 902.000000 -> 928.000000 (26.000000 MHz)
INFO  | ??:??:?? 2 numChannels: 104 x 250.000kHz
INFO  | ??:??:?? 2 channel_num: 20
INFO  | ??:??:?? 2 frequency: 906.875000
INFO  | ??:??:?? 2 Slot time: 28 msec, preamble time: 131 msec
INFO  | ??:??:?? 2 Final Tx power: 22 dBm
INFO  | ??:??:?? 2 SX126x init result 0
INFO  | ??:??:?? 2 Frequency set to 906.875000
INFO  | ??:??:?? 2 Bandwidth set to 250.000000
INFO  | ??:??:?? 2 Power output set to 22
DEBUG | ??:??:?? 2 Current limit set to 140.000000
DEBUG | ??:??:?? 2 Current limit set result 0
DEBUG | ??:??:?? 2 Set DIO2 as RF switch, result: 0
DEBUG | ??:??:?? 2 SX126X_RXEN not defined, defaulting to RADIOLIB_NC
DEBUG | ??:??:?? 2 SX126X_TXEN not defined, defaulting to RADIOLIB_NC
DEBUG | ??:??:?? 2 Use MCU pin -1 as RXEN and pin -1 as TXEN to control RF switching
INFO  | ??:??:?? 2 Set RX gain to boosted mode; result: 0
INFO  | ??:??:?? 2 SX1262 init success
INFO  | ??:??:?? 2 Not using WIFI
DEBUG | ??:??:?? 2 LoRA bitrate = 116.967873 bytes / sec
INFO  | ??:??:?? 2 PowerFSM init, USB power=1
DEBUG | ??:??:?? 2 Node status update: 1 online, 1 total
INFO  | ??:??:?? 32 [NodeInfo] Send our nodeinfo to mesh (wantReplies=1)
INFO  | ??:??:?? 32 [NodeInfo] Send owner !7975d508/Meshtastic d508/d508
DEBUG | ??:??:?? 32 [NodeInfo] Initial packet id **********
DEBUG | ??:??:?? 32 [NodeInfo] Partially randomized packet id 3765458495
DEBUG | ??:??:?? 32 [NodeInfo] Ignore update from self
DEBUG | ??:??:?? 32 [NodeInfo] handleReceived(LOCAL) (id=0xe070563f fr=0x7975d508 to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x0 Portnum=4 WANTRESP priority=10)
DEBUG | ??:??:?? 32 [NodeInfo] No modules interested in portnum=4, src=LOCAL
INFO  | ??:??:?? 32 [NodeInfo] Packet History - insert: Using new slot @uptime 32.475s TRACE NEW
DEBUG | ??:??:?? 32 [NodeInfo] Expand short PSK #1
DEBUG | ??:??:?? 32 [NodeInfo] Use AES128 key!
WARN  | ??:??:?? 32 [NodeInfo] send - lora tx disabled: Region unset

variant/rp2350/rpipico2w/platformio.ini:

[env:pico2w]
extends = rp2350_base
board = rpipico2w
board_level = pr
board_check = true
upload_protocol = picotool
# debug settings for external openocd with RP2040 support (custom build)
# debug_tool = custom
debug_init_cmds =
  target extended-remote localhost:3333
  $INIT_BREAK
  monitor reset halt
  $LOAD_CMDS
  monitor init
  monitor reset halt

# add our variants files to the include and src paths
build_flags =
  ${rp2350_base.build_flags}
  -DRPI_PICO2
  -Ivariants/rp2350/rpipico2w
#  -DDEBUG_RP2040_PORT=Serial
  -DHW_SPI1_DEVICE
  -DARDUINO_RASPBERRY_PI_PICO_2W
  -DARDUINO_ARCH_RP2040
  -DHAS_WIFI=1
  -fexceptions  # for exception handling in MQTT
  -DHAS_UDP_MULTICAST=1
build_src_filter = ${rp2350_base.build_src_filter} +<mesh/wifi/>
lib_deps =
  ${rp2350_base.lib_deps}
  ${networking_base.lib_deps}
debug_build_flags = ${rp2350_base.build_flags}, -g

[User643631]

It's completely unclear where the WiFi connection settings are configured.
The only file I found that the firmware files seem to reference (I searched for the text "Wifi not use") is firmware/userPrefs.jsonc. I tried removing the comments from the following lines:

// "USERPREFS_NETWORK_WIFI_ENABLED": "true",
// "USERPREFS_NETWORK_WIFI_SSID": "wifi_ssid",
// "USERPREFS_NETWORK_WIFI_PSK": "wifi_psk",

I rebuilt the firmware, send to device, and WiFi turned on, but I'm unclear what to do next. The network can't be found using the specified SSID, and the Meshtastic Android app doesn't have an SSID field; you have to enter the IP address.

[mverch67]

You configure the wifi settings with the phone app under network using bluetooth (or USB cable on Android).

If the picow doesn't have bluetooth then use the python CLI

[AKopytenko]

Ok after editing this file the Wi-Fi worked. But as far as I understand these are the parameters Pico uses to connect to the router. The opposite is needed so the client can connect to Pico. But maybe I'm wrong. Anyway, nothing's clear :)

[mverch67]

The firmware does not provide an Wifi AP but it opens port 4403. Once the pico connected to the wifi router you can either enable MQTT for telemetry analysis or meshtastic over MQTT. Or you can connect the meshtastic web client (served at https://client.meshtastic.org). Also it should be possible to enter the pico IP address in Android for connecting. With the current configuration there won't be a webserver running on the pico.

[AKopytenko]

The firmware does not provide an Wifi AP but it opens port 4403. Once the pico connected to the wifi router you can either enable MQTT for telemetry analysis or meshtastic over MQTT. Or you can connect the meshtastic web client (served at https://client.meshtastic.org). Also it should be possible to enter the pico IP address in Android for connecting. With the current configuration there won't be a webserver running on the pico.

Could you provide a link to any instructions or documentation on how to connect Pico 2W devices to the Meshtastic Android app? I couldn't find anything.

For example, how did you find out about port 4403? I was only able to configure the device through the web interface https://client.meshtastic.org/ (USB cable, Serial port). The device established a connection and functions solely as a repeater.

But even after setting it up via the web configurator, the Pico 2W couldn't connect via Wi-Fi. On the screen:

Navigation -> Config -> Network -> WiFi Config

I set the parameters to Enabled, SSID, and PSK. When I tried to add a new network via my smartphone, it failed. There is no such network.