We normally flash our custom linux image (based on V2.3) onto the Colibri T20 modules with the provided ‘update.sh’. This has been working for at least over 400 modules.
However in the latest lot of 20 modules there were 2 modules which stopped at ‘waiting for bootloader to initialize’.
These 2 modules seem to be from a different production lot. Their serial numbers are 10707188 and 10707187, whereas the serial numbers of the 18 working modules all start with 066xxxxx.
Here the flash log:
vo@PC033:~/Schreibtisch/xbbz4v-image-Colibri-T20_V1.0r6$ ./update.sh -r 512 -v V1_2 Colibri T20 rootfs detected LD_LIBRARY_PATH=../t20_nvflash ../t20_nvflash Nvflash version 19.0041 started rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x0359b007437ff057 macrovision: disabled hdcp: enabled sbk burned: false dk burned: false boot device: nand operating mode: 3 device config strap: 0 device config fuse: 4128 sdram config strap: 0 sending file: ColibriT20_333_512_V1_2_nand.bct - 4080/4080 bytes sent ColibriT20_333_512_V1_2_nand.bct sent successfully odm data: 0x1 downloading bootloader -- load address: 0x8300000 entry point: 0x8300000 sending file: loader.nb0 \ 360208/360208 bytes sent loader.nb0 sent successfully waiting for bootloader to initialize