embedded-linux

Problem: I have to configure various LCD displays to be used by Android Platform. Almost in all cases there are no electrical specifications freely available for LCD displays on interest. But through experience and reverse engineering the parameters can be guessed reasonably well. I am trying to use Loadable Kernel Modules to fine tune the display parameters (any other suggestions are welcome too). Please find the relevant information below. HW: Atmel SAMA5D31-EK (ARM 5 processor) SW: Andriod Linux (Target), Ubuntu (Host System), Sourcery CodeBench (Cross Compiler) Code Snippets from board-dt

I am using YOCTO project SUMO release to Build Linux kernel for my embedded board. I want to customize the features of my board. They told me to edit the device tree file. My question is what is the path of this DT file ? And when i modify it, I must rebuild all the kernel using Bitbake ? Thanks. Create the following tree in your layer meta-custom: recipes-kernel/ └── linux ├── linux-at91 │ ├── 0001-my-custom-dt.patch └── linux-at91_%.bbappend In linux-at91_%.bbappend , put FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI += "file://0001-my-custom-dt.patch" To generate 0001-my-custom-dt

The following is an excerpt from DTS file. linux/arch/powerpc/boot/dts/[board_name].dts memory { device_type = "memory"; reg = <0x00000000 0x40000000>; // 1GB at 0 }; The embedded device has 1 GB of memory. 0x40000000=1073741824 in decimal. The only way i get 1 GB is when i calculate 1073741824 as bytes. Which means 1073741824 bytes = 1GB. So does this mean 0x00000000 points to a byte of data in RAM? In other words, every byte in RAM has an address. Why is that so? What do we read a block of 8 bits? Why not a word? TL;DR : RAM accesses are NOT in byte sized chunks even though each byte is

This question already has an answer here: Cross compile mono for arm 2 answers I tried to compile mono for arm in scratchbox on Ubuntu 11.10. But when I make install I got an error message. [sbox-ARMEL:~] ./configure --enable-minimal=profiler,debug,logging,soft_debug --with-tls=--with-tls=__thread --with-monotouch=no --without-mcs-docs --disable-mono-debugger CFLAGS=-DARM_FPU_NONE --disable-mcs-build [sbox-ARMEL:~] make [sbox-ARMEL:~] make install I get this error: make[2]: Entering directory `/home/johannes/mono-2.10.2/mono/mini' CC genmdesc-genmdesc.o In file included from mini.h:39, from

I am currently working on a board booting in 64 bit mode using aarch64 and I have a u-boot in 32 bit mode, I would use arm-linux-gnueabihf. I looked around but there's no other way than using a secondary toolchain via: open-embedded tutorial to use a secondary toolchain Nevertheless, impossible to make it work. Intel made a layer (meta-tc-icc) but it's old and I didn't manage to make it work neither. Any idea how to configure it ? So there's a few ways around this. The general answer for your problem is that you need to have two machine.conf files for this particular setup, build 32bit U-Boot

I follow some document to boot embedded Linux on ARM board (ex: Freescale Vybrid tower) via sdcard. in the document there are steps to build uImage and write u-boot into sdcard as below: sudo dd if=u-boot.imx of=/dev/sdX bs=512 seek=2 mkimage -A arm64 -O linux -T kernel -C none -a 0x81000000 -e 0x81000000 -n “Linux” -d Image uImage What I would like to know is from which datasheet/UM/RM or any document they get the number: bs=512 seek=2, -a 0x81000000 (Load address), -e 0x81000000 (Entry point) Please also explain what Load address/entry point address mean? sawdust What I would like to know is

We have an embedded application, now it requires its state to be saved and reloaded. Just like in PC games, where you save it before you have to go out and breath some fresh air.The product is quiet evolutionary in nature, no proper design so identifying data to be saved is not an option. The software is in C so all data has fixed addresses (.data segment), its also deterministic,a and no dynamic memory allocations. So theoretically I take a back up of this data segment in a file and on relaunch of application update it back from the file. This approach will probably save a lot more data than