Hi there,
I received an RB5 Vision Kit in the mail. When I first powered it on and connected it to my workstation, it does not show up when I run `adb devices`. I have been able to interact with another non-vision RB5 from this worksation in the past.
So, I decided to try re-flashing the board. To do so, I follow the steps on the Qualcomm website, and in the README of Thundercomm's SDK Manager package. I am able to successfully build the image. When I go to flash it, with FD_L depressed, I see these errors:
commands:
help = Show usage help
1 = Download resources and generate system.img with current release
2 = Flash full build (require system.img generation first)
3 = Flash CDT build
4 = Flash NON-HLOS build
q = exit sdk manager
> 2
==================================================
Flash full build to Robotics RB5 device
The flash process will take about 5 minutes
Current image version to be flashed: QRB5165.1.0.0-210512
==================================================
Enter 'y' to continue, 'q' to main menu: y
Device found: /dev/ttyUSB0
SDK manager flashing full build...
Initializing flash ...
Erasing part0 ...
Base Version: 19.06.10.18.44
Binary build date: Jun 12 2020 @ 19:49:18
Incremental Build version: 20.06.12.19.49.18
21:46:27: INFO: User changed 'port_trace.txt' to '/home/jameson/sdkmanager/QRB5165.1.0.0-210512/erase0.log'
21:46:27: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader --port=/dev/ttyUSB0 --erase=0 --noprompt --showpercentagecomplete --memoryname=UFS --loglevel=1 --porttracename=/home/jameson/sdkmanager/QRB5165.1.0.0-210512/erase0.log
************************************************
21:46:27: INFO: Current working dir (cwd): /home/jameson/
21:46:27: INFO: Showing network mappings to allow debugging
21:46:27: INFO: User requested *semi-verbose* logging with --loglevel=1 - This is default
21:46:27: INFO: User wants to talk to port '/dev/ttyUSB0'
21:46:27: INFO: Took 0.00001100 seconds to open port
21:46:27: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
21:46:27: INFO: Sending <configure>
21:46:27: INFO: Trying to write 227 bytes
21:46:27: INFO: Just wrote 227 bytes
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
21:46:32: {ERROR: Timeout - no response trying to read from target
}
21:46:32: INFO: Didn't get any data from USB, sleeping for 1ms and trying again NumTries=1 of 10
21:46:33: INFO: Back from sleep
What's going wrong with the flash? How can I recover this device? Is it defective?
Thanks,
Jameson
I got it working! One of the following three things fixed the issue - I'm not sure which.
Glad that device is recovered and working!
Unfortuatnlly hitting the same or simiar error..
can't get the device into download mode, it says QDL mode but unsure if that is suffient, i'm using a ubuntu 20.04 vm in a vmware workstation setup the host system is linux and docker ubuntu image is running the sdkmanager
I got the non-vision rb5 to flash and work, but this F_DL switch isn't an easy nor accessaible process as you have to manage with both hands to plug in the power, hold the button down, connect the usb-c cable and then race to press "y"
Hi darragh,
There might be issues for sdkmanager to run in VM, can you use ubutun machine to run sdkmanager.
To make device to QDL mode, you can do in this way:
1. unplug power onnector
2. connect USB cable to host
3. hold F_DL button, and plug power connector and hold 3~ 5 seconds, the device will enter QDL mode
Thanks
Kevin