I have setup a serial console debug using Putty (baud rate of 115200, 8 data bits, no parity and one stop bit without hardware/software flow control) on Debian 6 - VMware Player virtual machine. I am trying to find out why some T20 boards do not load the operating system after flashing is complete and without any errors, while others work perfectly fine.
Small screenshot of image loading OK:
[upload|AdHEtvN5Rv8756cjjeEzZhGjFGE=]
Missing Colibri config block was listed for non-working boards:
But the next command (cfgblock create) cannot be found:
[upload|9qTaDCXHjOGPTR7ZyAt+QhTVSN0=]
I have tried re-flashing after erasing the entire NAND. After flashing was complete successfully and Evaluation board rebooted, the same error regarding missing config block appeared on the serial debug console.
In the old stable BSP V2.3 there should be a create_configblock.sh script as well as a -c argument to the update.sh script selecting configblock partition only update.
./update.sh -r 512 -v V1_2 . Then the Evaluation board was rebooted (holding down Recovery mode).
Step 2.
./update.sh -c -r 512 -v V1_2 which fixed the missing Colibri config block error.
Again after this, the Evaluation board was rebooted holding down Recovery mode
Step 3.
kernel updated using ./update.sh -r 512 -v V1_2 -k
No errors reported for all the above three steps.
Using the serial debug console (cutecom) and logging all the data to a file, then doing a diff on normal vs non-working case, it looks like the non-working board stopped after Initialized tegra uart driver.
Part of the diff:
[upload|P+NQRhqYAa70zk4nIUo2gS3FEZo=]
Top section zoomed in:
[upload|7tpktDjh099gpsRQeZneK/naGcU=]
Any ideas what this means?
Also is there a limit on how many times can the Colibri T20 be flashed?
Doing a NAND erase prior to Step 1 hasn’t helped. Is there anything else I need to do before flashing or can those commands (from Step 1 to Step 3) be run over and over again?
We ordered two new Toradex boards (same ColibriT20) and this time there were no problems after the flashing has been completed (same custom made image). It was really straightforward and they worked after the first attempt.
Could it be a hardware issue? Could the other two that are not working come from a broken batch? (their SN are 10523798 and 10524174 if it helps).
A responsible of Toradex will contact you by E-Mail and give you instructions how you can the non-working modules back to Toradex. Once we got the modules, we can examine them and find the root cause of the error.