I am trying to get to the U-boot/Kernel terminal to TFTP Boot my image but I cant open the terminal to do these commands:
setenv ipaddr
setenv serverip
tftpboot ${loadaddr}
I held ENTER || SPACE while in serial debug console after reboot/reset but no success.
Please help
Hey @blouisb2,
Would you mind giving a bit more information about your setup?
What image are you booting on the module? Is this a stock image from our Easy Installer?
What carrier board are you using?
And if you could provide the boot log from minicom via a text format instead of a picture that would be easier to pull information from.
Thanks
-Eric
Good morning,
I am using Apalis iMX8- carrier board: iXora.
it’s a customized image, the image work perfectly when loaded from SD card using the Easy Installer Gui. Now I put the same image in a directory to load it from a TFTP server.
Attached is the minicom boot log .txt
I really appreciate your quick reply.
minicomLog.txt (42.2 KB)
Hey @blouisb2,
When you mean the image works perfectly… You are referring to being able to enter the u-boot console?
And when you are trying to load your image via TFTP, is this from an image currently on the board or the easy installer?
-Eric
Hi,
I meant loading the image from SD card using the Easy installer works perfectly.
Now, I cannot get to the U-boot console to load it { the same image} via TFTP; The image is not on the board when trying to load it from TFTP.
Do you know if you have customized u-boot environmental variables? bootdelay = 0 will not allow the console to appear. You can check this from user space via fw_printenv in the linux shell.
A second possibility is something is not quite right with your serial terminal. Can you try the process with default image. This will allow us to isolate either the process or the image.
-Eric
-Eric
I will go with option 2 since I cant write anything from keyboard to the shell {in minicom} once the boot log start then stop. I will let you know in a few how option 2 goes. Thanks
The final message from your boot logs suggest you should be able to log in. apalis-imx8-07307207 login:
Are you not able to type root as the login nameonce you see this message? You may have to hit enter a few times to scroll down the text line.
-Eric
Yes, I am able to login as root when plugin a keyboard directly to the board. but this is not what I wish to accomplish.
I would like to accomplish the followings:
1- turn on the board while the serial debug is connected to a host computer.
2-minicom -D /dev/ttyUSB0 command on the host computer.
3-while the board is turning on: Able to press ENTER or SPACE on the host computer to enter Uboot console {via minicom}.
4- Once in Uboot console, typing these commands:
→ setenv ipaddr
→ setenv serverip
→ tftpboot ${loadaddr}
To load a live image from the TFTP server.
//------
So far, #3 is not happening. Hence, I cannot type the commands.
By the way i check: bootdelay = 1
It sounds like there may be a setting in minicom that is not allowing you to input characters. Can you go to your minicom serial port settings and check if Hardware Flow Control and Software Flow Control is set to No? There may be other settings effecting communication.
-Eric
Good morning.
I tried with Putty, no success either.
This is my minicom setting:
| A - Serial Device : /dev/modem |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| H - RS485 Enable : No |
| I - RS485 Rts On Send : No |
| J - RS485 Rts After Send : No |
| K - RS485 Rx During Tx : No |
| L - RS485 Terminate Bus : No |
| M - RS485 Delay Rts Before: 0 |
| N - RS485 Delay Rts After : 0
Hey @blouisb2,
It looks like Hardware Flow Control is set to Yes. Can you change this to No and try again?
With Putty, not being successful… This means you can shell into the device with putty, but are not able to provide inputs via the putty shell?
-Eric
O my, it works by changing it from [Yes-to-No] ; then hold the SPACE bar while rebooting.
i can do the commands such as:
→ Apalis iMX8 # setenv ipaddr 10.xx.xx.xx
→ Apalis iMX8 # setenv serverip 10.xx.xx.xx
I really appreciate it.
//--------------------------------------------------------------------------------------------------------------
Same issue with putty I was not able to provide input {setting issues}.
//--------------------------------------------------------------------------------------------------------------
Thanks again.
Awesome! Glad I can help. Do you also want to try and figure the issues with putty, or comfortable with using minicom?
-Eric
I prefer minicom
Again, thanks for all Eric.
