Problem in recovery mode for VF50


I’m trying to recover two modules VF50.

I use the image version 2.5 to recovery.
When I do this, I always follows the topic of recovery mode from scratch:

Follow my log:

$ sudo ./ -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
main dcd length 8
sub dcd length 4

loading binary file(colibri-vf_bin/u-boot.imx) to 3f4078e8, skip=0, fsize=67718 type=aa

<<<423704, 423704 bytes>>>
succeeded (status 0x88888888)
jumping to 0x3f4078e8

After that, I’m able to access the console again.

Colibri VFxx # nand erase.chip
NAND erase.chip: device 0 whole chip
Skipping bad block at  0x013c0000                                          
Skipping bad block at  0x07f80000                                          
Skipping bad block at  0x07fa0000                                          
Skipping bad block at  0x07fc0000                                          
Skipping bad block at  0x07fe0000                                          
Colibri VFxx # run setupdate                                                    
reading flash_blk.img                                                           
1719 bytes read in 13 ms (128.9 KiB/s)                                          
## Executing script at 80008000                                                 
enter "run update" to update the entire module                                  
Colibri VFxx # run create_bcb                                                   
NAND erase.part: device 0 offset 0x0, size 0x20000                              
Erasing at 0x0 -- 100% complete.                                                
Write FCB...                                                                    
FCB 2048 bytes written to 0x0: OK                                               
Colibri VFxx # cfgblock create                                                  
Is the module an IT version? [y/N] y                                            
Enter the module version (e.g. V1.1B): V1.2A                                    
Enter module serial number: 04887763                                            
Toradex config block successfully written                                       
Colibri VFxx # run update                                                       
reading u-boot-nand.imx                                                         
453400 bytes read in 47 ms (9.2 MiB/s)                                          
NAND erase.part: device 0 offset 0x20000, size 0x160000                         
Erasing at 0x160000 -- 100% complete.                                           
NAND erase.part: device 0 offset 0x180000, size 0x80000                         
Erasing at 0x1e0000 -- 100% complete.                                           
NAND write: device 0 offset 0x20000, size 0x160000                              
 1441792 bytes written: OK                                                      
reading ubifs.img                                                               
47108096 bytes read in 3063 ms (14.7 MiB/s)                                     
UBI: default fastmap pool size: 50                                              
UBI: default fastmap WL pool size: 25                                           
UBI: attaching mtd1 to ubi0                                                     
UBI: scanning is finished                                                       
UBI: empty MTD device detected                                                  
UBI: attached mtd1 (name "mtd=3", size 126 MiB) to ubi0                         
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes                   
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048                    
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096                  
UBI: good PEBs: 1003, bad PEBs: 5, corrupted PEBs: 0                            
UBI: user volume: 0, internal volumes: 1, max. volumes count: 128               
UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 0  
UBI: available PEBs: 982, total reserved PEBs: 21, PEBs reserved for bad PEB ha5
No size specified -> Using max size (124690432)                                 
Creating dynamic volume rootfs of size 124690432                                
47108096 bytes written to volume rootfs                                         
resetting ...

This is my problem, I receive the message “resetting…”, but nothing happens.
In this point I’m not able to type any command. If I try reset the module by hardware I need to run the recovery mode again. The same happens if I try to turn OFF and ON the evaluation board.

What I’m doing wrong? It’s always works to me.

Thank you very much!

@witte, everything appears correct. At the very end after “resetting…” you will need to do a hardware reset/power cycle which it sounds like you have attempted. Perhaps you can try powering off and completely removing power from the board for 5+ seconds. Then try powering back on.

If it seems that the system is still is not booting, check if the module is still in recovery mode. For example, try running the -d script. If the module is still in recovery mode, then I suppose there are a few unusual ways which that could happen - perhaps the recovery mode button on the eval board is somehow stuck. Do you happen to have a 2nd carrier board?

Note that you need to powercycle the module after the update. A reset does not take the module out of the recovery mode.

@brandon.shibley and @stefan.agner,

I think the image I used was corrupted for some reason. I rebuild all and the end of the process I cut off the power. Now it works perfectly.

I apreciate your support!!!
Thank you!