I have a new Apalis IMX6 board with Ixora 1.1 board. I am unable to stop uboot from booting. It is connected to a linux PC through the serial console.
No key press are being recognised. I also tried connecting a usb keyboard directly to the board but had no luck either. Is there any other way I can stop or get to uboot menu ?
In an effort to stop the prompt at uboot, I renamed the files in the /boot folder. But unfortunately, it still autoboots in uboot and hangs at “starting kernel…”
So, I am stuck without anyway to boot the device too. Any pointers to solve this issue is appreciated.
Most possibly your serial connection is not quite proper and while you can receive you fail to transmit anything. Please check your serial connection finding some more useful information in the this and the following article on our developer website as well.
Alternatively you may also access the U-Boot environment variables from regular Linux user space as e.g. outlined in the following article.
Thanks for the suggestion, Marcel. The serial connection is working fine, I think.
If I swap the Apalis IMX6 board for a Apalis TK1 board, I am able to enter uboot prompt. Please note the only change I am making is to swap out the IMX6/TK1 boards in an Ixora carrier board.
However, with the IMX6 boards, I am not able to get into uboot prompt.
To add more information, for serial connection, we use an adapter from the Carrier board accessory kit.
After a lot of debugging, I suspect this has something to uboot settings.
The keyboard starts working the instant the device boots up to the login prompt. I think it could be due to a missing default uboot setting “stdin=serial”. I tried adding this using fw_setenv but everytime the system boots up it uses the default uboot settings with the error
" *** Warning - bad CRC, using default environment"
I am running the latest uboot
U-Boot 2016.11-2.7.2+g60021a4 (Apr 10 2017 - 02:10:44 +0200)
but the linux version is
Angstrom v2014.12 - Kernel 3.10.17
I am unable to update the OS through any method due to not being able to stop at uboot prompt. This should be a simple thing to do on a new toradex board out of the box.
The keyboard starts working the instant the device boots up to the login prompt. I think it could be due to a missing default uboot setting “stdin=serial”.
I don’t think so. At least I never ever heard of any such issue.
I tried adding this using fw_setenv but everytime the system boots up it uses the default uboot settings with the error
Warning - bad CRC, using default environment
Which just means that the environment never has been saved before.
I am running the latest uboot
U-Boot 2016.11-2.7.2+g60021a4 (Apr 10 2017 - 02:10:44 +0200)
but the Linux version is
Angstrom v2014.12 - Kernel 3.10.17
Unfortunately mixing and matching versions of things like that won’t quite work. The Linux user space u-boot-fw-utils (e.g. fw_printenv/fw_setenv) shipping in a certain BSP version are ultimately tied to whatever U-Boot version is/was also deployed with that BSP. Anything else may really give undesired effects just like what you are seeing.
This is driving me crazy. I am unable to update the OS through any method due to not being able to stop at uboot prompt.
May I ask what exact Apalis iMX6 hardware model and version you are using?
This should be a simple thing to do on a new toradex board out of the box.
Agreed, you may also try our new Toradex Easy Installer which is available here.
Thanks for your responses, Marcel.
The primary issue is that no keyboard presses are recognized until the login prompt is up. So I am unable to get into uboot prompt.
I am using Apalis iMX6 2GB IT - V1.1B bought recently but was shipped with a old BSP Angstrom v2014.12 and without toradex easy installer.
A hack (that I added commands in uboot variable to run update) to upgrade the os to 2.7 ended up half done with only the uboot updating and not the OS. Hence I am now stuck with these two versions.
I also tried the easy installer, problem is, I need to get into uboot to give “bmode usb” , and I cant get into uboot.
I was able to put the board in recovery mode and update the OS to the latest version using Toradex easy installer, without having to enter uboot.
Cheers
Thanks for your responses, Marcel.
You are very welcome.
The primary issue is that no keyboard presses are recognized until the login prompt is up. So I am unable to get into uboot prompt.
I am using Apalis iMX6 2GB IT - V1.1B bought recently but was shipped with a old BSP Angstrom v2014.12 and without toradex easy installer.
Yes, paradoxically we still ship them with an older since unsupported BSP V2.4 beta 1 which has mainly to do with the irreversible fast boot mode fusing and only the later V1.1C will ship with the Toradex Easy Installer pre-installed and consequentially fast boot mode being enabled by default.
BTW: I have such an exact Apalis iMX6Q 2GB IT V1.1B module which for me works just fine:
U-Boot 2016.11-2.7.2+g60021a4 (Apr 10 2017 - 02:10:44 +0200)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: WDOG
I2C: ready
DRAM: 2 GiB
PMIC: device id: 0x10, revision id: 0x21, programmed
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment
auto-detected panel HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Model: Toradex Apalis iMX6 Quad 2GB IT V1.1B, Serial# 04920411
Net: using PHY at 7
FEC [PRIME]
Hit any key to stop autoboot: 0
Apalis iMX6 #
Apalis iMX6 # hello
A hack (that I added commands in uboot variable to run update) to upgrade the os to 2.7 ended up half done with only the uboot updating and not the OS. Hence I am now stuck with these two versions.
OK, now I understand.
I also tried the easy installer, problem is, I need to get into uboot to give “bmode usb” , and I cant get into uboot.
Yes, alternatively one can also short some pad on the module itself as outlined in the data sheet or press the recovery button on the Apalis iMX6 Mezzanine daughter card should you have one.
Perfect, thanks for letting us know!
I had the same problem. In Windows I have forwarded the serial port to virtual-box, but after exiting the virtualbox the serial port can not send to device. So I disabled the forwarding and it got fixed. Might not be the case for you but maybe helps someone else. So I recon its a serial port issue
@rogerp
Hi,
I had the same issue, I solved it by removing the flow control form minicom
BR,
Ben
Ok, Thanks for letting us know.
Running U-Boot 2016.11-2.8.6+g83a53c1 with Toradex Apalis iMX6 Quad 2GB IT V1.1C and Ixora V1.1A. Had the same problem and fixed it by disabling flow control in minicom too.
Thanks @benrey !
Thanks for letting us know.
Yes, if using minicom one should really adhere to the following article on our developer website outlining the whole configuration: