I tried to flash my Buffalo WHR-HP-AG108 to Kamikaze Atheros 7.09 but ran out of flash memory. Here's my newly initialized memory:

Can someone suggest the memory addresses I should use to load the 3 Kamikaze files? If I'm successful I'll post a how-to.

Thanks in advance,

Rob

this is how I do it

ip_addr -l 192.168.1.1 -h 192.168.1.2 (router is 1, your PC is 2)
fis init -f
load -r -v -b %{FREEMEMLO} openwrt-atheros-2.6-vmlinux.gz
fis create -r 0x80041000 -e 0x80041000 vmlinux.bin.gz
load -r -v -b %{FREEMEMLO} openwrt-atheros-2.6-root.squashfs

here is where you do 'fis free' to see how much space you've got left. I actually get two separate free sections but one is small and the other is big. after deducting the the first hex number from the second hex number (of the big section) I get 280000 (free space) so for me it's...

fis create -l 0x280000 rootfs

after this do

fconfig

and when it asks you for your init script you put following lines

load -d vmlinux.bin.gz
exec

and that's it, do a 'reset' and watch it boot. it took me a few days to get to this but eventually, after going through every conceivable bit of info in the forum and on wifi pages I arrived at this solution. good luck and post back your results!

(Last edited by posix on 6 Nov 2007, 01:41)

Thanks posix,

I have a problem. I seem to have currupted the redboot directory during my earlier flashing attempts. Redboot is working fine, but when I run 'fis free' a blank line is returned. Is there a way to re load redboot and start clean?

I might be able to load Kamikaze with your free memory but I'd prefer to fix my directory problem.

Thanks again for the help.

Rob

posix,

I was able to fix my directory problem by using 'fis init -i'. I flashed using your instructions and everything seems to go ok, I even calculated the same 'fis free' of 0x280000 as you, but when I reboot I get a fast flashing red light on the router and no ping response.

Also, there is some free memory after flashing which shouldn't be there:

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBE000000  0xBE000000  0x00050000  0x00000000
RedBoot config    0xBE3DF000  0xBE3DF000  0x00001000  0x00000000
FIS directory     0xBE3D0000  0xBE3D0000  0x0000F000  0x00000000
vmlinux.gz        0xBE050000  0x80041000  0x00100000  0x80041000
rootfs            0xBE150000  0x80000400  0x00280000  0x80000400
RedBoot>

RedBoot> fis free
  0xBE270000 .. 0xBE3D0000
  0xBE3E0000 .. 0xBE3F0000
RedBoot>

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

Boot script timeout (1000ms resolution): 9
Use BOOTP for network configuration: false
Gateway IP address: 192.168.1.1
Local IP address: 192.168.1.2
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.1.30
Console baud rate: 9600
DNS server IP address: 192.168.1.1
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
RedBoot>

Any clue as to what my problem is?

Thanks in advance,

Rob

(Last edited by robrob on 6 Nov 2007, 17:48)

I forgot to say that I didn't download anything from the web site but instead built my own kamikaze 7.09. it is very simple, look into kamikaze documentation for svn addresses to download from, then you just do make menuconfig and create your kernel, squashfs and jffs2 images. You will also have to make sure your madwifi is using ap30 profile instead of ap51.

I really don't know why your red led is flashing. Try and do fis init -f (-f for format) and re-load everything from the beginning. Also try with root.jffs2-64k as well. You ARE using .gz kernel, right?

After you do fis init -f do fis free to see what's available. Do fis free after each step. I still have this 100000 block available after I'm done but it's not contiguous with the 280000 block. Maybe there is a way to fix that but right now my priorities are elsewhere - I will get back to this issue once I've sorted everything else out

I did use the fis init -f command before I loaded the files, and I am using the .gz kernel.

When do you load the root.jffs2-64k file? It's not in your instructions. I've only been loading the squashfs file system.

I have the 10000 block free as you do, but I also have the   0xBE270000 .. 0xBE3D0000 block after everything has been flashed.

I have been using the standard files from openwrt/atheros, that's probably the main problem. I'll have to figure out how to download the svn files and make the kernel. I'm using Fedora 7, will that work?

Thanks again for the help,

Rob

I am also using fedora. In your software administration thingamabob find gcc, make, svn and I think that was it. Download and install those packages and you should be all set.

Then using svn checkout kamikaze7.09 and you're all set! I can send you my images by email if you want but you'll really want to build the whole thing yourself, makes understanding things later on a bit easier :-)

Give us a should if you get stuck.

p.s. forget about free blocks for the moment, first get the thing up and running.

I finally figured out what was wrong. The boot script was wrong, it should be "fis load -d vmlinux.bin.gz" You left out the "fis". Kamikaze is up and running on the WHR. I'll post more info later.

Thanks again for the help and the Kami images,

Rob

Kamikaze 7.09 is running great on my Buffalo WHR-HP-AG108 thanks to posix's help and firmware images.

You can download posix's Kamikaze 7.09 WHR-HP-AG108 firmware images here: http://robrobinette.com/temp/posix.vmlinux.gz http://robrobinette.com/temp/posix.squashfs

Follow his instructions above with this one change:

fconfig

and when it asks you for your init script you put following lines

fis load -d vmlinux.bin.gz <-- Here's the change--added 'fis'
exec

(Last edited by robrob on 12 Nov 2007, 15:22)

hi guys,
I can't get the memory address correct.
can you give me some hints?

I get fis free and try the free address that it gives
me but it fails to load the thing and it also says
that it is a memory address. so I'm not sure

thanks

my fis free gives me

fis free
  0xBE150000 .. 0xBE3D0000
  0xBE3E0000 .. 0xBE3F0000

now I do

  0xBE3D0000 - 0xBE150000 (in my calculator, hex mode on) which gives me 280000 in hex or 2621440 in decimal or around 2.5MB
  0xBE3F0000 - 0xBE3E0000 gives me 100000 in hex, 65536 in decimal, 64k basically, too little to worry about

So I use this "280000" in hex as my -l parameter when creating root filesystem in
   "fis create -l 0x280000 rootfs"

Comprende?

(Last edited by posix on 26 Nov 2007, 02:37)

I did exactly as ws state and I also got 280000 in hex as free side.
but it doesn't boot and I can't ping 192.168.1.1 (the default ip address)

anything wrong?

I tried both compilee from this page and the one from /mirrors/openwrt.org and the same result.

thanks

after you load and create your root and linux images, did you forget to do fconfig?

fconfig

and when it asks you for your init script you put following lines

fis load -d vmlinux.bin.gz
exec

use the images rob provided for you

I did key in in fconfig exactly as it was mentioned.
I flashed back to DD-WRT and it was working fine, I formated and flashed to OPENWRT and again the same thing
the red light (diag) is flashing after reboot.

guys,
no matter what I try is totally doesn't work.
in DD-wrt it work 100% each time,
although dd-wrt method is a bit different :
http://www.dd-wrt.com/wiki/index.php/WHR-HP-AG108

can anyone help me on this? I've been flashing for the whole week !!!

Please help me out here.
Thanks

I don't know whether it helps other people or no, but I solved the problem by typing fconfig -d instead of fconfig
and then it boot successfully. although I can't setup wireless yet since it hasn't detected any wifi.

thanks

(Last edited by hellbound on 6 Dec 2007, 11:57)