Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You cannot do that directly. You would need to use a USB/Ethernet or USB/Serial interface on your SBC. In addition, you will need to have an appropriate driver for the USB dongle loaded and installed on the Linux SBC. Potentially, you could run the SBC Linux with the USB-Gadget driver installed, and doing so would make the SBC look like a USB Mass Storage device (thumb drive).
Hi, thanks for reply. I connected my Linux SBC via USB/Serial and this connection was appeared in my PC Linux as /dev/ttyUSB0, not as disk. Because I don't have display in my SBC so I want to issue commands from my PC Linux. I need commands, how I can control my SBC Linux from my PC Linux.
Either I don't understand your question, or you have misread what I said previously.
I assume your SBC does not have ethernet. If it does, I would recommend using that to effect a login.
You can attach a USB/Ethernet adapter to the SBC USB interface, along with the appropriate driver in the SBC. This will make the SBC have ethernet, after which you should be able to attach your Linux PC to the SBC using traditional networking methods, probably ssh.
Alternatively, use a USB/Serial interface on the SBC, again along with the appropriate driver. This should allow you to run a getty process on the serial port of the SBC. Then, using a serial port on a PC running Linux or Windows, you can then login to the SBC using a terminal emulator, such as minicom or C-Kermit, using a serial port on the PC, and the USB/Serial interface on the SBC.
The only way to make a direct connection between the PC and SBC using only USB interfaces would be if one of the hosts has the USB interface set up as a non-host-control interface; ie USB-gadget driver. Two USB host-control-interfaces can't talk to each other.
Replace the dotted-decimal IP with the IP or IP name of your SBC, and use a username appropriate to your SBC.
For more info, consult the man pages. Secure shell access is generally preferred over telnet, due to increased security. Telnet is a much lighter weight protocol, and on single board computers, may be the only supported protocol.
Thank you very much for your involved in helping me. The problem is that I bought the board on the stock market and no get drivers and no information about the system. But I was able to connect to the SBC Linux via USB/Serial, but during boot there is a kernel panic and system suspend
Okay, this is a whole different question. Here is what we know:
the flash disk from which the SBC boots appears to be either faulty (numerous bad blocks), or at the very least, contains bad data.
there is a boot loader, and that boot loader at least seems to acknowledge the possibility of doing a network boot
the existing kernel image seems to be intact (checksum okay)
To restore the system, you will need to re-write at least part of the NAND flash filesystem, possibly containing an initrd or other root filesystem. Without knowing any details of your system, I cannot tell whether this can be done by a running kernel or userspace application, or whether it requires the use of something like a JTAG interface, or whether it is totally bricked. You are going to need to somehow figure this out.
An alternative might be to mount an NFS root filesystem, if you can use the bootloader to pass the appropriate kernel arguments. I don't know how/where you would possibly acquire such a thing, however.
You are facing a monumental job to get this thing working. If it is just a hobby or learning exercise, you may find some benefit in it. If there is a real-world purpose to this, then I recommend moving on to something that actually boots, and has documentation and vendor support. I don't like to be the bearer of bad news, but I think it looks like either the device was damaged in transit, or you were sold someone else's junk.
Maybe even this will help. When I reset the board I have 3 seconds to cancel the operation. Then I send the ENTER key character (and only then) and cancel the reset. After canceling the operation, I have a prompt from the U-Boot>. The problem is that if I can not send anything from the keyboard, or I have something misconfigured in minicom. Can you help me configure minicom? Or is this the fault of the system already on the board that do not respond?