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

First boot fails. Where can I look for symptoms to debug? #87

Open
enorberg opened this issue Nov 7, 2021 · 20 comments
Open

First boot fails. Where can I look for symptoms to debug? #87

enorberg opened this issue Nov 7, 2021 · 20 comments
Labels
bug Something isn't working

Comments

@enorberg
Copy link

enorberg commented Nov 7, 2021

Describe the bug
Just put my Mark-II Dev Kit together. Trying to boot for the first time, but it fails.

To Reproduce
Steps to reproduce the behavior:

  1. Apply power.
    RPi Red power led is on.
    RPi Green led is on for several seconds - as though reading USB Drive.
    Then goes out and after a few seconds, flickers once.
    SJ-201 shows blue leds circling for ~ 1 min.
    SJ-201 flashes red led circle.
    SJ-201 flashes yellow/white led circle. Then leds off.
    There is no other activity.
  2. Wait 5 min, then power off.

Expected behavior
Boot and go into WiFi setup .. then device registration.

Log files
N/A

I'm looking for diagnostic suggestions.

  • I've tried the USB drive in both of the USB-3 ports with the same results.
  • Should I be able to hook up a monitor and get useful feedback?
  • Other?

I've had this Dev Kit since sometime this summer and just now had time to work on it.
I created the Image file with dd on my linux (ubuntu) laptop from
MarkII_arm-rpi64_Prod_012-stable_2021-08-19.img.gz
after unzipping.

Thanks for your help.
@enorberg enorberg added the bug Something isn't working label Nov 7, 2021
@ChanceNCounter
Copy link

Does the screen do anything? Maybe a screen test when power is applied? I'm wondering about the ribbon connector. Just a thought.

@enorberg
Copy link
Author

enorberg commented Nov 7, 2021 via email

@krisgesling
Copy link
Collaborator

Hey @enorberg - sorry to hear you're having trouble.

If you're not getting any audio output after boot then I think it points to more than a display issue.

Another thing to check is that the 40 pin connector between the pi and the SJ201 is nicely fitted. It must be getting power to the pi if that has LED's lit up but if some pins aren't connecting properly it won't successfully boot.

@enorberg
Copy link
Author

enorberg commented Nov 8, 2021

Hi @krisgesling, thanks for the suggestions.

There is no audio at any point - only the SJ201 led displays (circling blue, momentary all red then momentary all yellow).
I did check the 40 pin connector and it is completely snugged up between the RPi and the SJ201.

The only other thing I can think of is to re-image the USB drive.

The 1st time, I simply expanded the downloaded .gz file and used dd to copy the .img to the USB.

I am going to try the other method mentioned in the instructables.com page that involves downloading the Raspberry Pi Imager app. Then I'll use that to write the USB drive in case I was wrong that both methods are equivalent.

If that doesn't fix the issue, would there be useful output from the RPi mini-hdmi port at boot time?
I could disassemble the Mark-II enough to hook up a monitor if there's something to see and no other diagnostic option.

@MetaGamer
Copy link
Collaborator

If the blue circle animation on the SJ201 LEDs stops, it means the HAL is at least working. Which makes me think it's booting fine and it's a display issue. I'd double check the ribbon cable to the display- it's easy to put it in backwards. As for sound- even without a resonating chamber you should be able hear the speakers.

Do the buttons do anything? The two front buttons should make the ring-LEDs temporarily light up with the current volume, and the left switch should cause on LED to turn red to indicate that the mic is disconnected.

@enorberg
Copy link
Author

enorberg commented Nov 8, 2021

Hey @MetaGamer, thanks for the suggestion. This helped a lot! ... but now another issue.

I checked the ribbon cable and questioned the SJ201 end. It "looked" correct per the pix on the instructables.com page - see screen shot below. BUT that shows the exposed conductors facing outboard so they don't make contact with the board. I reversed this and the Dev Kit now boots with both audio and video output.

However, when prompted to join the temporary Mycroft network, I couldn't find it. I saw several other neighbor's wifi networks, but no "Mycroft". - I tried this with an iPhone8, a ubuntu desktop and a MacMini but none of them could see the Mycroft network.

There was a prompt to go to start.mycroft.ai, but that site appears to be down. I'm going to try again later tonight.

Screen Shot 2021-11-08 at 13 39 29

@enorberg
Copy link
Author

enorberg commented Nov 8, 2021

...oops - not the SJ201 attachment - the LCD attachment - sorry.

@krisgesling
Copy link
Collaborator

Ah, that is a good thing for us to fix up!!

Did the wifi network show up after a reboot? If it's still happening it would be good if we could dig into it to figure out what's going wrong. Do you have an ethernet connection available at all?

@enorberg
Copy link
Author

enorberg commented Nov 9, 2021 via email

@krisgesling
Copy link
Collaborator

Damn, but good that you have ethernet available.

First is a short list of the network manager connections:

  1. Plug in via ethernet and get paired
  2. Add an SSH key to that device in your account
  3. SSH into the awconnect container:
ssh -p 8222 awconnect@$IPADDRESS
  1. Send us the output of the following command:
nmcli c

Second, if you’re happy to temporarily share your device logs with us it would also be great if you could

  1. login to the main mycroft container:
ssh -p 8222 mycroft@$IPADDRESS
  1. Get your device-id and send that to us:
sudo cat /pantavisor/device-id
  1. Shutdown the device and plug the usb into a computer
  2. In the pvboot partition, edit cmdline.txt
    change the final
ph_log.push=0

to

ph_log.push=1

This will push your device logs to our backend, so we then need to replicate the issue:

  1. shutdown the device
  2. remove the ethernet cable
  3. plug the device back in and see if the mycroft wifi AP has been created
  4. wait at least 3-5 minutes after it’s booted to ensure it’s definitely not showing up
  5. plug in the ethernet cable to connect to the net and have the logs uploaded.
  6. run nmcli c again to see if anything has changed there.

Thanks

@krisgesling
Copy link
Collaborator

The device-id does uniquely identify your device but it's not something anyone can use against you. Even so, if you'd prefer to send things to me privately my email is [email protected]

@enorberg
Copy link
Author

enorberg commented Nov 10, 2021 via email

@enorberg
Copy link
Author

enorberg commented Nov 10, 2021 via email

@enorberg
Copy link
Author

enorberg commented Nov 10, 2021 via email

@enorberg
Copy link
Author

enorberg commented Nov 10, 2021 via email

@krisgesling
Copy link
Collaborator

Hey @enorberg sorry for the radio silence - just wanted to say thanks heaps for the logs - they came through perfectly.

The team have finally been able to replicate the issue and are working on a fix. I'll hopefully have more details on what went wrong soon too.

@enorberg
Copy link
Author

enorberg commented Nov 22, 2021 via email

@GameGuy1900
Copy link

Is there already a solution to this problem?

@enorberg
Copy link
Author

enorberg commented Dec 26, 2021 via email

@GameGuy1900
Copy link

Okay, that's too bad

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
5 participants
@enorberg @MetaGamer @krisgesling @ChanceNCounter @GameGuy1900