rcn-ee_ has quit [Remote host closed the connection]
rcn-ee_ has joined #beagle
rob_w has joined #beagle
rob_w has quit [Client Quit]
rob_w has joined #beagle
rcn-ee_ has quit [Remote host closed the connection]
rcn-ee_ has joined #beagle
rcn-ee_ has quit [Remote host closed the connection]
rcn-ee_ has joined #beagle
vd has quit [Ping timeout: 256 seconds]
vd has joined #beagle
Shadyman has quit [Quit: Leaving.]
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
otisolsen70 has joined #beagle
florian has joined #beagle
otisolsen70_ has joined #beagle
otisolsen70 has quit [Ping timeout: 265 seconds]
otisolsen70 has joined #beagle
otisolsen70_ has quit [Ping timeout: 268 seconds]
otisolsen70 has quit [Quit: Leaving]
lucascastro has quit [Read error: Connection reset by peer]
set_ has quit [Remote host closed the connection]
lucascastro has joined #beagle
akaWolf has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
buckket has joined #beagle
rcn-ee_ has quit [Quit: Leaving]
rcn-ee has joined #beagle
Posterdati has quit [Read error: Connection reset by peer]
Posterdati has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
Posterdati has quit [Ping timeout: 252 seconds]
giort has joined #beagle
Posterdati has joined #beagle
giort has quit [Quit: giort]
rob_w has quit [Quit: Leaving]
russ has quit [Ping timeout: 265 seconds]
shoragan[m] has quit [Quit: Bridge terminating on SIGTERM]
RossSchulman[m] has quit [Quit: Bridge terminating on SIGTERM]
mvaittin has quit [Quit: Bridge terminating on SIGTERM]
jduchniewicz has quit [Quit: Bridge terminating on SIGTERM]
jkridner[m] has quit [Quit: Bridge terminating on SIGTERM]
shoragan[m] has joined #beagle
mvaittin has joined #beagle
RossSchulman[m] has joined #beagle
jduchniewicz has joined #beagle
jkridner[m] has joined #beagle
russ has joined #beagle
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
russ has quit [Ping timeout: 260 seconds]
russ has joined #beagle
CrazyEddy has quit [Ping timeout: 268 seconds]
set_ has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
lucascastro has quit [Remote host closed the connection]
lucascastro has joined #beagle
starblue has joined #beagle
set_ has quit [Ping timeout: 252 seconds]
giort has joined #beagle
giort has quit [Client Quit]
Guest58 has joined #beagle
<Guest58>
Hello, I was looking for support on the pocketbeagle. I've purchased about 36 of them, but have 3 that won't boot. Connecting to computer with SD card inside, I get a COM port registered with windows, but the lights dont indicate booting. Bad boards maybe?
<rcn-ee>
or bad microSD cage..
CrazyEddy has joined #beagle
Shadyman has joined #beagle
<Guest58>
Should I just return to the vendor for replacements then? I don't think I could troubleshoot anything on the board itself. And at this point, its just the PB connected to my computer with micro USB cable. I've tried other cables and other SD cards, but nothing seems to get them to boot.
<zmatt>
strange
<zmatt>
does the power led turn on?
<Guest58>
If you guys have any other troubleshooting tips, I'm all ears. Yes, power LED does light up.
<Guest58>
are there any reset mechanisms having to do with holding the power button while plugging in. Or anything like that?
<zmatt>
if you connect it to computer with _no_ sd card inserted, does it show up as usb network interface (RNDIS) ?
<Guest58>
in device manager?
<Guest58>
or would that be in network settings?
<zmatt>
I don't use Windows myself, but whereever you can either notice whether it shows up as usb network interface (or just in general whether it shows up as usb device)
<zmatt>
there's not really anything to reset, the pocketbeagle has no flash/eMMC
<Guest58>
It shows up in device manager as USB Serial Device (COM7)
<Guest58>
On the PB's that do work, after I plug them in, the 4 led's flash, it boots, and after some seconds, the device is recognized as a drive, and I can access it via 192.168.7.2.
<Guest58>
For these last 3 that appear to be faulty, the power light comes on, but the 4 other LED's never flash and I never see it show as a drive, and cannot access via IP.
<zmatt>
okay it showing up is a good sign, so the cpu is running and bootrom is working normally
<zmatt>
it's just not booting the sd card for some reason
<Guest58>
is there a way to test it with no SD card inserted?
<Guest58>
like perform functional tests and ensure the board is ok?
<Guest58>
I'm also always wondering if my micro USB cable supports data, and isnt just a power cable. But I have 4 cables here on my desk I keep trying all of them.
<Guest58>
that one that booted the other devices, is a little finicky. If I don't hold it just right, the board loses power. So I've tried some other cables.
<zmatt>
well, you kinda just did... checking it shows up as usb device when no sd card is inserted shows the SoC works on a basic level and bootrom is trying to boot
<Guest58>
ok, makes sense.
<zmatt>
well you said it just showed up as usb device, so clearly it's not a power-only cable
<Guest58>
yeah, i guess if it was power only, it wouldn't even show the COM port.
<zmatt>
wait actually, COM port?
<Guest58>
USB Serial Device (COM7)
<zmatt>
that's odd, it should be an RNDIS device... or does Windows just report those in a weird way?
<Guest58>
I'm not sure. Device Manager is kind of a pain. The whole screen refreshes and then good luck noticing what device was added/removed from the huge list of devices.
<zmatt>
hmm, I'm finding reports of people who have RNDIS devices showing up as COM port in Windows 10
<Guest58>
Nothing new under Network Adapters when I insert it.
<Guest58>
But yes, under Ports (COM & LPT) it shows up when plugged in and disappears when I unplug it.
<zmatt>
okay it's probably just the typical headache of getting Windows to properly recognize RNDIS devices (despite the fact that RNDIS is Microsoft's own proprietary usb networking protocol, because they couldn't be arsed to implement the one from the USB standard like every other OS does)
<zmatt>
bootrom is probably missing some detail in its usb descriptor that's required to get newer versions of Windows to recognize it as RNDIS
<Guest58>
I could try this on another machine, and see if I have any luck. Wish I still had my Macbook around.
<zmatt>
rcn-ee: you think it's possible the board ID eeprom might be misprogrammed?
<zmatt>
Guest58: Mac doesn't support RNDIS anyway, they implement the standard and not Microsoft's custom not-invented-here protocol... Linux implements both
<Guest58>
plugged into my laptop for the first time, windows told me it was setting up the device AM335X, normally means its just installing the driver for it, then a few seconds later it said that USB Serial Device (com3) was ready for use.
<zmatt>
Guest58: oh, if you try to boot from sd card, does it still show up as usb device or does it not show up at all in that case?
kveremitz has quit [Changing host]
kveremitz has joined #beagle
<Guest58>
with the SD card installed, it still shows up as a COM device, but goes no further.
<zmatt>
okay, so bootrom is falling back to usb netboot (which is the purpose of showing up as RNDIS interface) even if an sd card is present
<zmatt>
that means it either doesn't see the sd card at all (e.g. defective microSD cage like rcn suggested earlier) or it doesn't consider the sd card to be bootable (broken or incorrectly flashed)
<Guest58>
yeah, I have about 6 SD Cards here with the OS on it, including one I flashed with Debian, that I got from a page about beaglebone.
<Guest58>
I could try reflashing them.
<zmatt>
try an sd card that's known good (works in a different pocketbeagle)
<Guest58>
here's some good news, reflashed an SD, put it into one of them, and now I got the 4 lights as its booting.
<Guest58>
I wonder if somehow the new SD's were getting corrupted as they booted for the first time, leaving them in a bad state.
<Guest58>
and now I just got the "BeagleBone is ready to go" message from Windows.
<Guest58>
confirmed I can access it via IP, so it has booted now.
<Guest58>
I'll finish configuring this one, and then try the same thing with the last 2.
<zmatt>
I can't think of any plausible mechanism for them to get corrupted (especially to the point of being completely unbootable) on first boot
<zmatt>
more likely something went wrong with writing the image to sd card
<zmatt>
what are you using to write the sd cards?
<zmatt>
it's a good idea to use a program that verifies the sd card contents after writing the image to it, e.g. Balena Etcher
<zmatt>
brb
<Guest58>
I'm using the latest version of Balena Etcher
<Guest58>
After it booted, I inserted it back into the cape I'm using to control lights, tried to boot again and it wouldn't. I removed it from the cape, applied power but now it seems like it won't boot again. Not getting the page accessible via IP.
CrazyEddy has quit [Ping timeout: 245 seconds]
<Guest58>
it seems so inconsistent
<Guest58>
getting a fast heartbeat light pulse now.
<zmatt>
odd
<Guest58>
unplugged, plugged back in, the 4 lights lit up, but then they never turned off, like it froze up during that stage of boot. lights are still stuck on.
<zmatt>
the logical explanation is that these boards are inhabited by ghosts. try an exorcism.
<Guest58>
haha
<Guest58>
that seems more and more likely.
<Guest58>
the chip feels fairly warm.
<Guest58>
i wonder if a bad board or SD cage is leading to these weird issues.
<Guest58>
maybe heat related so it appears to work fine for a second and then start doing strange things?
<zmatt>
I've only heard of an AM335x overheating once, on the E2E forum, and that guy was using it in an environment with 90͏°C ambient temperature