TonidoPlug2

[devr]

grrrr USPS messed up the delivery of my USB serial cable.... I am so impatient to try this out... I am soy red envious of you jklaiho. Can't wait to no longer have the blinking red led

[kmihelich]

You should be able to do everything if you can get into the stock NAND system. Or if you're already running Arch there are just a few things to set.

[devr]

Yeah I had thought I could.... but things tend to go badly for me when I dun have a safety net (i.e no serial console access). I may just end up trying it tonight though

[kmihelich]

Basically, if you have Arch already running..

1. Upgrade your system, make sure you're running 3.1.10-9.
2. pacman -S uboot-env
3. wget http://archlinuxarm.org/os/tp2/fw_env.config -O /etc/fw_env.config
4. fw_setenv mainlineLinux yes (though this is probably already done if you're booting our kernel)
5. fw_setenv arcNumber 4101
6. reboot!
7.

That's really all there is to it. Just be sure about the kernel.. 4101 doesn't exist prior to that version.

[devr]

Just an update, I was able to successfully update my TonidoPlug per kmihelich instructions. Didn't have too much time to poke around, but doesn't seem like I was able to change the GPIO leds. On boot the red LED was still blinking, and any attempts to make changes by echo'ing values into /sys/class/.... did not have an affect. cat'ing the files I echo'd into showed the update values, just the leds did not change. Could be user error, but wanted to share the success

Now if I could only figure out how to get a USI Topkick, an "Armada 300 clocked at 1.6GHz" sounds pretty sweet

[WarheadsSE]

Hmm, please confirm the uboot environment is reading arcNumber 4101

[devr]

Just got my USB Serial adapter, doing the wire now... so will double check per uboot.. but ssh'ing into the TP2 I see the following. And yes I did step 6 of kmihelich instructions

$this->bbcode_second_pass_code('', '# fw_printenv
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
mainlineLinux=yes
arcNumber=4101

# uptime
17:47:23 up 19:49, 1 user, load average: 0.00, 0.01, 0.05
')

[kmihelich]

I think you missed step 3.

[devr]

o,O could of sworn that was all good... I had issues resolving archlinuxarm.com from my TP2 lastnight, so I copied the text from my laptop to the file on the plug... or so I thought I did.... After fixing my resolv.conf, I re-tested the wget command to test name resolution.. and thus wiping out whatever was in "/etc/fw_env.config". And the fw_printenv command shows a lot more, so guess I fat-fingered something.

I reset arcNumber via uboot with my new, fancy USB serial cable. (that was before I realized I had fat-fingered anything)

LED is working now. On boot I have a solid blue. I can also use the /sys/class/led/... controls to change things.

Wifi seems to have issues. UDEV seems to be detecting it on boot, but get an error message. Will google for the error, guess I need to install a package or firmware. Figured I would share in case others see this error:
$this->bbcode_second_pass_code('', ':: Waiting for UDev uevents to be processed [BUSY]
[ 31.938177] mwifiex_sdio mmc0:0001:1: request_firmware() returned error code 0xfffffffe
[ 31.951767] mwifiex: mwifiex_add_card: firmware init failed
[ 31.958516] mwifiex_sdio: mwifiex_sdio_probe: add card failed
[DONE]
')

[aghitza]

I followed the steps on the install page. Everything was fine except for the following:

$this->bbcode_second_pass_code('', '
root@TonidoPlug2:/tmp# ./install_envtools.sh
--2012-04-24 19:39:18-- http://archlinuxarm.org/os/tp2/fw_printenv
Resolving archlinuxarm.org... 206.217.130.189
Connecting to archlinuxarm.org|206.217.130.189|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 668497 (653K) [text/plain]
Saving to: “fw_printenv”

100%[=====================================================>] 668,497 166K/s in 3.9s

2012-04-24 19:39:23 (166 KB/s) - “fw_printenv” saved [668497/668497]

--2012-04-24 19:39:23-- http://archlinuxarm.org/os/tp2/fw_env.config
Resolving archlinuxarm.org... 206.217.130.189
Connecting to archlinuxarm.org|206.217.130.189|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 329 [text/plain]
Saving to: “/etc/fw_env.config”

100%[=====================================================>] 329 --.-K/s in 0s

2012-04-24 19:39:23 (8.83 MB/s) - “/etc/fw_env.config” saved [329/329]

mount: / is busy
')

I didn't notice the error message at the time (I was half asleep) and continued with fw_setenv, etc. After reboot the led stays red and I can't ssh in (whether I boot with the USB drive with Arch connected, or not). So I seem to have bricked it. Is there a way out?