embedded-linux

问题 U-boot passes kernel command-line parameters. In my requirement I want to edit these parameters in the kernel source tree and don't want to change U-boot code. I am using 2.6.35 kernel. So please guide me which part of the kernel source I have to check for this. 回答1: Follow this procedure: Enter the kernel config by typing make menuconfig Enter the menu Processor type and features Enable Built-in kernel command line Specify your command line by clicking on Built-in kernel command string

问题 U-boot passes kernel command-line parameters. In my requirement I want to edit these parameters in the kernel source tree and don't want to change U-boot code. I am using 2.6.35 kernel. So please guide me which part of the kernel source I have to check for this. 回答1: Follow this procedure: Enter the kernel config by typing make menuconfig Enter the menu Processor type and features Enable Built-in kernel command line Specify your command line by clicking on Built-in kernel command string

问题 I am trying to incorporate a CPLD programming utility on Github available at https://github.com/kontron/altera-stapl into my Yocto build but am getting undefined references to gpiod functions. I have that it depends on libgpiod in my recipe. Am I specifying the dependency correctly? Here is my recipe: SUMMARY = "CPLD STAPL Programming" DESCRIPTION = "A userspace port of the Altera Jam STAPL Bytecode Player." MAINTAINER = "Michael Walle <michael.walle@kontron.com>" HOMEPAGE = "https://github

问题 How can I run valgrind on an embedded Linux box to find memory leaks in my main software? In the rcS script, I am running like this: ./main_app How can I associate the ./main_app program with valgrind? The main_app process never terminates. I want to constantly log the data to file. Also, I want to access the log file without terminating the main_app process. I can do telnet and can access the log file. But the problem is until and unless the handler is closed, how can I open the file i.e. I

问题 How can I run valgrind on an embedded Linux box to find memory leaks in my main software? In the rcS script, I am running like this: ./main_app How can I associate the ./main_app program with valgrind? The main_app process never terminates. I want to constantly log the data to file. Also, I want to access the log file without terminating the main_app process. I can do telnet and can access the log file. But the problem is until and unless the handler is closed, how can I open the file i.e. I

问题 How can I run valgrind on an embedded Linux box to find memory leaks in my main software? In the rcS script, I am running like this: ./main_app How can I associate the ./main_app program with valgrind? The main_app process never terminates. I want to constantly log the data to file. Also, I want to access the log file without terminating the main_app process. I can do telnet and can access the log file. But the problem is until and unless the handler is closed, how can I open the file i.e. I

问题 I want to add custom command command to u-boot be it a simple hello world command. After searching I found this link Yocto u-boot Custom Commands where it says to look at timer command in cmd/misc.c as starting point. How do I bring this timer command to my u-boot image? I assume I have make changes to the makefiles but not sure which makefile I should edit. I am using qemu to test the u-boot image in Ubuntu 18.04 using the following method Cloned the u-boot source from github. Installed all

问题 I'm using .NET Core on an embedded Linux platform with good success so far. I just ran into a problem with trying to open a tty device in raw (noncanonical mode) though. If I was using regular C or C++ I would call cfmakeraw() after opening the device, but how do I do that from a .NET Core app? The device I need to work with is a CDC ACM function driver for the USB client connector, i.e. it's a virtual COM port. It appears in my system as /dev/ttyGS0 . I can open the device and then read from

问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to

问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to