meteohub.de

Sorry for the length of this message, but I'm having troubles getting MeteoPlug 4.5 to run on my new Sheevaplug. I've tried 3 SHDC cards, and redownloaded all of the install files.

Any help would be great.


;;run meteoplug-installer.sh

[root@asterisk log]# more sheeva.log
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/ope ... /openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9,
Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 20.155991s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 72.485519s

;; copy MeteoPlug filesystem to SDHC card

c:\\tmp>dd if=mhplug-v4.5.img of=\\\\.\\h: bs=1M --progress
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for details
3,963,617,280
3780+0 records in
3780+0 records out

;; SheevaPlug console output

__ __ _ _
| \\/ | __ _ _ ____ _____| | |
| |\\/| |/ _` | '__\\ \\ / / _ \\ | |
| | | | (_| | | \\ V / __/ | |
|_| |_|\\__,_|_| \\_/ \\___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \\ / _ \\ / _ \\| __|
| |_| |___| |_) | (_) | (_) | |_
\\___/ |____/ \\___/ \\___/ \\__|
** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
SDHC found. Card desciption is:
Manufacturer: 0x1b, OEM "SM"
Product name: "00000", revision 1.0
Serial number: 2985019958
Manufacturing date: 12/2008
CRC: 0x00, b0 = 0
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
## Booting image at 00400000 ...
Bad Magic Number
À

your dd command looks strange to me. dd and diskimage won't do on vista. If you have a XP system at your hand, please use diskimage instead (write in "physical disk" mode!).

If no XP there, try with a linux system (any live cd for example). Insert SD card, look with "dmesg" as what device the card gets recognized, unmount device as it might have been mounted by linux the moment it gets inserted (umount /dev/sdx) und use dd command to write the image to the card. Look out to transfer data to base device (/dev/sdx) and not to a certain partition (not /dev/sdx1). Make sure not to select the wrong device, as this might delete your hard disk!

Thanks. That worked.

I used linux dd earlier, but copied to sdb1 rather than sdb. When that failed I used dd (for windows) on Windows 7. I guess that doesn't work.

Working much better now.

The sheevaplug console gives lots of messages of the form
sh: led: command not found

I'm assuming this is not just me.

Thanks for pointing on this. These are error messages caused by a program that tries to signal the IP of SheevaPlug via the blue led. I will fix this with the next update.

One last question. Is Meteohub supposed to use both the DHCP granted address and the 192.168.1.77 address at the same time? When I ran two Meteohubs, although they had different DHCP address they (apparently) were still both responding to .77

Mike

Yes, every Meteohub responds to 192.168.1.77. So if you have more than one in your LAN you cannot make use of this.

To get one connected at this IP would need to unplug the other ones. 192.168.1.77 is an emergency IP, so in normal use you will never need that.