Hi,
I’m trying to use a Colibri vf61 board with Linux. The board looked like it had a problem in NAND, so I’ve tried this tutorial Flashing from Scratch, but the board crashed after the command “run setupdate”
.
I’m now trying to follow the recovery tutorial, but when I open the terminal after that the board does not respond (the u-boot does not seem to be running).
./update.sh -n -d /dev/ttyUSB0
Colibri VF rootfs detected
Put the module in recovery mode and press [ENTER]...
config file <vf_flash/vybrid_usb_work.conf>
parse vf_flash/vybrid_usb_work.conf
starting associating phase.
association phase succeeded, response was 0x23454523
HAB security state: development mode (0x56787856)
== work item
filename colibri-vf_bin/u-boot.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
No dcd table, barker=402000d1
loading binary file(colibri-vf_bin/u-boot.imx) to 3f4074e8, skip=0, fsize=73b18 type=aa
<<<473880, 473880 bytes>>>
succeeded (status 0x88888888)
jumping to 0x3f4078e8
U-Boot should definitely be responding after that command.
Can you try using && to get the serial console as early as possible, e.g.:
./update.sh -n -d /dev/ttyUSB0 && screen /dev/ttyUSB0 115200
Which carrier board are you using?
Hi, Thanks for your reply.
I’m using a custom carrier board, with I have already been able to recover a Colibri Vf50. I tried to do with the && and got:
user@user:~/Colibri-VF_LXDE-Image_2.7.4$ ./update.sh -n -d /dev/ttyUSB0 && screen /dev/ttyUSB0 115200
Colibri VF rootfs detected
Put the module in recovery mode and press [ENTER]...
config file <vf_flash/vybrid_usb_work.conf>
parse vf_flash/vybrid_usb_work.conf
starting associating phase
association phase succeeded, response was 0x23454523
HAB security state: development mode (0x56787856)
== work item
filename colibri-vf_bin/u-boot.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
No dcd table, barker=402000d1
loading binary file(colibri-vf_bin/u-boot.imx) to 3f4074e8, skip=0, fsize=73b18 type=aa
<<<473880, 473880 bytes>>>
succeeded (status 0x88888888)
jumping to 0x3f4078e8
[screen is terminating]
user@user:~/Colibri-VF_LXDE-Image_2.7.4$
Hm, since screen just terminated there is probably a permission issue? I would make sure to setup you host linux system such that your Linux user has access rights for tty’s…
Or just start screen as root:
./update.sh -n -d /dev/ttyUSB0 && sudo screen /dev/ttyUSB0 115200
Hi Stefan,I’ve tried your suggestion, but the board still does not respond.
hi, what was output in the console when you provided the command with sudo rights? Do you have native Linux or are you using Virtual Machine? How did you connect the carrier board to your host, directly or using a Hub?
