• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: May 26, 2011, 01:56:52 PM
/lib/firmware/libertas/sd8686_v9.bin
/lib/firmware/libertas/sd8686_v9_helper.bin
2  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: May 26, 2011, 04:13:26 AM
I have the same issue here. Sometimes it boot and sometimes it doesn't
I cant wrap my head around it but it must have something to do with the uboot version i think.

Regarding the kernel && firmware

iWhat i did is i copied the firmware files from my ubuntu machine to the plug.

On my ubuntu machine it look like:

Code:
/lib/firmware/libertas/cf8385.bin
/lib/firmware/libertas/cf8385_helper.bin
/lib/firmware/libertas/gspi8682.bin
/lib/firmware/libertas/gspi8682_helper.bin
/lib/firmware/libertas/gspi8686_v9.bin
/lib/firmware/libertas/gspi8686_v9_helper.bin
/lib/firmware/libertas/gspi8688.bin
/lib/firmware/libertas/gspi8688_helper.bin
/lib/firmware/libertas/sd8385.bin
/lib/firmware/libertas/sd8385_helper.bin
/lib/firmware/libertas/sd8682.bin
/lib/firmware/libertas/sd8682_helper.bin
/lib/firmware/libertas/sd8686_v8.bin
/lib/firmware/libertas/sd8686_v8_helper.bin
/lib/firmware/libertas/sd8686_v9.bin
/lib/firmware/libertas/sd8686_v9_helper.bin
/lib/firmware/libertas/sd8688.bin
/lib/firmware/libertas/sd8688_helper.bin
/lib/firmware/libertas/usb8388_v5.bin
/lib/firmware/libertas/usb8388_v9.bin
/lib/firmware/libertas/usb8682.bin

i used the V9 type and renamed them to the requested name.

(if Jesus would have know the Internet he would have made the bible OpenSource) 
3  Linux Stuff / General Linux questions / Re: LIRC issues with Guruplug server PLUS on: March 24, 2011, 03:14:14 PM
This is the downside of the really simple receiver circuits and can't be addressed in software except keeping the time where interrupts are disabled to a minimum.

So..... i think this will be the end?

Why the end? You could just stop trying to use those "really simple receiver circuits" that require interrupts enabled and use a "decent" receiver hardware instead...

Do you mean that the CommandIR mini III is not a decent piece of hardware? http://www.commandir.com/
4  Linux Stuff / General Linux questions / LIRC issues with Guruplug server PLUS on: March 24, 2011, 09:51:35 AM
All,

I've been struggling with LIRC and a USB IR tranceiver from CommandIR for a few weeks now and i finally found the issue why it will not work on the Guruplug.

The issue:

LIRC works flawlessly on my desktop PC with Ubuntu 10.04. I can record my remotes witout a glitch.
Doing the same with the same remotes and the same IR device on the guruplug ends in total disaster. Irrecord will simply not decode the ir commands or hangs totally.

I used all debian versions with stock and self compiled lirc from squeeze to sid and unstable, i used plugapps linux to see if it  makes a difference but without any luck.

It seems that lirc de/encodes a incomming/outgoing ir stream synchronously. If it cant get the correct interrupt scheduling it needs it fails to decode the stream and it will not send or receive a command correctly.

i found an interesting page regarding this topic and i was suprised to see that LIRC dev team has marked this as a "known bug"

http://www.lirc.org/html/technical.html

it states:

    The lirc_serial and lirc_parallel drivers measure the time between interrupts on the serial resp. parallel port to get a pulse and space representation of the incoming infra-red signal. If interrupts are disabled by the CPU for a rather long time (>100 Ás, which happens often e.g. during heavy IDE disk activity) some interrupts might get lost and the incoming data stream becomes disturbed. In this case decoding of the infra-red signal will fail. This is the downside of the really simple receiver circuits and can't be addressed in software except keeping the time where interrupts are disabled to a minimum.

    If you are using an IDE system you might want to try calling hdparm -u1 -d1 for all of your drives. This enables DMA for the drive and allows the driver to unmask other interrupts during handling of a disk interrupt. But be aware that this can be dangerous for some (buggy) IDE chipsets. Consult the hdparm man page for further information.

So i investigated and i found that in all these plug computers (Marvell CPU ones) all disk (sd-card) and USB traffic goes through one controller on on the chip.
Running "hdparm" on the plug reports that DMA is not supported for disk devices and this relates perfecly with the known bug from LIRC dev team.

So..... i think this will be the end?

Or has somebody a working LIRC? (or do i need to get back to school)

5  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: March 21, 2011, 11:53:50 AM
sorry for replying so late.

wifi can be enabled by copying the firmware files.

Just download the kernel sources and copy them over to the requested directory and give them the right name.

do dmesg | grep firmware and youĺl find what you looking for.  i have to get back on bluetooth here.
6  Linux Stuff / Linux distributions / Re: Upgraded Kernel will not boot. on: March 16, 2011, 04:05:17 AM
You could try to do the following

http://plugcomputer.org/plugforum/index.php?topic=5142.new;topicseen#new

then install a kernel of your choise  with --rootkernel

rebuild your uInitrd with this method

http://plugcomputer.org/plugforum/index.php?topic=1410.new;topicseen#new

voila your good to go

Please let me know if you find any problems
7  Hardware and U-Boot firmware / U-Boot stuff / Re: Guruplug installer issues on: March 16, 2011, 03:34:58 AM
i see you are running the following command

Code:
root@debian:/home/rich/guruplug-installer# ./runme.sh uboot.bin
[code]

What happens if you run
[code]
root@debian:/home/rich/guruplug-installer# ./runme.sh openocd/
[code]

[/code][/code][/code]
8  Linux Stuff / General Linux questions / compiled LIRD won' t decode IR stream on: March 15, 2011, 12:47:00 AM
Debian squeeze has LIRC 0.8.3 by default  but i need 0.8.7 to get my commandir box working.
I downloaded 0.8.7. and compiled and all seems fine. but when i use irrecord to record remotes it just doesnt want to decode my signals.

I tried the same remotes on an ubuntu 10.04 and this works without any problem.

Are there any decoding libraries that i need tyo include? or specific kernel settings.
9  Linux Stuff / Linux distributions / Re: NEW guruplug / openrd / sheeva installer images WHEEZY on: March 15, 2011, 12:31:20 AM
sorry about that  Tongue

The correct link is

http://people.debian.org/~joeyh/d-i/armel/images/20110314-11:29/kirkwood/netboot/marvell/
10  Linux Stuff / Kernel / Re: sheeva with-linux kernels into normal Debian install? on: March 14, 2011, 11:59:45 AM
This is exactly wat i was looking for. It solved a whole bunch of my problems without having to recompile my kernel.

I would like to link this article in my new and improved HOWTO
11  Linux Stuff / Linux distributions / NEW guruplug / openrd / sheeva installer images WHEEZY on: March 14, 2011, 06:30:50 AM
While i was surfing on the debian pages i came across the following:

http://people.debian.org/~joeyh/d-i/armel/images/daily/kirkwood/netboot/marvell/

The installer images are from March 14th so fresh as hell.

enjoy
12  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: March 05, 2011, 12:09:31 AM
OK great to hear thats itś working for you. I read my prcedure again and somehow i copied in a wrong part.

I've made to mod and iĺl write a wiki about it.

Didi you by any chance upgraded your kernel also? i tried it but afterwards its not booting and hanging in initramfs. If you could please let me know and iĺl included it in the wiki
13  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: March 04, 2011, 12:55:27 AM
with saveenv you make your variables permanent

Code:
GuruPlug>> printenv
arcNumber=2659
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sdb3
bootcmd=run bootcmd_usb; bootm 0x00800000 0x01100000
bootcmd_usb=usb start; ;ext2load usb 1:1 0x0800000 /uImage; ext2load usb 1:1 0x1100000 /uInitrd
bootdelay=3
eth1addr=00:50:43:01:91:31
ethact=egiga0
ethaddr=00:50:43:01:91:30
ipaddr=192.168.10.110
mainlineLinux=yes
serverip=192.168.10.105
stderr=serial
stdin=serial
stdout=serial

Environment size: 440/131068 bytes
GuruPlug>>

the root=/dev/sdb3 needs to be modified for you setup


14  Hardware and U-Boot firmware / U-Boot stuff / Re: bricked guruplug / guruplug-installer on: March 01, 2011, 02:52:36 AM
I see you are the perfect candidate to try the following http://plugcomputer.org/plugforum/index.php?topic=5142.msg18334#msg18334

I had the same error as you multiple time. What i did is unplug the power, unplug the JTAG (usb), reboot the PC.   Why? i dunno, but the issue was fixed.

BTW passing the uboot bin directly to the runme script is nor really the best thing to do since you are missing specific parameters. 

Hint: place the uboot binary file which tyou want to use in the openocd directory and modify the ./board/guruplug.cfg file at the section "flash"

No directly execute the openocd commandline in the runme.sh script.
 
15  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 28, 2011, 08:14:45 AM
so quickly reading your method. You end up booting the plug from the sd card completely?
does it work for you? when I did that method the boot crash with a kernel panic (complaining about not knowing how to mount my partition)

I've tested the method multiple times from scratch and it works like a charm. The OpenOCD part is not really necessary if you have a good working plug and just want to upgrade.
If you plug is totally f*cked then OpenOCD is a life saver. I'll modify the procedure with your comment Tnx for that ;-)
Pages: [1] 2