When I boot my board, while I am reading the kernel boot process via minicom, I can not access bootloader menu with pressing [SPACE], also there is no any prompting message “Press [SPACE] to enter Bootloader Menu”
Could you provide the version of the hardware and software for your module? Unfortunately this picture does not help a lot. Could you provide a complete boot log? Try to restart the module, once you are in Linux (command reboot)?
No, this is not a complete boot log. Please provide the complete boot log off the entire boot sequence. Please also indicate the exact hardware and software versions of things you are exactly talking about. Thanks!
I have configured my minicom settings just like you supported me, and something is changed, now there is new problem. When the board is booting I press a key and it just stops the booting, but that’s it, only stops and nothing is coming out…
And here is new output according to new settings link text
Once it is booting, I cannot enter anything, no any text, also with new configurations again I cannot not enter any text, but now if I press a key starting of boot process, it stops, but only stops and nothing comes again.
OKEY PROBLEM İS SOLVED, I JUST USED SUPPORTED MINICOM SETTINGS AND NOW I AM ABLE TO LOG IN UBOOT MENU
I have the same essential problem! I have an imx6 apalis SoM in an Ixora carrier board. I tried to follow the same flashing instructions in the link above with no luck, as I could never get the uboot to appear at all via minicom. I did, however, manage to flash Linux LXDE on to the board via the Easy Installer and a flash drive.
But I still can’t interact with the uboot at all even after that! Nothing is displayed in minicom when I’m plugged into port X22 and my host machine tells me it has a usb connection, and I’ve set those exact specs posted for minicom… It’s like there is a jumper setting or some other detail missing here to enable access…
Here’s a pic, but I don’t think there’s anything much to see there. I’m 99% sure they are plugged in correctly. But, could there be a driver issue, etc. ? I using Ubuntu 16, which comes with FTDI drivers. I also tried Windows 10 with Tera Term. Neither worked, despite indicating a serial connection.