snakeos running on tivic windrunner......

248 views
Skip to first unread message

Pedro

unread,
Apr 27, 2012, 8:57:19 PM4/27/12
to DealExtreme NAS SnakeOS
Ok, so I've been able to tftpboot this damn thing with a 64MB snakeos
1.3.2 and it runs just fine. theres a million ways to update this
thing really, I attempted to use the ns-k330 un-bricking procedure to
permanently flash snake to the chip and also tried through the web
interface with both "from snake and" "from original" uboot gives me
"bad magic number" when trying to boot after flash & reboot. any
ideas on what I can do to fix the "Magic number" problem???

Pedro

unread,
Apr 27, 2012, 8:58:18 PM4/27/12
to dealextr...@googlegroups.com
Screenshot at 2012-04-27 17:47:45.png

Stefan Scheffler

unread,
Apr 28, 2012, 8:25:18 PM4/28/12
to dealextr...@googlegroups.com

Can you post the output of uboots printenv command?

Am Fri, 27 Apr 2012 17:57:19 -0700 (PDT)
schrieb Pedro <kneegr...@gmail.com>:

kneegr...@gmail.com

unread,
Apr 29, 2012, 2:16:16 AM4/29/12
to dealextr...@googlegroups.com
Well, I got pissed and switched the flash chip from my ns-k330 with my windrunner and cheated a LOT. tore up some pads on the windrunner though and have ordered another one. son of a bitch, I'll post the output of printenv as soon as it gets here and I tftp the snake image to it.  I did successfully flash the rootfs.jffs2 and would only need to tftp the zImage and go 1000000, whenever I tried to copy the zImage to address 60000 (the correct location according to "printenv" I get no output and am brought straight back to the prompt.

--
You received this message because you are subscribed to the Google
Groups "Snake OS mail list": http://groups.google.com/group/dealextreme-nas-?hl=en

Snake OS website is here: http://code.google.com/p/snake-os/

kneegr...@gmail.com

unread,
Apr 29, 2012, 2:17:29 AM4/29/12
to dealextr...@googlegroups.com
go 0x60000 didn't work either...

Stefan Scheffler

unread,
Apr 30, 2012, 6:55:20 PM4/30/12
to dealextr...@googlegroups.com

Oh well

Running the kernel directly from 0x60000 doesn't work. The windrunner
uboot is probably expecting a uImage there. Which i think are
automatically copied to an address embeddeded in the image before beeing
run.

To run a zImage you have to copy it into a higher address manually. So
when you get a chance try something like:
setenv bootcmd cp.b 0x30060000 0x1000000 0xf0000\;go 0x1000000

The commands in bootcmd are run at startup. The above will copy the
kernel and run it from the new address.

To test it run "boot" If that worked you can save the settings to flash
with "saveenv".


Am Sat, 28 Apr 2012 23:16:16 -0700
schrieb kneegr...@gmail.com:

kneegr...@gmail.com

unread,
Apr 30, 2012, 7:13:15 PM4/30/12
to dealextr...@googlegroups.com
That's basically the workaround I was looking for, changing the bootcmd, I was trying to boot without changing it (I have no idea why) I can't test it for a couple weeks though as I stupidly tried to remove the flash chip without de-soldering braid and pulled up some traces. (everything was actually going perfect until my 2 year old daughter bumped my elbow) So I am waiting on a new board.



Thanks

thiu

unread,
May 22, 2012, 9:44:26 PM5/22/12
to DealExtreme NAS SnakeOS
Work with a modified snakeos and need to use a serial ttl to upload
the OS image.


Here is memory map:
0x30000000-0x00FFFFFF - is a mapped flash memory (16mb)
0x30000000-0x3003FFFF - bootloader Snakeos image should start from
0x30040000 (length = 0x3b0000 bytes) The kernel should be at
0x30060000 after flashing and it length is 0xf0000 bytes.



I used this uboot commands to flash that image through tftp server:
1) tftpboot 0x100000 snakeos.bin
2) cp.b 0x100000 0x30040000 0x3b0000
3) setenv boot_cmd cp.b 0x30060000 0x100000 0xf0000\; go 0x100000
4) saveenv



then reboot. should work


if it not booting, try to run manually first:
1) cp.b 0x30060000 0x100000 0xf0000
2) go 0x100000





On Apr 30, 7:55 pm, Stefan Scheffler <stefanscheff...@gmx.net> wrote:
> Oh well
>
> Running the kernel directly from 0x60000 doesn't work. The windrunner
> uboot is probably expecting a uImage there. Which i think are
> automatically copied to an address embeddeded in the image before beeing
> run.
>
> To run a zImage you have to copy it into a higher address manually. So
> when you get a chance try something like:
> setenv bootcmd cp.b 0x30060000 0x1000000 0xf0000\;go 0x1000000
>
> The commands in bootcmd are run at startup. The above will copy the
> kernel and run it from the new address.
>
> To test it run "boot" If that worked you can save the settings to flash
> with "saveenv".
>
> Am Sat, 28 Apr 2012 23:16:16 -0700
> schrieb kneegrople...@gmail.com:
>
>
>
>
>
>
>
> > Well, I got pissed and switched the flash chip from my ns-k330 with my
> > windrunner and cheated a LOT. tore up some pads on the windrunner
> > though and have ordered another one. son of a bitch, I'll post the
> > output of printenv as soon as it gets here and I tftp the snake image
> > to it.  I did successfully flash the rootfs.jffs2 and would only need
> > to tftp the zImage and go 1000000, whenever I tried to copy the
> > zImage to address 60000 (the correct location according to "printenv"
> > I get no output and am brought straight back to the prompt.
>
> > On Sat, Apr 28, 2012 at 5:25 PM, Stefan Scheffler
> > <stefanscheff...@gmx.net>wrote:
>
> > > Can you post the output of uboots printenv command?
>
> > > Am Fri, 27 Apr 2012 17:57:19 -0700 (PDT)
> > > schrieb Pedro <kneegrople...@gmail.com>:

kneegr...@gmail.com

unread,
May 23, 2012, 1:26:33 AM5/23/12
to dealextr...@googlegroups.com
Thanks, waiting on my new tivic's as we speak, really just trying to learn about the uboot and compiling kernels etc for embedded devices, I only like to work with the serial interface, so shouldn't be a problem.

Pedro

unread,
Jun 15, 2012, 8:26:59 AM6/15/12
to dealextr...@googlegroups.com
Thiu, could you please upload or email me the modified config you used to build snake for the tivic? I changed the memory to 64Mb, wasn't sure exactly how to change the memory map, I assume I add it to the config file used to build snakeos. maybe I am confused.  I'll tftp the modified 64mb ram FW to the tivic and see if she'll boot using

"cp.b 0x30060000 0x100000 0xf0000"
"go 0x100000"

I don't think I ever tried with the whole bin before, I tftp'd the kernel and FS separately and attempted to boot, I will let you know how I progress as I wait for your reply...
Reply all
Reply to author
Forward
0 new messages