As far as I can tell, the toolchain is not included in the code from github. I'm not sure where I can get the old toolchain required, with the uClibc ABI. Do you think I can use a gnueabi version instead, given that I only need to compile U-Boot (which I assume won't need to dynamically link to anything)?by bkallus - Debian
I have been using a kwboot that I built from the newest U-Boot source. I am able to successfully kwboot the MI424WR, so I know the binary is good. It just doesnt work on the Ap-135. Do you have any tips for building those GPL sources? I'm having trouble finding the armeb-linux-gnu-uClibc-0.9.30 toolchain. Can I use the armeb-linux-gnueabi toolchain instead?by bkallus - Debian
For whatever reason, I can't get the kwboot handshake to work, just like hurricos. hurricos's uboot also has no bootm, so i bet that all the 134s and 135s dont. My U-Boot has no mm or md, (hurricos's does) so that suggests that maybe IU did mess around with U-Boot. As for accessing stuff within the OS, the serial shell user is extremely locked down; no permission to do anything. Alby bkallus - Debian
These are the commands available from within apboot: apboot> help ? - alias for 'help' boot - boot the OS image clear - clear the OS image or other information dhcp - invoke DHCP client to obtain IP/boot params factory_reset - reset to factory defaults help - print online help mfginfo - show manufacturing info osiby bkallus - Debian
> What is apboot? apboot is Aruba's U-boot. > Can you connect and run serial console to interact with u-boot? Yes. According to this, I can just setenv serverip and ipaddr and avoid using DHCP like that. I'll try that when I get back home in a few hours. > Look at my repo. It is openwrt snapshot and still updating regularly. Very cool; I'll check this out. I'by bkallus - Debian
The AP-135 doesn't have a USB port, so I can't test with your rootfs. My apboot does have tftpboot, so I should be able to get something working with that. Unfortunately, I see no way to set a static IP, so I'll be wrangling with apboot's dhcp client for a while before tftpboot will work.by bkallus - Debian
Hey, not to drag up dead topics, but I recently picked up an Aruba AP-135 in a thrift store, so if you'd like to see if we can get your Debian to run on it, I'm happy to test for you.by bkallus - Debian
@8086k If you really want to be sure about having the newest kwboot binary, you can compile it from source pretty easily. Just clone the u-boot git repository and run this: make defconfig make tools-all The kwboot binary will be in the tools directory. That said, I'm sure the one in the Ubuntu repositories is fine. I had the exact same problem that you're having when I wasby bkallus - Debian
Also, the U-Boot source code and config is distributed only with the 4x firmwares. I can't UART boot yet, but once I have that set up, I'll see if I can get the U-Boot source code to build, and if their config is portable to the a modern U-Boot.by bkallus - Debian
Wow; I didn't know they had two revisions of the Rev. I! I bet that's why they skipped straight from I to K (the gpl source for the google fiber network box refers to it as mi424wr rev k) This also explains why a month ago, when I built the all firmwares from the actiontec gpl site you linked, I couldn't get any 5x firmware to boot, but the 4x firmwares all worked as expected. Iby bkallus - Debian
I'm trying to UART boot mine, and it's telling me this: ./kwboot -t -B 115200 /dev/ttyACM0 -b uboot-revI-128MbFlash.bin -p uboot-revI-128MbFlash.bin: Invalid image. Did you use the image I uploaded? I've been using a precompiled kwboot from the other thread; do you think it would make a difference if I compile my own? EDIT: I cloned the u-boot repository and ran makby bkallus - Debian
Also ,which file should I try to send over with kwboot, exactly? I don't have any kwb files to test it out with.by bkallus - Debian
Attached is the stock U-Boot.by bkallus - Debian