Hi,

I have a Meraki and attempted to upload the latest firware (untested) to it using the EasyFlash utility.

http://wiki.openwrt.org/OpenWrtDocs/Har … 9f3e8584a3

I did as stated in the wiki post, but I don't know what is meant to happen now. I have repowered the device, but it is not getting an address from the router. The right hand ethernet light is flashing continuously.

Just to be sure I am right about the instructions.

I downloaded the ap51-flash-gui.exe for winxp
I downloaded the openwrt-atheros-2.6-vmlinux.gz and openwrt-atheros-2.6-root.jffs2-64k from the latest compile. I also tried the files from the snapshot (26/07/2007)
I then run the gui app, select the files, press Go, then add power to the meraki.

This is what I get now. Followed swiftly with either arp errors or tftp errors. I have winpcap installed.

<a href="http://photobucket.com" target="_blank"><img src="http://i86.photobucket.com/albums/k109/dwrenne/fail1.png" border="0" alt="Photo Sharing and Video Hosting at Photobucket"></a>

Maybe teh device is working, but it is not responing to ping requests on 192.168.1.1. Is it on a different address

Regards

Diarmuid

I set up the serial link and this is what I get when I run EasyFlash and then let it boot. This time it ran without errors but gain is unresponsive once it boots.

<0><0><0><0>Ethernet eth0: MAC address 00:18:0a:01:19:37
IP: 192.168.84.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.84.9

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Release, version V1.04 - built 12:24:00, Apr 17 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Meraki Mini
RAM: 0x80000000-0x82000000, [0x8003d110-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
<0><0><0><0>Ethernet eth0: MAC address 00:18:0a:01:19:37
IP: 192.168.84.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.84.9

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Release, version V1.04 - built 12:24:00, Apr 17 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Meraki Mini
RAM: 0x80000000-0x82000000, [0x8003d110-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
RedBoot> fis load -d vmlinux.bin.l7
Image loaded from 0x80041000-0x80290086
RedBoot> exec
Now booting linux kernel:
Base address 0x80030000 Entry 0x80041000
Cmdline :

(Last edited by DiarmuidWrenne on 1 Aug 2007, 13:56)

Ctrl-c

I was having trouble sending ctrl-c but have it now. The flow control was set to TRS/CTS when it should be NONE, absent, nada, rien, nothing, etc.

I have tried to use the serial method but The wiki page is confusing. Does it describe 4 different ways of flashing the Meraki? I don't know which bits are essential and which are parts of other methods. So if you look at section 4, where do I start?
4.1 ran fine the first time but ran all the way to boot and I ended with a shell. Then I rebooted got to redboot prompt and continued with 4.2 and now seem to have totally screwed it as all I get now is

Ethernet eth0: MAC address 00:18:0a:01:19:37
IP: 192.168.84.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.84.9

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Release, version V1.04 - built 12:24:00, Apr 17 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Meraki Mini
RAM: 0x80000000-0x82000000, [0x8003d110-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
ÿÿÿ^C
RedBoot> c^C
RedBoot> ^C
RedBoot> c^C
RedBoot> ^C
RedBoot> ^C
RedBoot> ^C
RedBoot>
RedBoot>
RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xA8000000  0xA8000000  0x00030000  0x00000000
rootfs            0xA8030000  0x80041000  0x006A0000  0x80041000
linux             0xA8150000  0x80041000  0x00340000  0x80041000
vmlinux.bin.l7    0xA86D0000  0x80041000  0x00100000  0x80041000
FIS directory     0xA87D0000  0xA87D0000  0x0000F000  0x00000000
RedBoot config    0xA87DF000  0xA87DF000  0x00001000  0x00000000
RedBoot> fis load -d linux
decompression error: incorrect header check
RedBoot>

Do those partition look ok.

Is there a serial guide for idiots out there.

Regards

Diarmuid

So now I felt that I had messed up the partitioions so I deleted them as per 5.1.1 then I ran the following commands

RedBoot> fis init
RedBoot> load -r -b 0x80041000 -m tftp -h 192.168.84.9 openwrt-atheros-2.6-vmlinux.gz
RedBoot> fis create -r 0x80041000 -l 0x180000 -e 0x80041000 linux
RedBoot> load -r -b 0x80041000 -m tftp -h 192.168.84.9 openwrt-atheros-2.6-root.jffs2-64k
RedBoot> fis create -r 0x80041000 -l 0x620000 rootfs

That all ran fine with no errors (taking maybe 20 minutes), then I modified the boot script to add the lines
>> fis load -d linux
>> exec

Now when I boot I get

Ethernet eth0: MAC address 00:18:0a:01:19:37
IP: 192.168.84.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.84.9

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Release, version V1.04 - built 12:24:00, Apr 17 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Meraki Mini
RAM: 0x80000000-0x82000000, [0x8003d110-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
RedBoot> fis load -d linux
Image loaded from 0x80041000-0x80296085
RedBoot> exec
Now booting linux kernel:
Base address 0x80030000 Entry 0x80041000
Cmdline

Then nothing.

Any Ideas?

Thanks

Diarmuid

This is the method I use for flashing the Meraki all the time and is working well.  Sounds like your kernel is not built correctly if it does not boot.   It does take the Meraki about 30 seconds to decompress the kernel and start it, so be patient.   (Hopefully the lzma loader for the Meraki will be done soon.  )

Try one of the kernels from the prebuilt kamikaze: http://downloads.openwrt.org/kamikaze/7 … vmlinux.gz

Hi lschweiss,

Those are the images I am using for my install (26/07/2007 15:38). I am using WinAgents TFTP server (30 day trial) on WinXP.

This is the current state of my partitions. Do yours match this? Or would you expect them to.

[BBCode]

RedBoot> ^C
RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xA8000000  0xA8000000  0x00030000  0x00000000
linux             0xA8030000  0x80041000  0x00180000  0x80041000
rootfs            0xA81B0000  0x80041000  0x00620000  0x80041000
FIS directory     0xA87D0000  0xA87D0000  0x0000F000  0x00000000
RedBoot config    0xA87DF000  0xA87DF000  0x00001000  0x00000000
RedBoot>

RedBoot> fconfig -l
Run script at boot: true
Boot script:
.. fis load -d linux
.. exec

Boot script timeout (1000ms resolution): 2
Use BOOTP for network configuration: false
Gateway IP address: 0.0.0.0
Local IP address: 192.168.84.1
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.84.9
Console baud rate: 115200
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false

[/BBCode]

Thanks

Diarmuid

Hi

I ran the following and got it to boot, ping, etc. However, I don't know if the wifi was running. How would I test that?

Whats this does show is that the kernal image is working. So why is it not booting. Are there any diagnostics I could run  and post teh results here.

RedBoot>
RedBoot>
RedBoot> load -r -d -b 0x80041000 -m tftp -h 192.168.84.9 openwrt-atheros-2.6-vmlinux.gz
Raw file loaded 0x80041000-0x80290085, assumed entry at 0x80041000
RedBoot> exec
Now booting linux kernel:
Base address 0x80030000 Entry 0x80041000
Cmdline :
Linux version 2.6.21.5 (nbd@ds10) (gcc version 4.1.2) #12 Thu Jul 26 17:38:18 CEST 2007

but that obviously did not save. When I boot again, it stalls at the  same point as below.

Cheers

Diarmuid

(Last edited by DiarmuidWrenne on 1 Aug 2007, 18:57)

If your using a serial connection, the default build makes the kernel switch to 9600 bps, and you need to change your terminal speed once the kernel loads.

Wireless is disabled by default.  Look in /etc/config/wireless once you login. 

See this thread about configuring the baud rate when building:

http://forum.openwrt.org/viewtopic.php?id=11904

(Last edited by lschweiss on 4 Aug 2007, 14:13)