I am on Step 18 of the Getting Started guide for reflashing a T30 going from the built-in WinCE to Linux. I get the following error:
Colibri T30 rootfs detected
./tegrarcm: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
Back in step 1 I got various “Ignore” and “Error” messages on the sudo apt-get for the libraries which probably led to this problem.
However, I have no control over the apt-get process and can only type what I am told to type. I tried the exact commands in Step 1 over and over very carefully but got a number of messages about not being able to find this or that file as it whirled by on the screen.
Even backing up to the “sudo apt-get update” command there are errors such as
“Err:50 Index of /ubuntu xenial-security/main arm64 Packages 404 Not Found …”
Its a Colibri T30 on the Colibri Evaluation Board.
The internet works and apt-get goes out and gets many things but fails on some things. If I rerun it the same apt-get failures occur over and over as if the files I was told to request don’t exist.
Then if I proceed anyway, it fails in Step 18 while running the update.sh with the message that the libusb is missing.
The internet works and apt-get goes out and gets many things but fails on some things. If I rerun it the same apt-get failures occur over and over as if the files I was told to request don’t exist
Was able to ping as described above without problems.
Started executing you second set of commands and got as far as step 46 before it failed on not finding the USB. See attached log.link text
Was able to ping as described above without problems.
This is strange. There is something wrong with your host installation. Try to do a clean install and reinstall these packages.
Started executing you second set of commands and got as far as step 46 before it failed on not finding the USB
For this, you must put the module in the recovery mode using the hardware mechanism described in the chapter 6 of the datatsheet
or enter in U-Boot and write enterrcm.
Additionally you also need to connect the USB_CL Port (X29) to the Host.
So I think we may be getting at the heart of the matter.
I have notionally 3 USB connections to the target board: x27, x29, x30. Possibly x29 and x30 are the same?
Anyway, if I only connect to either x29 or x30, I never see any /dev/ttyUSBx in the list.
If, however, I connect x27 to a USB, I see that one come up immediately as ttyUSB0 while the bootloader is counting down.
If I also connect to x30 as the instructions indicate, I see ttyUSB1 show up but only AFTER the bootloader countdown times out and the OS comes up.
I can get the bootloader menu to show up in minicom on x27 and via that port I can interrupt the bootloader and get to the menu shown. I can never get that on x30 (obviously because that ttyUSB never shows up until the OS is booted, and only if I also have x27 connected.
So, it would be nice to have clear instructions on which USB ports I should have connected and what I am supposed to see on each one as the bootloader is waiting to be interrupted. I am currently of the opinion that the instructions are not correct but will be happy to be shown otherwise.
