embedded-linux

问题 I am using SAMA5D27-SOM-EK1 embedded board. I build for it Linux image OS using YOCTO project version SUMO. I need to know device's GPIOS ( gpios-leds and gpios keys specialy) and the mapping of the board. When I enter in /sys/firmware/devicetree/base/leds/red for example in the board terminal I can find gpio file but when i open it there are symbols which i can't read. I think that I can find such things in the generated Device Tree but i can't find its path! Please help me out 回答1: Here is

问题 I am working with a Ethernet camera that comes with Busybox. A single board computer is connected to it through RS232. The SBC needs to send a single command to the camera in order to take a jpg snapshot, save it to a CF memory card and name it in a sequential order (0001, 0002 etc..). This is the code I use to take a single snapshot, without sequential naming: wget http://127.0.0.1/snap.php -O /mnt/0/snapfull`date +%d%m%y%H%M%S`.jpg I need the files to be named sequentially. This is the code

问题 I am working on microzed 7010 board, I have manualy compiled kernel, u-boot, fsbl, and .bit (vivado). Board is booting well with all setup (without using petalinux). But i have noticed that kernel is not Uncompressing kernel... with zImage nor uImage. whereas i can see bootlogs with that of petalinux's images. INPUT : 1 . zImage env is zImage=tftpboot 0x3000000 zImage && tftpboot 0x2A00000 system.dtb && bootz 0x3000000 - 0x2A00000 2 . Boot log is => Zynq> run zImage [2017-10-25 15:57:11

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 2 years ago . How reboot procedure works on ARM SOCs running Linux, e.g do boot loaders reinitialize DDR memory? can anybody please explain me rebooting process in detail. 回答1: How reboot procedure works on ARM SOCs running Linux, ... ? The typical ARM processor in use today is integrated with

问题 Consider unpacking an android firmware image made for a Media box using for example the C code in this post or by 'Amlogic customization tool'. When I use the compiled C code with an android 7.1 image, I get these files: _aml_dtb.PARTITION aml_sdc_burn.ini aml_sdc_burn.UBOOT boot.PARTITION bootloader.PARTITION DDR.USB logo.PARTITION manifest.xml mesonl.dtb platform.conf recovery.PARTITION system.PARTITION UBOOT.USB Excluding some minor config files here, I know each of these images are a

问题 I am trying to mount a source directory from nfs server to a destination directory in embedded board having linux. The following command works perfectly as expected in shell prompt in the board. mount -t nfs -o nolock 10.126.62.45:/vol/home/avinoba/Sky /mnt What is the equivalent system call to be used in program for the command above? I tried the below call but the mount failed with "Invalid Argument" if(mount("10.126.62.45:/vol/home/avinoba/Sky","/mnt","nfs",MS_MGC_VAL,"nolock") == -1) {

问题 This question was migrated from Ask Ubuntu because it can be answered on Stack Overflow. Migrated 6 years ago . I have to interface my GSM module with the AM1808 based on ARM9. I have assigned all the GPIO pins to the Da850.c as well as mux.h files. I successfully created a uImage and inserted that image in my flash. I need to handle some of that GPIO from User application. I know that we can handle the GPIO from the Kerel space but i need to handle from the user space. As for example I have

问题 I'm working on setting up an OPKG repository to be used by embedded linux devices. We'd like to secure the server so that only our devices have access to the packages. I couldn't find any information on how to do this other than some references to http proxy username and passwords. Is there a way this can be achieved? I believe opkg repositories use the same system as ipkg. 回答1: You don't really need to modify the sources - compiling OPKG with libcurl will enable http basic auth: ./configure

问题 I wanted to know if any porting is available for back trace implementation for uclibc in arm that I can use in my signal handler to debug segmentation faults. I did come across a useful code here and tried using it inside my signal handler but it fails at the first check and returns from there. I also tried a recurcive backtrace function which simply recursed using (current_frame_p)-3) till it was NULL and printed (current_frame_p)-1). This too seems to give me issues. All I get is the

问题 Because of old Das u-boot from HEAD branch that do not have gcc 5 yet, I am planning on using gcc 4.8 or 4.9 as a default compiler instead of 5.2. GCC required virtual/libc glibc-2.22. glibc-2.22 complied successfully with 5.2. Unfortunately, it failed at do_compile with the error: ld: cannot find -lgcc with gcc 4.8 and 4.9 arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/yocto/hio-jethro/build-hio/tmp/sysroots/hio