I recently got a Cisco ASA 5505 Firewall. Since it is not the newest one I decided to install OpenWRT.
As far as I know it uses an AMD Geode Processor so I went and downloaded the x86/geode/generic-kernel.bin but after copying it to a CF Card, plugging that card in and booting via RAMMON I was not able to get it working. After entering the boot command it outputs something like Booting...openwrt-geode.bin.
After that line the cursor jumps to the upper left corner of the screen and a weird C with a zigzag under it is displayed. I also tried the x86 generic kernel but after booting it I get the messga that a i686 CPU is needed but my machine only has a i586 cpu. I also tried the x86 legacy image. After booting the same as on the goede image happens.
Cisco is one of those vendors who are both known to use (very-) custom developed hardware and who want to make it hard to stray from their firmware. Therefore you might not be doing anything wrong, it might simply not be possible (or at least involve serious development to make it possible - which would hardly be worth the effort for geode based hardware).
Disclaimer: just raising this as a possibility, I have no experience with this hardware.
When the ASA boots I get into some kind of command line called "ROMMON". There I can execute commands like ping. But for booting there is the command "boot" it (I think) requires a bin file, or some kind of specific file. To boot the Cisco firmware I can enter "boot disk0:asa802-k8.bin". But after writing an image to the card what file should I point at?
So I should write the image and then point to the file that contains the kernel(in that case what would the path to it be)?
Btw. The default CF card uses FAT and I am not sure if the firewall supports ext4.
I'm sorry if what I am writing sounds stupid but I don't quite understand what you mean.
So I flashed the image now and well, I won't work. First off all there are two partitions now one named kernel with a boot folder. But that doesn't contain a kernel.bin file. Then there is the other partition named rootfs which looks like the filesystem. What should I do?
So, It would be great if I could tell you about the progress. But well there is not that much. I tried booting vmlinuz, but the file was not found so I changed the Partitions to FAT and tried again. Now after boot disk0:/boot/vmlinuz the cursor jumps to the top left corner of the screen again and prints two square like characters. If I try to boot /boot/grub/boot.img the firewall tells me that this image is not bootable and if I try /boot/grub/core.img nothin happens but the firewall seems to recognize it as bootable.
Any other ideas what Icould try, what I could do in another way?
I can enter a "config file spec". But I don't know how the bootloader will give the config file to vmlinuz and in what format the config should be/what I should write in there. As far as I know are the entries in grub.cfg grub specific.
assuming Cisco haven't invented their own serial communication (what whatever you use) console=tty0 console=ttyS0,115200n8 should generate output on a serial port when you trigger the boot.
unless the boot param isn't passed on to the kernel.