https://turingpi.com logo
Powered by
#β”‚forum
Cannot reach the computer modules via usb
# β”‚forum
p

padigru

04/13/2023, 5:03 PM
i cannot access any node via USB to flash. I've done everything the docs say (https://help.turingpi.com/hc/en-us/articles/8687165986205-Install-OS). None of the nodes can be reached via USB via host-mode. I've tried several USB cables. Where could the problem be? I have CM4
u

_dhanos_

04/13/2023, 7:07 PM
Are you using USB A-to-A cable? USB A-to-C work rarely for this purpose
p

padigru

04/13/2023, 7:23 PM
I have use both of them
u

_dhanos_

04/13/2023, 7:25 PM
Can you describe the whole process step by step with all the actions and commands? Let's try to find what might be wrong
p

padigru

04/13/2023, 7:32 PM
Sure. I think it's the same Problem, like in the Chat actually. If I connect a monitor I saw the nvme error. To the process: I connect the USB cable to the USB port next to the hdmi port and then I start the rpiboot Programm with sudo ./rpiboot and after that I use the command tpi -u device -n 1 (I tried other nodes also). But it doesn't connect or find the node
u

_dhanos_

04/13/2023, 7:36 PM
You need to keep the node powered off, and power it on only after you set the device mode.
In other words you must first set the node into device mode then power on the node, otherwise the CM4 will try to boot instead of be ready for flashing
s

shadowbumble

04/13/2023, 7:38 PM
The docs say this the other way around, first power on ( or it states it assuming that it's powered on ) before running the tpi -u device -n 1 took me while also to figure that one out
p

padigru

04/13/2023, 8:01 PM
just tried it. unfortunately it still doesn't work 😦
u

_dhanos_

04/13/2023, 8:05 PM
Make sure to try node other than Node 1
Also, the command is 
sudo rpiboot -d .\msd
(assuming you 
cd
-ed into the directory with rpiboot
p

padigru

04/13/2023, 8:20 PM
-d .\msd dont work on mac
u

_dhanos_

04/13/2023, 8:20 PM
It does
What do you mean by "don't work"?
p

padigru

04/13/2023, 8:21 PM
No 'bootcode' files found in '.msd'
Try it on Windows now
u

_dhanos_

04/13/2023, 8:22 PM
Did you 
cd
to the folder where the 
rpiboot
is installed?
p

padigru

04/13/2023, 8:22 PM
Yes in the git repo
u

_dhanos_

04/13/2023, 8:23 PM
Did you type in 
.msd
instead of 
./msd
?
p

padigru

04/13/2023, 8:23 PM
./msd working πŸ˜…
u

_dhanos_

04/13/2023, 8:25 PM
p

padigru

04/13/2023, 8:29 PM
But don't connect 😦
u

_dhanos_

04/13/2023, 8:29 PM
What do you see?
p

padigru

04/13/2023, 8:29 PM
Only "Waiting for BCM2835/6/7/2711..."
Tried node 2
# tpi -u status { "response": [{ "mode": 1, "node": 1 }] }
u

_dhanos_

04/13/2023, 8:32 PM
Without touching anything else, can you turn the node power off and on and see what happens?
p

padigru

04/13/2023, 8:33 PM
With key1 or web?
u

_dhanos_

04/13/2023, 8:33 PM
Both will work for this purpose
p

padigru

04/13/2023, 8:34 PM
Nothing happend. They turn on and off
u

_dhanos_

04/13/2023, 8:35 PM
On and off? Are you sure?
Not off and on?
p

padigru

04/13/2023, 8:36 PM
You're right off and on πŸ˜… . Sorry it's late here πŸ˜„
u

_dhanos_

04/13/2023, 8:36 PM
And it's still like this?
p

padigru

04/13/2023, 8:36 PM
Yes
u

_dhanos_

04/13/2023, 8:37 PM
I'm not sure what are you doing wrong, then
Are these CM4s with eMMC?
p

padigru

04/13/2023, 8:37 PM
i'm too πŸ˜…
Yes of course
u

_dhanos_

04/13/2023, 8:37 PM
Did you put anything into the Mini PCIe slots?
p

padigru

04/13/2023, 8:38 PM
No, only battery, power and three nodes
u

_dhanos_

04/13/2023, 8:41 PM
Ok, let me try to put some step by step instruction: - put all node power off - set usb mode to device for node 2 - connect the USB A-to-A cable - run the rpiboot - turn the node power on The red LED should turn on next to the node, but no the green one on the other side of the node. 
rpiboot
should pre-flash the module Also try other USB ports in your PC
p

padigru

04/13/2023, 8:52 PM
I have try it. The Result is interesting. The Mac don't detect the device. Windows, says "device not recognized"
u

_dhanos_

04/13/2023, 8:57 PM
Have you tried different USB ports?
p

padigru

04/13/2023, 9:00 PM
Yes
u

_dhanos_

04/13/2023, 9:04 PM
Did you try node 3?
Something's wrong and I'm unsure what
p

padigru

04/13/2023, 9:09 PM
node 3 same issue. Tomorrow i receive a new USB-A to USB-A cable. Maybe the cable is broken
u

_dhanos_

04/13/2023, 9:09 PM
Ok! I ran out of ideas
p

padigru

04/13/2023, 9:10 PM
I feel it
c

clarkezone

04/14/2023, 1:11 AM
i have exactly the same issue as this
i tried same steps on a different windows machine and i see this when powering on the node:
g

gromboli

04/14/2023, 1:32 AM
I'm also having this issue. I've tried three different computers and two different cables. I'm completely out of ideas. In Windows Device Manager under Universal Serial Bus controllers it says 
Unknown USB Device (Device Descriptor Request Failed)
.
I'm running BMC version 
1.0.1
.
c

clarkezone

04/14/2023, 1:35 AM
darn.. looks like this is broken. Same here, also on 
1.0.1
g

gromboli

04/14/2023, 1:42 AM
Node 4 just worked for me!
n

Netscruff

04/14/2023, 1:43 AM
I've had luck with slots 3 & 4 but not 1 & 2
a

apple4ever

04/14/2023, 2:05 AM
Alright glad its not just me
g

gromboli

04/14/2023, 2:06 AM
Slot 4 has worked for writing to two of my CM4's. I wish I tried this slot earlier.
a

apple4ever

04/14/2023, 2:23 AM
AHHH this is also part of my problem! This was not clear at all.
Yup, just got that one connected for me too
g

gromboli

04/14/2023, 2:32 AM
Curious why slot 1 and 2 weren't working.
m

merlinvn

04/14/2023, 5:29 AM
Follow those instruction for CM4 with eMMC, I'm using both MacOs and Windows, and none of the 4 nodes work...
Flashing CM4 with waveshare IO board works...
s

shadowbumble

04/14/2023, 6:06 AM
I have 4x CM4 8/32 and Node 2,3,4 works for me (but first setting tpi -u device -n x and then powering on the module) 1 is being his unusual self of being stubborn. had to use a short USB-A to USB-C cable tho everything longer then 50cm gave no response on rpiboot.
m

merlinvn

04/14/2023, 6:11 AM
Thanks, I'll look for short 50cm cable, and re-try πŸ˜…πŸ˜…πŸ˜…
s

shadowbumble

04/14/2023, 6:15 AM
And give it some time, it's experimental hardware it needs some tlc ;), Boot TPi2 board but make sure all nodes are off from BMC. (tpi -p off) Then setup rpiboot so that it's listening, wait a minute or so then on the BMC shell do "tpi -u device -n X" (where X is the node# 1,2,3,4) and use the API to turn on the matching specific node (keep the rest off). The rpiboot listener you setup should respond within max 20 secs (slowest i measured, usually it's within 5 secs). After flashing etc power off the node again wait a minute rinse and repeat.
u

_dhanos_

04/14/2023, 7:48 AM
We know that Node 1 can be problematic for flashing, but Node 2 was never a problem, really. Did you put any Mini PCIe card into the Mini PCIe slot?
USB A-to-C cable rarely works. The length does not really matter. Most llikely you'll need USB A-to-A cable
This is odd, because the rpiboot should react immediately, there's no need for delay and you can power up all of the nodes at once if you wish so
s

shadowbumble

04/14/2023, 8:00 AM
Yeah didn't find a root cause for it either, but switching fast between nodes ( and remember the need to be set in device mode before powering on so it has no use to power everything on since not everything can be in device mode at the same time ) gave me lots of problems so i decided on this approach which worked fine.
btw even if the BMC allows device mode on all nodes rpiboot doesn't support it to do 4 nodes at the same time πŸ˜‰
u

_dhanos_

04/14/2023, 8:13 AM
You can only set a single node into the device mode - the one of your choice. What this does is routes the USB connection to this node and puts the node into the flashing mode
p

padigru

04/14/2023, 9:55 AM
Now it works for me. I have use a USB-A to USB-C cable and my windows computer.
Thank you @_dhanos_ for your help.
I had the same problem. The solution was a different cable.
g

gromboli

04/14/2023, 11:56 AM
No Mini PCIe cards. I did have a USB to UART adapter attached to the board that was causing issues as well, so maybe slot 2 will work now. I’ll test when I receive my last CM4 adapter board.
c

clarkezone

04/14/2023, 1:07 PM
I will try slot 2 and 4 and a short A to C cable which I have. if that doesn’t work will try ordering a A to A cable
m

merlinvn

04/14/2023, 1:50 PM
I used both USB A-A and USB A-C, none of those appear to work...
a

apple4ever

04/14/2023, 2:47 PM
Yeah I think that's really the best solution, outside of netbooting lol
For me seems like only node 4 is flashable
m

merlinvn

04/14/2023, 2:55 PM
Just wonder is it related to usb cable, all my cables are USB 3.0, not 2.0... πŸ˜…
a

apple4ever

04/14/2023, 2:55 PM
Hmm maybe. But for me, node 3 kept erroring, but node 4 seems to work
Though I do get an error about storage at the end Β―\_(ツ)_/Β―
m

merlinvn

04/14/2023, 2:56 PM
Are you flashing by internet or pre-download image?
a

apple4ever

04/14/2023, 2:56 PM
Via the Rasperry Pi Imager
m

merlinvn

04/14/2023, 2:57 PM
sure, but did you pre-download the image or just simply chose the os the Imager will download and flash over internet?
I have to pre-download the image and flash using the custom option, the flashing over internet always has problem at the very end πŸ˜…
a

apple4ever

04/14/2023, 3:06 PM
Oh sorry didn't understand your terminology
I chose the image the downloaded
If this next one fails, I'll try downloading it myself
u

_dhanos_

04/14/2023, 3:22 PM
Mine is also 3.0
Did you power teh node off, set USB mode to device and THEN power the node on? Did you try multiple USB ports? What's the command with rpiboot you used (does it include the msd poart)?
m

merlinvn

04/14/2023, 3:24 PM
Yup, I tried all of these. I will re-try it tonight.
a

apple4ever

04/14/2023, 6:16 PM
This is so frustrating
I've given up, will try flash drive and then cloning, and then later do netboot
u

_dhanos_

04/14/2023, 7:01 PM
What's your current problem? I know you wrote it somewhere above, but so many people are asking about flashing currently
a

apple4ever

04/14/2023, 7:02 PM
Bunch of problems. Sometimes can't mount eMMC, sometimes it says mounted but doesn't show up, sometimes it images but doesn't boot.
Have yet to have a successful flash
Been using Node 4 slot
(Seems like a lot of people are having problems - sorry to bug you!)
u

_dhanos_

04/14/2023, 7:10 PM
And I'm not sure why do you have so many issues. I have 2 boards and only experienced issues in Node 1
a

apple4ever

04/14/2023, 7:18 PM
Yeah I don't know why either
c

clarkezone

04/14/2023, 7:32 PM
I got it working finally. The key was a short USB A-C cable.. I used one that was about 5-6 inches long. Anything longer failed. With that, I also found the following: 1) Single CM4 node in slot 1 failed. Saw Loading: .\mid/boot oder.bin, sending boot code.bin, failed to write correct length, returned 0 2) Moved single node into slot 4. Nothing worked at all 3) Put another CM4 in slot one and kept one in slot 4. Attempted to flash to slot 4. This finally worked. Although on first power up, after boot was sent, opened disk amanagement and it hung. Powered off slot 4 and back on, leaving disk management open and second time it worked and I could flash. In order to flash the other node had to swap 1 and 4, repeated the process and it worked. Summary for me: 1) Use short cable 2) Flash in slot 4 3) ensure there is a module in slot 1 as well
u

_dhanos_

04/14/2023, 7:34 PM
Node 1 can indeed be problematic with flashing and you should use Node 2-4 if this is a case for you (and it is). I'm not sure, however, how keeping a module in Node 1 could change anything.
c

clarkezone

04/14/2023, 7:34 PM
it did for me. Have you tried a single node in slot 4?
u

_dhanos_

04/14/2023, 7:35 PM
I probably tied all of the combinations already πŸ™‚ I flashed my nodes countless times and tested things in various ways πŸ™‚
a

apple4ever

04/14/2023, 7:40 PM
Maybe it is my cable, because I get things like tihs
Copy code
$ sudo ./rpiboot
RPIBOOT: build-date Apr 12 2023 version 20221215~105525 21ba5119
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Failed control transfer (-7,24)
Failed to write correct length, returned -7
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Failed control transfer (-7,24)
Failed to write correct length, returned -7
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Failed control transfer (-7,24)
Failed to write correct length, returned -7
(flash drive cloning didn't work either sigh)
m

merlinvn

04/14/2023, 7:47 PM
why my usb-a-c cable work with the cm4 io board πŸ˜…? ... If the cable is not working with CM4, will it work with Jetson Nano?
u

_dhanos_

04/14/2023, 8:18 PM
This is indeed odd. Maybe different cable or USB port could help, but hard to guess
Can you elaborate?
m

merlinvn

04/14/2023, 8:44 PM
I'll test with Jetson Nano tonight to see how it goes
a

apple4ever

04/15/2023, 12:38 AM
I did indeed try a different port and now have had two successful flashes!
u

_dhanos_

04/15/2023, 12:48 AM
Great to hear!
b

bolen_

04/15/2023, 1:37 AM
I had trouble getting mine to work with an USB-A to USB-C cable. I was using a direct port on my Macbook (listed as USB 3.1). Eventually I put a USB 3.0 hub in between (my monitor actually) and then it worked. Might be worth trying if you're having issues.
u

_dhanos_

04/15/2023, 9:20 AM
Which hub did you use?
b

bolen_

04/15/2023, 1:57 PM
It was my LG 5K built-in usb-c hub
u

_dhanos_

04/15/2023, 3:57 PM
OK, can you say more about how it's being connected to your MAC and what ports does it expose? Did you connect it via USB-C and it exposes USB-A? or USB-C still?
b

bolen_

04/15/2023, 3:58 PM
The monitor is connected to my Macbook via Thunderbolt 3 (usb-c like connection), then it exposes a 3-port usb-c hub. So I was still using an USB-A to USB-C cable from the turingpi to the monitor's USB-C port.
My Mac's "System Information" utility says that my regular (direct) ports are on an USB 3.1 Bus, while the monitor's hub is on an USB 3.0 Bus. I don't know if that makes any difference.
u

_dhanos_

04/15/2023, 4:11 PM
Thank you! This might be important and help people in the future
m

merlinvn

04/16/2023, 5:42 PM
My updates, only node 3 and 4 work for CM4. For Jetson Nano, Im too layzy to setup ubuntu to install sdk manager so I used the old man method, using the carrier board to set up headless. But now the Nano cannot connect to network (while it can with the carrier board) πŸ˜…
u

_dhanos_

04/16/2023, 6:09 PM
I'm trying to find out what do you mean. To flash a Nano, you need ubuntu 18.04.
m

merlinvn

04/16/2023, 6:26 PM
I don't have Ubuntu, so I flash image to sdcard. I also want Nano run in headless mode, but the uart on tp2 did not work, so I have to use the nano dev board to config headless mode. When replug to tp2, there is no network, I can uart to the board. Will try to see how to reset and detect network.
u

_dhanos_

04/16/2023, 6:26 PM
OK, so 3 things
1. You don't need Ubuntu if you are using an SD card indeed - just flash the image using any tool you like
2. The UART work but is not the one you think it is - the default one is connected to BMC and you could use it through BMC
3. Which revision of Nano this is? A02 or B01?
--- As for the UART from BMC:
Copy code
microcom -s 115200 /dev/ttyS1
UARTs:
Copy code
Node 1: /dev/ttyS2
Node 2: /dev/ttyS1
Node 3: /dev/ttyS4
Node 4: /dev/ttyS5
m

merlinvn

04/16/2023, 6:33 PM
I think there is no difference between A02 and B01, the differences are for the carrier board.
u

_dhanos_

04/16/2023, 6:33 PM
There is a difference. Nvidia has changed the pinouts
A02 is not compatible with Turing Pi 2
The only thing you get from A02 in Turing Pi 2 is UART
I have A02, by the way πŸ™‚
m

merlinvn

04/16/2023, 6:36 PM
I have 3 different Nano, mix-match of A02 and B01 but none seem to work when using sd card flash method
u

_dhanos_

04/16/2023, 6:37 PM
B01 should work fine. Make sure you know which one it is
m

merlinvn

04/16/2023, 6:38 PM
I setup and work correctly on the carrier board, but when I replug to tp2, the network appear not working
u

_dhanos_

04/16/2023, 6:39 PM
This will be true for A02, B01 should work no problem
m

merlinvn

04/16/2023, 6:40 PM
Is there any way to tell if your board is A02 or B01?
u

_dhanos_

04/16/2023, 6:40 PM
Yes, you can find that on the module in one of teh corners on the back
m

merlinvn

04/16/2023, 6:42 PM
Right, I got 2 A02 and 1 B01
Voila, B01 works
πŸ˜…
u

_dhanos_

04/16/2023, 6:46 PM
Sadly the other 2 won't 😦
m

merlinvn

04/16/2023, 6:47 PM
Speechless πŸ˜…πŸ˜…πŸ˜…
u

9600

04/20/2023, 5:21 PM
Glad to see I'm not the only one having issues! I can occasionally get drives temporarily mounted in OSX but all writes fail. Absolutely no luck in Windows. Are folks having better experiences with Linux proper? I've tried 3 different A -> A cables and two A -> C with little change in behavior.
Has anyone come up with a consistently working methodology?
m

merlinvn

04/20/2023, 6:02 PM
If writing fails towards the end of the writing, try writing custom image with the pre-downloaded images.
u

unamanic

04/20/2023, 7:02 PM
I have the best luck with a USB-A to USB-A cable connected via a USB 2.0 hub.
u

9600

04/20/2023, 7:10 PM
So its funny you mention the 2.0 hub, as I was just coming here to post about that.
A -> A -> powered USB 2.0 gets me flashing reliably. Albeit very slow.
eMMC disk transfer occurs in bursts of 5MB every 20-30 seconds but active time is 100%.
If I use an SD card will USB storage mode default to SD instead of eMMC?
u

_dhanos_

04/20/2023, 7:49 PM
If your CM4 has eMMC, you cannot use SD card, the traces are eitehr connected to the eMMC or SD card
Is this also for nodes other than node 1?
u

9600

04/20/2023, 7:51 PM
Yes.
But I was able to image node 1, it just took a few hours. πŸ™‚
u

_dhanos_

04/20/2023, 7:52 PM
Node 1 can be problematic. Nodes 2-4 should work well for flashing
u

9600

04/20/2023, 7:52 PM
Using the USB 2.0 hub on a USB 2.0 port has resolved some of the usb mode issues i was experiencing.
o

one.true.beepdog

04/27/2023, 3:31 AM
I'm experiencing this on node 1, I thought I remember reading this, and I'm glad I found it again. Is this something that'll be fixed? or is it just a hardware flaw of some sort?
u

_dhanos_

04/27/2023, 3:32 AM
This seems to be hardware-related. I cannot think of any way to fixt it via a firmware upgrade, but I might also not know something.
o

one.true.beepdog

04/27/2023, 3:32 AM
it's only for flashing right? Everything else seems to work fine?
u

_dhanos_

04/27/2023, 3:34 AM
If you put a CM4 in Node 1 and will try to use the same USB_OTG port to connect a USB device (like, for example, keyboard/mouse receiver), you might also experience some issues since it's the same USB connection that serves both cases. I've heard some powered USB hubs can help (a few people mentioned this). And yes, this affect the USB connection to the back port only, nothing else
o

one.true.beepdog

04/27/2023, 3:35 AM
Mkay, that's not ideal, but it's not a showstopper
u

_dhanos_

04/27/2023, 3:36 AM
Yeah, you usually flash the node once and forget. You can try to flash it in node 1 still, for example with a USB hub, or move the module into another node. It's yet not known if this will also affect flashing from the BMC in the future (like in the future you'll be able to flash a module from the BMC's interface directly without any cables and this might work just ok)
o

one.true.beepdog

04/27/2023, 3:37 AM
Yeah I'm hoping the BMC flash mechanism will work great
u

_dhanos_

04/27/2023, 3:38 AM
I should, but I can see a challenge in flashing the Jetson modules this way. CM4s should be easy
o

one.true.beepdog

04/27/2023, 3:40 AM
Hopefully the rk1s will also be super easy to flash via BMC
u

_dhanos_

04/27/2023, 3:41 AM
I guess they should. Nvidia's modules are quite specific speaking of flashing
o

one.true.beepdog

04/27/2023, 3:42 AM
heh, just nvidia things
14 Views
Powered by