So this might be revealing my n00bishness but I can't load Kamikaze on my wrt600n. I would like to look at how the 2.4 kernel maps flash so I can help you ZeroPain, but what did you do to build a .bin file?
Edit: I can build Kamikaze for a Broadcom 4785 with the bcm5397 roboswitch... But when I tried to tftp up openwrt-wrt350n_v1-squashfs.bin the CFE rejected it. I think what I'm missing is the signature... here is the relevant section from kamikaze/target/linux/brcm-2.4/image/Makefile:
define Image/Build/jffs2-64k
$(call Image/Build/CyberTAN,$(1),wrt54g3g,W54F,2.20.1,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt54g3g-em,W3GN,2.20.1,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt54g,W54G,4.71.1,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt54gs_v4,W54s,1.09.1,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt150n,N150,1.51.3,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt300n_v1,EWCB,1.51.2,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/CyberTAN,$(1),wrt350n_v1,EWCG,1.04.1,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/Motorola,$(1),wa840g,2,$(patsubst jffs2-%,jffs2,$(1)))
$(call Image/Build/Motorola,$(1),we800g,3,$(patsubst jffs2-%,jffs2,$(1)))
endef
I think if I'm reading your posts correctly, ZeroPain, you have it working. How?
Edit: I think the wrt600n uses the bcm5397 switch, supported by the bcm57xx driver
(Last edited by dch24 on 6 Aug 2008, 22:35)