embedded-linux

i tried Grabserial to measure the startup code of my embedded Linux device. It works somehow but after a while (that means a longer startup code - talking about > 26 s) it stops printing out the messages, but grabserial still is running - i have to hit the [CTRL-C] to retrieve control. I checked the serial port with putty and it's working so it's a problem with grabserial. But i can't think of what it is. I downloaded and installed with both of the 2 install-variants and it just changed the look-and-feel but stucks at the same point. Does anyone ever had the same problem ? Greets [edit:] i

Environment: Bluez 5.14, Linux 3.1, USB Plugable BLE radio, TI BLE keyfob (CC2541 dev kit) Linux Device <---hci----> USB BLE Radio We enabled key press events on TI keyfob using gatttool and started to listen for events gatttool -b [hardware ID] --char-write-req -a [handle] -n [value] --listen (gatttool -b 90:59:AF:09:E1:5D --char-write-req -a 0x0048 -n 0100 --listen) Pressing buttons on the keyfob and see these events Notification handle = 0x0047 value: 02 Notification handle = 0x0047 value: 00 Notification handle = 0x0047 value: 02 Hence we can receive the key press events from the Keyfob

I have a S3C6410 board. The default Linux in the package is 2.6.28 and working fine. I want to upgrade it with more recent kernel. I grabbed buildroot 2012.11 edition. Then I get the default config file in the DVD and compiled the kernel 3.6.8 with that. Boot loader and root file system are the same old ones. Now when I boot the kernel I got this error: VFS: Cannot open root device "mtdblock2" or unknown-block(0,0): error -19 Please append a correct "root=" boot option; here are the available partitions: 1f00 8192 mtdblock0 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on

I have a custom board with freescale P1010 processor in which P1010's eTSEC2 ( Enhanced 3-speed Ethernet controller) port is directly connected to Marvell 88E6046 ethernet switch Port 9 in SGMII mode. Linux (3.17) DSA driver is able to probe and detect switch ( Port 9 is 'cpu' whereas port 0 and 1 are designated as 'lan1' and 'lan2'). The problem however is, that there is no PHY for switch to attach to ( 'ifconfig up' fails to attach to ethx). U-boot creates a 'generic PHY' eth0 since it finds there is something ( switch ) attached to processor P1010 but when Linux is up and switch is attached

I am trying to build alsa-util-1.1.0 for an arm-linux platform, through trial and error I managed to compile alsa-lib and alsa-util ok using these commands: alsa-lib: CC=arm-linux-gnueabihf-gcc ./configure --host=arm-linux -prefix=/home/username/20160311_alsa_work/alsa/install --disable-python alsa-util: CC=arm-linux-gnueabihf-gcc ./configure --prefix=/home/username/20160311_alsa_work/alsa/install --host=arm-linux --with-alsa-inc-prefix=/home/username/20160311_alsa_work/alsa/install/include --with-alsa-prefix=/home/username/20160311_alsa_work/alsa/install/lib --disable-alsamixer --disable

I'm trying to create a large empty file on a VFAT partition by using the `dd' command in an embedded linux box: dd if=/dev/zero of=/mnt/flash/file bs=1M count=1 seek=1023 The intention was to skip the first 1023 blocks and write only 1 block at the end of the file, which should be very quick on a native EXT3 partition, and it indeed is. However, this operation turned out to be quite slow on a VFAT partition, along with the following message: lowmem_shrink:: nr_to_scan=128, gfp_mask=d0, other_free=6971, min_adj=16 // ... more `lowmem_shrink' messages Another attempt was to fopen() a file on the