Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: 2.2.7 pico does not initialize properly #2816

Closed
NickDolfin opened this issue Sep 20, 2023 · 12 comments
Closed

[Bug]: 2.2.7 pico does not initialize properly #2816

NickDolfin opened this issue Sep 20, 2023 · 12 comments
Labels
bug Something isn't working

Comments

@NickDolfin
Copy link

Category

Other

Hardware

Raspberry Pi Pico (W)

Firmware Version

2.2.7.e8970ad

Description

It hangs during boot.
The led stays on continuesly.
I cannot get a putty window on the serial port.

The previous alpha version 2.2.6 works

Relevant log output

No response
@NickDolfin NickDolfin added the bug Something isn't working label Sep 20, 2023
@rcarteraz
Copy link
Member

Yeah, there's definitely something going on with this.

DEBUG | ??Connected to radio
WARNING file:mesh_interface.py _sendPacket line:530 Not sending packet because protocol use is disabled by noProto
:??:?? 1  channels.proto (53 Bytes)
lfs_file_close: fd=0x20012e0c
DEBUG | ??:??:?? 1  db.proto (112 Bytes)
lfs_file_close: fd=0x20012e0c
DEBUG | ??:??:?? 1 Using analog input 26 for battery level
INFO  | ??:??:?? 1 Scanning for i2c devices...
DEBUG | ??:??:?? 1 Scanning for i2c devices on port 1
INFO  | ??:??:?? 1 No I2C devices found
DEBUG | ??:??:?? 1 acc_info = 0
INFO  | ??:??:?? 1 Meshtastic hwvendor=47, swver=2.2.7.e8970ad
INFO  | ??:??:?? 1 Initializing NodeDB
INFO  | ??:??:?? 1 Loading /prefs/db.proto
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 1 Loaded saved devicestate version 22
LittleFSDirImpl::openFile: rc=-2 fd=0x20012bac path=`/prefs/config.proto` openMode=0 accessMode=1 err=-2
INFO  | ??:??:?? 1 No /prefs/config.proto preferences found
INFO  | ??:??:?? 1 Installing default LocalConfig
INFO  | ??:??:?? 1 Setting default channel and radio preferences!
DEBUG | ??:??:?? 1 Expanding short PSK #1
INFO  | ??:??:?? 1 Wanted region 0, using UNSET
LittleFSDirImpl::openFile: rc=-2 fd=0x20012bac path=`/prefs/module.proto` openMode=0 accessMode=1 err=-2
INFO  | ??:??:?? 1 No /prefs/module.proto preferences found
INFO  | ??:??:?? 1 Installing default ModuleConfig
INFO  | ??:??:?? 1 Loading /prefs/channels.proto
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 1 Loaded saved channelFile version 22
LittleFSDirImpl::openFile: rc=-2 fd=0x20012bac path=`/oem/oem.proto` openMode=0 accessMode=1 err=-2
INFO  | ??:??:?? 1 No /oem/oem.proto preferences found
DEBUG | ??:??:?? 1 cleanupMeshDB purged 0 entries
DEBUG | ??:??:?? 1 Expanding short PSK #1
INFO  | ??:??:?? 1 Wanted region 0, using UNSET
DEBUG | ??:??:?? 1 region=0, NODENUM=0x77b4323, dbsize=1
DEBUG | ??:??:?? 1 Read RTC time as 0
DEBUG | ??:??:?? 1 WANT GPS=1```

@thebentern
Copy link
Contributor

GPS initialization issue possibly based on that last line. @jp-bennett do you have a pico based board?

@jp-bennett
Copy link
Collaborator

No, but I'd agree, it's something odd with trying to power up GPS. Which may or may not exist. What is the general setup for a pico board? Is there a Lora HaT?

@rcarteraz
Copy link
Member

No, but I'd agree, it's something odd with trying to power up GPS. Which may or may not exist. What is the general setup for a pico board? Is there a Lora HaT?

Waveshare LoRa module https://meshtastic.org/docs/hardware/devices/raspberry-pi/

@thebentern
Copy link
Contributor

There's also the RAK RP2040 based core but don't know if it's affected.

@rcarteraz
Copy link
Member

rcarteraz commented Sep 20, 2023 •
edited
Loading

There's also the RAK RP2040 based core but don't know if it's affected.

I'm going to say yes

WARNING file:mesh_interface.py _sendToRadio line:680 Not sending packet because protocol use is disabled by noProto
lfConnected to radio
WARNING file:mesh_interface.py _sendPacket line:530 Not sending packet because protocol use is disabled by noProto
s_file_close: fd=0x20012d94
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Saving /prefs/config.proto
lfs_file_close: fd=0x20012bac
lfs_file_close: fd=0x20012d9c
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Saving /prefs/module.proto
lfs_file_close: fd=0x20012bac
lfs_file_close: fd=0x20012d9c
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Saving /prefs/channels.proto
lfs_file_close: fd=0x20012bac
lfs_file_close: fd=0x20012d9c
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Loading /prefs/config.proto
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Loaded saved config version 22
INFO  | ??:??:?? 2 Loading /prefs/module.proto
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Loaded saved moduleConfig version 22
INFO  | ??:??:?? 2 Loading /prefs/channels.proto
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Loaded saved channelFile version 22
LittleFSDirImpl::openFile: rc=-2 fd=0x20012bac path=`/oem/oem.proto` openMode=0 accessMode=1 err=-2
INFO  | ??:??:?? 2 No /oem/oem.proto preferences found
DEBUG | ??:??:?? 2 cleanupMeshDB purged 0 entries
INFO  | ??:??:?? 2 Setting default channel and radio preferences!
DEBUG | ??:??:?? 2 Expanding short PSK #1
INFO  | ??:??:?? 2 Wanted region 0, using UNSET
DEBUG | ??:??:?? 2 region=0, NODENUM=0x53314d24, dbsize=1
INFO  | ??:??:?? 2 Saving /prefs/db.proto
lfs_file_close: fd=0x20012bac
lfs_file_close: fd=0x20012d94
lfs_file_close: fd=0x20012bac
INFO  | ??:??:?? 2 Saving /prefs/channels.proto
lfs_file_close: fd=0x20012bac
lfs_file_close: fd=0x20012d9c
lfs_file_close: fd=0x20012bac
DEBUG | ??:??:?? 2 Read RTC time as 0```

@jp-bennett
Copy link
Collaborator

We dropped the check for GPS_SERIAL_NUM during init. That chip probably doesn't have a serial port to try to bring up. I'll open a PR just to try to fix this in a bit.

@NickDolfin
Copy link
Author

NickDolfin commented Sep 20, 2023 •
edited
Loading

I have a Waveshare RP2040-Plus 4MB coupled to a Waveshare SX1262 LoRa Node Module for a Raspberry Pi Pico.

No gps at the moment. Perhaps in the future.

@jp-bennett
Copy link
Collaborator

In theory #2817 fixes this hang.

@rcarteraz
Copy link
Member

In theory #2817 fixes this hang.

I’ll test it

@NickDolfin
Copy link
Author

Nope, 2.2.8 is not working.

I tried to capture the output:
▒▒@INFO | ??:??:?? 1

//\ E S H T /\ S T / C

DEBUG | ??:??:?? 1 Filesystem files:
DEBUG | ??:??:?? 1 channels.proto (53 Bytes)
lfs_file_close: fd=0x20012e14
DEBUG | ??:??:?? 1 config.proto (93 Bytes)
lfs_file_close: fd=0x20012e14
DEBUG | ??:??:?? 1 db.proto (299 Bytes)
lfs_file_close: fd=0x20012e14
DEBUG | ??:??:?? 1 module.proto (88 Bytes)
lfs_file_close: fd=0x20012e14
DEBUG | ??:??:?? 1 Using analog input 26 for batter y level
INFO | ??:??:?? 1 Scanning for i2c devices...
DEBUG | ??:??:?? 1 Scanning for i2c devices on port 1
INFO | ??:??:?? 1 No I2C devices found
DEBUG | ??:??:?? 1 acc_info = 0
INFO | ??:??:?? 1 Meshtastic hwvendor=47, swver=2.2.8.8f9d335
INFO | ??:??:?? 1 Initializing NodeDB
INFO | ??:??:?? 1 Loading /prefs/db.proto
lfs_file_close: fd=0x20012bb4
INFO | ??:??:?? 1 Loaded saved devicestate version 22
INFO | ??:??:?? 1 Loading /prefs/config.proto
lfs_file_close: fd=0x20012bb4
INFO | ??:??:?? 1 Loaded saved config version 22
INFO | ??:??:?? 1 Loading /prefs/module.proto
lfs_file_close: fd=0x20012bb4
INFO | ??:??:?? 1 Loaded saved moduleConfig versio n 22
INFO | ??:??:?? 1 Loading /prefs/channels.proto
lfs_file_close: fd=0x20012bb4
INFO | ??:??:?? 1 Loaded saved channelFile version 22
LittleFSDirImpl::openFile: rc=-2 fd=0x20012bb4 path=/oem/oem.proto openMode=0 accessMode=1 err=-2
INFO | ??:??:?? 1 No /oem/oem.proto preferences found
DEBUG | ??:??:?? 1 cleanupMeshDB purged 0 entries
DEBUG | ??:??:?? 1 Expanding short PSK #1
INFO | ??:??:?? 1 Wanted region 3, using EU_868
DEBUG | ??:??:?? 1 region=3, NODENUM=0xdf58312c, dbsize=3
DEBUG | ??:??:?? 1 Read RTC time as 0
DEBUG | ??:??:?? 1 WANT GPS=1

Green led is still on.

@NickDolfin
Copy link
Author

@jp-bennett Yes, you are right. I was too fast and downloaded the wrong one.

Now 2.2.8 is working.

Many thanks for the fast fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jp-bennett @rcarteraz @thebentern @NickDolfin