• I bricked my Mirabox
    2 replies, posted
A while ago I decided to try to build my own router. Since I don't have enough knowledge to design and build it from scratch I had to look for existing alternatives. It took a while but eventually I found [URL="https://www.globalscaletechnologies.com/p-58-mirabox-development-kit.aspx"]Mirabox by Globalscale[/URL]. I chose it because it looked like the most complete solution (two ethernet ports, even built-in wifi...). Then I decided I didn't like the default Debian and would use [URL="http://archlinuxarm.org/platforms/armv7/marvell/mirabox"]Arch linux[/URL], which I could customize as much as I would like. I managed to get it to boot to Arch linux using an external SD card. But then while messing with U-Boot I unknowingly ran the erase command without partition table defined and it erased the whole nand memory including the bootloader. So now I have bricked Mirabox. Fortunately I found [URL="https://1wt.eu/articles/mirabox-vs-guruplug/"]this blog[/URL] in which the author got into the same problem as me and he managed to solve it. He used a tool called kwboot to upload a new uboot image into the mirabox. But here is my problem: Whenever I try to use the tool to upload a new uboot image to the mirabox, it looks like the configuration message is sent successfully, but when it reaches the upload part, it crashes with message "[xmodem]: Bad message" and the bootloader is not uploaded. I tried this on Arch linux (3.14 and newer) but always with the same result. I tried a kwboot binary I downloaded from the internet and one I managed to compile myself, but without difference. I hope someone can help me or point me in the right direction to solve this problem. Thanks in advance.
Are you doing what he says and powering the device up with the tool already running, maybe the device doesn't actually see the magic sequence? I also assume you have the patched bootloader as he mentions is required?
Yes, the tool starts with "Waiting for device to start..." then switches to "Sending magic numbers" (or something in that sense) and then starts uploading "Uploading bootloader...". After that, progress bar appears and starts to fill up and then it crashes. They use a custom modified uboot image. I've downloaded it from [URL="https://code.google.com/p/mirabox/downloads/list"]here[/URL].
Sorry, you need to Log In to post a reply to this thread.