need help creating a uImage for the IGSR windrunner

[Peter Bell]

I have been attempting to update this thing for two days now, I know
it's super easy for someone with more linux experience, uboot has lots
of alternative boot options, unfortunately it takes at least a day to
learn about each one....have tried so far with bootb and uploading
from ubuntu via linux, however it never boots from my bin, other
options are tftp boot, nfs boot, any suggestions? in the meantime
I'll just keep trying

[hank]

When booting a uImage/zImage I prefer to use a TFTP upload and then
manually run the uboot boot command. After I have determined that it
is a good image I then flash the kernel to somewhere in flash and
uboot boots automatically.

The basic steps are:
1. Upload the kernel to somewhere in RAM using TFTP i.e. tftp uImage
0x2000000
2. Using bootm boot the kernel i.e. bootm 0x20000000
Uboot should now read the extra info included in a uImage and copy the
kernel to where it is executed/execute inplace.

I have been doing some development for the windrunner - essentially
trying to port a snakeos variant to it and I think you should be
careful loading the vanila snakeos images as where the uboot parition
is different. Overwriting the uboot partition would be dreadful.
You can check out some more info on the windrunner here www.sideramota.com/?p=92
and my fork of snakeos here www.github.com/hankhank/BotBot

I hope this is of some use and I would really excited for some
community contributions to botbot. I am currently working on porting
minidlna but alot of the snakeos scripts in packages/botbot_features
need updating/development. But using that buildroot you can generate
zImage and rootfs for either the windrunner or a qemu simulator.

Good luck

[kneegr...@gmail.com]

Thanks for the reply hank, I actually removed the chip last night in an attempt to flash it via my LPT port. not so successful. I did erase a portion of the memory that uboot said contained firmware and now I get Bad magic number after uboot. I don't care about that, if I need to I will just replace the chip.

At least I have a portion of memory that I KNOW won't wipe out uBoot. My problem is compiling a uImage from snake-os.bin. I can't get it to compile  I can upload the bin via bootb but when I run the command to list images in flash I get a flash of something with a nonsense header and a reboot.

 when attempting to bootm I get "bad magic number" or when I command go 0800000, uboot will output "running application at 0x0800000......" but just seem to hang there, maybe I'm not near patient enough.

 I would love to help develop botbot, I just am a little weak on the software side, I can learn but have been locked in a windows box for 20 years.. I can definitely learn quickly.


 I can program chips all day long and test your builds though. just have to find a good source...



Please help me by maybe building me a uImage to try of snake and botbot, I'll solder a socket on the board or add an ISP and test different builds all day long.



Also, tftp upload isn't working for me I believe it's because the device doesn't have the proper permissions,
I followed a guide for changing permissions in oneric but it doesn't seem to work for me...

--
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]

While looking @ the links you posted I noticed that you are using a different header than I am, I am using the while one right below the one you are using. furthest from the chip is TX middle is GND and closest to the chip is RX.

[hank]

The uImage is just one portion of the system, it only contains the
linux kerne and boot instructions. If you want to boot snakeos you
will also need the rootfs which contains all the userland
applications.
Not only that you need a uImage containing a kernel that has the
correct flash map(sections of flash segmented into different regions
for different pieces the system ie one for the kernel one for rootfs
one for uboot etc..) and also the rootfs and etcfs in the case of
snakeos in the right locations.

I can't remember exactly but I'm pretty sure the snakeos flash map is
alot different to the windrunners flash, the bootloader info is stored
somewhere it will be overwritten by the rootfs or something. This is
bad as I'm pretty sure you can't move the bootloader info without
building uboot to direct it to where the boot params are now stored.

So even if you can build the snakeos uImage you will need to update
its flash mapping which is trivial if you know where to look (in the
arm platform dir under the 8132 chip dir there is a config file). Once
you have done that you can build the filesystems flash them to the
right locations in flash and boot the uImage and snakeos should build.

I was faced with the same problem a couple of months ago, I decided
rather than mess around with snakeos build system I just moved to
buildroots. So if you want to build a zImage(another kernel image
format) you can do so using the botbot build chain by checking out the
project, typing in make botbot_tivicwindrunner_defconfig, make and it
will build the rootfs and kernel for you and put it all under output/
images.

You will need to do this on a linux machine with the basic
buildtools(build-essentials) installed the rest of the dependencies
are handled by the buildscripts. If you only have windows machine I
would suggest setting up a vm to do the building. Once you have done
this I can give you some instructions on how to boot and flash botbot
and you will have the basic linux machine on your tivic windrunner as
I am now in the process of bring across alot of the snakeos http
interface and porting a couple of packages that I want.


Good luck,
Andrew

On second thought I might make a post over the weekend on this topic
for botbot and include some precompiled kernels and rootfs but it
worth your time to get it building yourself as then you can easily
customise the rootfs, i.e. which packages you want installed etc..

[kneegr...@gmail.com]

Thanks a lot, I will check it out for sure, I should have no problem booting into ubuntu,


everything ran smooth only this error:

make[1]: Leaving directory `/home/pedro/Desktop/hankhank-BotBot-7060f6d'
make: *** No rule to make target `board/tivic_windrunner/crosstool-ng.config', needed by `/home/pedro/Desktop/hankhank-BotBot-7060f6d/output/build/build-toolchain/.config'

[kneegr...@gmail.com]

fixed that last error, couldn't figure out this one though,


\make: *** No rule to make target `board/tivic_windrunner/crosstool-ng.config', needed by `/home/pedro/Desktop/hankhank-BotBot-7060f6d/output/build/build-toolchain/.config'\




build-toolchain doesn't exist in that location, opened the make file and config and tried to append where I saw the need...

[kneegr...@gmail.com]

that error was overcome with a copy and paste, everythings flowing smoothly now.


We'll see how she goes

[kneegr...@gmail.com]

Ok, Ive got the rootfs and zImage now......

[hank]

Sorry that was poor form on my behalf. I have checked in some changes
to fix the issue.

If you want to boot botbot. Stop the booting process in uboot and use
the following commands

tftp 2000000 rootfs.jffs2
cp.b 2000000 30140000 e00000
tftp 100000 zImage
go 100000

That will flasht the rootfs and boot the new kernel

[hank]

Hey Pedro I just bricked my tivic. I accidently wrote over the uboot partition. Looks like in some other posts you have had some success with reflashing. Can you post a short summary of the programmer you made, the steps required and if at all possible a copy of uboot from the windrunner?

An entire flash dump would also be nice - something I should have done before starting.

Cheers,

Hank

[kneegr...@gmail.com]

Hell, I never dumped my tivic either before I started screwing with it, but I can dump uboot for you. I messed up the kernel, BTW I'm still getting the timeout with tftpboot, I change my NIC ip to 192.168.0.164 because thats what the tivic is looking for, no dice...

Retry count exceeded; starting again                                           
TFTP from server 192.168.0.164; our IP address is 192.168.0.202                
Filename 'rootfs.jffs2'.                                                       
Load address: 0x2000000                                                        
Loading: T T                                                                   
Abort                                                                          

--

[kneegr...@gmail.com]

I built the programmer from here (google translate) http://rayer.ic.cz/elektro/spipgm.htm



now how about a little insight on dumping uboot

[kneegr...@gmail.com]

guess I can remove the chip again and dump the whole thing via the parallel programmer maybe you can patch what I have with whats left of what you have...@ least mine has a complete uboot

[hank]

Removing the chip would be a massive pain in the ass. Start the board and boot into uboot, turning logging on in your terminal application and type the command 

md.w 0x30000000 0x140000

md = memory display will then dump the first 2 sections to the screen. Then you can just upload that file to the mailing list and I can convert it back to a binary image.

[kneegr...@gmail.com]

Ok, sorry been with family all day, I'll do it in about an hour when I get home.

[kneegr...@gmail.com]

Here's what you need...

[hank]

Thanks Pedro. I'll give this a go during the week when I get my hands on a jtag.

Cheers,

Andrew

[kneegr...@gmail.com]

for sure, Glad I could help!  Think you can help me figure out why tftpboot isn't working for me? do I need to specify the download or upload folder in the minicom settings? I don't care if snakeos ever works on this device, as long as we develop the shit out of botbot!!! bought a snake compatible device yesterday (nks-330)...




Thanks

Pedro

--

[hank]

I don't have much experience with tftpbooting. What I would suggest to get working first is just manual TFTP uploading into RAM.

It sounds to me from your previous posts that the TFTP server cannot find the files you are requesting to resolve this try these steps.

1. Double check your TFTP server settings. 

 a. ipaddr of server matches what the uboot serverip environment variable i.e. printenv serverip setenv serverip NEWVAL

 b. the directory the tftp server is hosting contains the file you wish to transfer to the target

 c. the 2 units are connected

2. Upload the kernel to RAM (botbot kernel)

 a. run tftp 100000 zImage

 b. go 100000

 c. you should see the kernel booting

 d. it will fail

3. Upload the rootfs to RAM

 a. tftp 2000000 rootfs.jffs2

 b. cp.b 2000000 30140000 e000000 (this is writing to flash 3xxxxxxx is flash region)

4. Upload kernel again and it should boot up

5. I need to figure out how to flash kernel(how I broke my tivic) 

4. Upload 

If you still have issues try connecting the board directly to the server without a switch/router.

If you still have ip issues send me the output of the following and the uboot error messages

Server: ip addr

uboot: printenv

Cheers,

Andrew

On Tuesday, April 10, 2012 8:19:10 AM UTC+10, Pedro wrote:

for sure, Glad I could help!  Think you can help me figure out why tftpboot isn't working for me? do I need to specify the download or upload folder in the minicom settings? I don't care if snakeos ever works on this device, as long as we develop the shit out of botbot!!! bought a snake compatible device yesterday (nks-330)...




Thanks

Pedro

[kneegr...@gmail.com]

It is connected directly, that reminds me to try through a switch or router, just like my damn android phone, won't be detected by my pc without a hub in between....you'll need a programmer, I made mine with a sharpie, copper clad board from radio shack and some pool acid in a ziploc baggie. it's ugly, but functional. took all of 30 minutes to make. really, you could get a db25 from radio shack and use small leads to connect it directly. if I had to remove my chip again, I'd use a little pair of side cutters and snip the legs instead of de-soldering. only the two on each corner are used, (glad because I lifted a couple of those pads)

Pedro

[kneegr...@gmail.com]

got tftp boot goint finally after setenv serverip ipaddr saveenv... now I'm dealing with this.....






Star Equuleus # go 100000                                                      
## Starting application at 0x00100000 ...                                      



with a blinking cursor forever.....

[kneegr...@gmail.com]

Welcome to minicom 2.5

OPTIONS: I18n
Compiled on May  2 2011, 10:05:24.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys             
                                                    
                                                    
                                                    
U-Boot 1.1.4 (Jun 30 2009 - 14:51:55)               

U-Boot code: 00000000 -> 0001C544  BSS: -> 00021A9C
IRQ Stack: 00e5ff7c
FIQ Stack: 00e5ef7c
RAM Configuration:
Bank #0: 00000000 64 MB
Flash Manufacturer: MX
Flash: 16 MB
DataFlash: MX 25L128
Page Count: 65536
Page Size: 256
Size: 16777216 bytes                                                           
Logical Address: 0x30000000                                                    
Area 0: 30000000 to 3002FFFF                                                   
Area 1: 30030000 to 3003FFFF                                                   
Area 2: 30040000 to 3023FFFF                                                   
Area 3: 30240000 to 30FFFFFF                                                   
********** teltel **********                                                   
 upstatus = run boot_cmd                                                       
 upfail   = 0                                                                  
****************************                                                   
In:    serial                                                                  
Out:   serial                                                                  
Err:   serial                                                                  
PLL clock at 250MHz                                                            
CPU clock at 250MHz                                                            
AHB clock at 125MHz                                                            
APB clock at 62MHz                                                             
Hit any key to stop autoboot:  0                                               
Star Equuleus # tftp 100000 zImage                                             
Check Link Status ....Up                                                       
TFTP from server 192.168.0.100; our IP address is 192.168.0.1                  
Filename 'zImage'.                                                             
Load address: 0x100000                                                         
Loading: #################################################################     
         #################################################################     
         #################################################################     
         #################################################################     
         #################################################################     
         #################################################################     
         ################                                                      
done                                                                           
Bytes transferred = 2074380 (1fa70c hex)                                       

[hank]

Ok so the kernel image is being transfered to the board nicely now.

Not sure why its not booting can you post the output of printenv from the board and also the .config from the botbot builddir?

[kneegr...@gmail.com]

Heres the printenv, and I wasn't sure about the .config, but think I grabbed the right file: /board/botbot/tivic_windrunner/linux/cns2132_kernel_config



Thanks

[hank]

No I ment the .config file from the top of the buildroot dir. So /pathtobuildroot/.config I want to double check that you've built the right kernel and not the kernel for the simulator.

[kneegr...@gmail.com]

here's the whole buildroot-config folder

[kneegr...@gmail.com]

Andrew?

[hank]

Hi Pedro,

Yeah you are building the kernel/rootfs for the simulator. Type make clean; make botbot_tivicwindrunner_defconfig; make

Here are some of the values that tell me this

BR2_ARM_TYPE="ARM926T"

BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.1.5"l

On Saturday, April 14, 2012 2:10:25 PM UTC+10, Pedro wrote:

Andrew?

[kneegr...@gmail.com]

Ok, so she boots fine, then says logging started. then begins what looks like nonsense...

ec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 31Dec 3Dec 31 17Dec Dec 3Dec 3Dec Dec 31Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec De0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999cc0: v 2006 r 0x7af000-0x7b0000 ov 0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39995e0: v 2007 r 0x7b0000-0x7b1000 ov 0
Dec 31 17:04:23 botbot kern.debug kerneDec 31 17:04:23 botbot kern.debug kernel: [DecDeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 3Dec 3Dec Dec 3Dec0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f00: v 2036 r 0x7cc000-0x7cd000 ov 0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f20: v 2037 r 0x7cd000-0x7ce000 ov 0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode:DeDecDeDec 31 17:04:23 botbot kern.debug kernel: DecDeDeDecDeDeDecDe0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39997a0: v 2019 r 0x7bb000-0x7bc000 ov 0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999780: v 2020 r 0x7bc000-0x7bd000 ov 0
Dec 31 17:04:23 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39997DeDeDecDeDeDecDeDeDecDeDeDec Dec 3Dec 3Dec 31 17Dec 3Dec Dec 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996e0: v 2025 r 0x7c1000-0x7c2000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996c0: v 2026 r 0x7c2000-0x7c3000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel:Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 31Dec Dec 3Dec 31 17Dec0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c340: v 1983 r 0x798000-0x799000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c360: v 1984 r 0x799000-0x79a000 ov 0
Dec 31 17:04:24 botbot kern.debug kernelDec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 31 17Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec Dec 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf80: v 2065 r 0x7e8000-0x7e9000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf60: v 2066 r 0x7e9000-0x7ea000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel:Dec 31 17:04:24 botbot kern.debug kernel:DecDeDeDecDeDeDecDeDeDecDec Dec 3Dec 31 17:04:24 botbot k0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f60: v 2039 r 0x7cf000-0x7d0000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f80: v 2040 r 0x7d0000-0x7d1000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode:DecDeDeDec 31 17:04:24 botbot kern.debug kernel: DeDecDeDeDecDeDeDec0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39998e0: v 1991 r 0x7a0000-0x7a1000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39998c0: v 1938 r 0x76c000-0x76d000 ov 0
Dec 31 17:04:24 botbot kern.debug kernel: [JDec 3Dec 3Dec Dec 3Dec 3Dec Dec 31 17:04:24 botbot kern.debug kernel: [JDeDecDeDeDecDeDeDecDeDe0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999760: v 2018 r 0x7ba000-0x7bb000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39997a0: v 2019 r 0x7bb000-0x7bc000 ov 0
Dec 31 17:04:25 botbot kern.debug kernelDec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999de0: v 2015 r 0x7b7000-0x7b8000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999dc0: v 2016 r 0x7b8000-0x7b9000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel:Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec Dec0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c600: v 1989 r 0x79e000-0x79f000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c620: v 1990 r 0x79f000-0x7a0000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode:DeDecDeDec 31 17:04:25 botbot kern.debug kernel: DeDecDeDeDecDeDeDec0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999700: v 2024 r 0x7c0000-0x7c1000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996e0: v 2025 r 0x7c1000-0x7c2000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: cDeDecDeDec 31 17:04:25 botbot kern.debug kernel: DeDeDecDeDeDecDeD0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39993e0: v 2044 r 0x7d4000-0x7d5000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999400: v 2045 r 0x7d5000-0x7d6000 ov 0
Dec 31 17:04:25 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: cDecDeDeDec 31 17:04:25 botbot kern.debug kernel: [JDeDeDecDeDeDecD0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf40: v 2055 r 0x7de000-0x7df000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cee0: v 2056 r 0x7df000-0x7e0000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel:Dec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999e20: v 2013 r 0x7b5000-0x7b6000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999e00: v 2014 r 0x7b6000-0x7b7000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999de0: vDeDeDecDeDeDeDecDeDeDecDeDec Dec 3Dec 3Dec 3Dec 3Dec Dec0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999760: v 2018 r 0x7ba000-0x7bb000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39997a0: v 2019 r 0x7bb000-0x7bc000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel:Dec 31 17:04:26 botbot kern.debug kernel: DeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 31 17:04:26 botbot k0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999500: v 2029 r 0x7c5000-0x7c6000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999e40: v 2030 r 0x7c6000-0x7c7000 ov 0
Dec 31 17:04:26 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3DeDeDecDec 31 17:04:26 botbot kern.debug kernel:DecDeDeDecDeDeDec0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999840: v 1996 r 0x7a5000-0x7a6000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999820: v 1997 r 0x7a6000-0x7a7000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399980DeDeDecDeDeDeDecDeDeDecDec Dec 3Dec 31 17:04:27 botbot kern.0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999700: v 2024 r 0x7c0000-0x7c1000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996e0: v 2025 r 0x7c1000-0x7c2000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996c0: DeDecDeDeDecDeDeDecDeDeDecDec Dec Dec 31Dec Dec 3Dec 3Dec0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f00: v 2036 r 0x7cc000-0x7cd000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f20: v 2037 r 0x7cd000-0x7ce000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f40: DecDeDeDecDeDeDecDeDeDeDecDec Dec Dec 31Dec Dec 3Dec 3Dec0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f80: v 2040 r 0x7d0000-0x7d1000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fa0: v 2041 r 0x7d1000-0x7d2000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3DeDecDec 31 17:04:27 botbot kern.debug kernel:DecDeDeDecDeDeDecDe0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999ce0: v 2005 r 0x7ae000-0x7af000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999cc0: v 2006 r 0x7af000-0x7b0000 ov 0
Dec 31 17:04:27 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39DeDecDec 31 17:04:27 botbot kern.debug kernel: [DeDeDecDeDeDecDe0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fc0: v 2042 r 0x7d2000-0x7d3000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fe0: v 2043 r 0x7d3000-0x7d4000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JDec Dec 31 17Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 31 17:04:28 botbot ke0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c500: v 2092 r 0x8021ff-0x803000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c4e0: v 2093 r 0x803000-0x804000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39DecDeDec 31 17:04:28 botbot kern.debug kernel: DeDeDecDeDeDecDeD0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999d00: v 2004 r 0x7ad000-0x7ae000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999ce0: v 2005 r 0x7ae000-0x7af000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999cc0DeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999720: v 2023 r 0x7bf000-0x7c0000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999700: v 2024 r 0x7c0000-0x7c1000 ov 0
Dec 31 17:04:28 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39DeDecDec 31 17:04:28 botbot kern.debug kernel:DecDeDeDecDeDeDecD0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999ee0: v 2035 r 0x7cb000-0x7cc000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f00: v 2036 r 0x7cc000-0x7cd000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399DeDec 31 17:04:29 botbot kern.debug kernel: DeDecDeDeDecDeDeDec0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999700: v 2024 r 0x7c0000-0x7c1000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996e0: v 2025 r 0x7c1000-0x7c2000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFDec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 31Dec Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 31Dec Dec 3Dec 3Dec0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999500: v 2029 r 0x7c5000-0x7c6000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999e40: v 2030 r 0x7c6000-0x7c7000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399DecDec 31 17:04:29 botbot kern.debug kernel: DeDecDeDeDecDeDeDe0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fc0: v 2042 r 0x7d2000-0x7d3000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fe0: v 2043 r 0x7d3000-0x7d4000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFDec Dec 31 17Dec 3Dec 3Dec Dec 3Dec 31 17:04:29 botbot kern.debug kernel: [JDeDeDecDeDeDecDeDe0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f60: v 2039 r 0x7cf000-0x7d0000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f80: v 2040 r 0x7d0000-0x7d1000 ov 0
Dec 31 17:04:29 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fDeDec 31 17:04:29 botbot kern.debug kernel: DeDeDecDeDeDecDeD0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39997a0: v 2019 r 0x7bb000-0x7bc000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999780: v 2020 r 0x7bc000-0x7bd000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFDec 3Dec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 31Dec Dec 3Dec 3De0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996e0: v 2025 r 0x7c1000-0x7c2000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39996c0: v 2026 r 0x7c2000-0x7c3000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JDec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec 31 170
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f00: v 2036 r 0x7cc000-0x7cd000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f20: v 2037 r 0x7cd000-0x7ce000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fDeDec 31 17:04:30 botbot kern.debug kernel: DeDeDecDeDeDecDeD0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999e80: v 2032 r 0x7c8000-0x7c9000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999ea0: v 2033 r 0x7c9000-0x7ca000 ov 0
Dec 31 17:04:30 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999ec0: vDeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 31 17:04:30 botbot k0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c480: v 2096 r 0x806000-0x807000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cc20: v 2097 r 0x807000-0x808000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c960: vDeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 31 17:04:31 botbot k0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c560: v 2090 r 0x801000-0x802000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c540: v 2091 r 0x802000-0x8021ff ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c500: vDeDeDecDeDeDecDeDeDecDeDec Dec 3Dec 31 17:04:31 botbot k0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf00: v 2054 r 0x7dd000-0x7de000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf40: v 2055 r 0x7de000-0x7df000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFDec 3Dec Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 3Dec 3Dec 3Dec Dec 3Dec 3De0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cc80: v 1974 r 0x78f000-0x790000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c240: v 1975 r 0x790000-0x791000 ov 0
Dec 31 17:04:31 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399c260DeDecDeDeDeDecDeDeDecDec Dec Dec 31 17:04:31 botbot kern.de0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399ce40: v 2061 r 0x7e4000-0x7e5000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cea0: v 2062 r 0x7e5000-0x7e6000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399ca20:DecDeDeDecDeDeDecDeDeDec Dec 3Dec 3Dec 3Dec Dec 3Dec 3Dec 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999460: v 2048 r 0x7d8000-0x7d9000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999480: v 2049 r 0x7d9000-0x7d9da8 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c39994aDeDec 31 17:04:32 botbot kern.debug kernel: DeDeDecDeDeDecDe0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f60: v 2039 r 0x7cf000-0x7d0000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999f80: v 2040 r 0x7d0000-0x7d1000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999fa0: v 2DeDeDecDeDeDecDeDeDecDec 3Dec Dec 31 17:04:32 botbot k0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cec0: v 2057 r 0x7e0000-0x7e1000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399cf20: v 2058 r 0x7e1000-0x7e2000 ov 0
Dec 31 17:04:32 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c399ce80: v DeDecDeDeDeDecDeDeDecDec Dec 3Dec 31 17:04:32 botbot ke0
Dec 31 17:04:33 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999740: v 2022 r 0x7be000-0x7bf000 ov 0
Dec 31 17:04:33 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999720: v 2023 r 0x7bf000-0x7c0000 ov 0
Dec 31 17:04:33 botbot kern.debug kernel: [JFFS2 DBG] (341) read_dnode: c3999700: v 2DeDecDeDeDecDeDeDecDeDec 3Dec 31 17:04:33 botbot kern.D

remeber I'm fairly new to linux, is there a GUI or web interface yet? how can I begin to port my favorite programs over? (cross compile?)





Thanks

[hank]

Hmmmm thats not good. Post the whole boot sequence but from looking at it the rootfs wasn't flashed properly.

Take a look at the packages/ dir in the buildroot for ideas about how to cross compile. THere is heaps of info about this for buildroot

[kneegr...@gmail.com]

Here ya go, thanks.....

[kneegr...@gmail.com]

Any luck on flashing your bootloader?

[kneegr...@gmail.com]

Any word Andrew? running outta projects over here, simulator boots fine. I wanna play with botbot

[kneegr...@gmail.com]

I've rebuilt this thing from scratch about 7-8 times now and always the same outcome....

[kneegr...@gmail.com]

Do I have to buy you a new windrunner to keep you interested or what? people WANT this device, lets make it useable!!!

[kneegr...@gmail.com]

Well, I finally let the thing work itself out, guess it just takes a long time to boot and the debug option is set for massive output. I can log in as root and issue commands although without a GUI I'm pretty impotent @ this point. Maybe it has a web interface but ifconfig doesn't output an ip I can't find out right now. I'm assuming it needs something top serve it up one, like a switch, router or DHCP server. I'll try in a minute. sorry for wasting your time with useless nonsense, how can I change the debugging to be less verbose?

[hank]

Hi back again, 

Can't be too much help atm got heaps of work on at the moment. Got the jtag now and started fiddling around with uboot/builds/configs etc.. 

There should be more than enough to get you going - try updating your checkout and running make clean; make and the build should be good. The only thing botbot needs now is to be packaged up and someone to figure out where to flash things correctly. If you get really excited I have also got the info there on how to make a tivic to botbot firmware image.

For the moment you will just have to have a crack at it and I'll make another post once I have some more time to get stuck into it.

Regards,

Andrew

[kneegr...@gmail.com]

glad to see you back, been fiddling with buildroot, reading man pages and learning about embedded systems and compiling firmware, theres a LOT to learn, but I feel like the fog is beginning to lift....


P.S.

can you send me a copy of that original fw once you get it back up and running?

[Pedro]

SO, WTF, how come nobody told me I could create a rootfs.jffs2 and zImage by compiling my own snake from source?  just because I ask a stupid question doesn't mean I can't take a few hints and go learn some more. I tell you what, after booting hanks botbot I KNOW how to boot snake via serial and tftp and KNOW how to flash it. I have the rootfs and zImage and all I need is for someone smart to tell me the memory address to cp.b the rootfs to once I tftp it over...

On Tuesday, April 3, 2012 12:02:12 AM UTC-7, Pedro wrote:

I have been attempting to update this thing for two days now, I know
it's super easy for someone with more linux experience, uboot has lots
of alternative boot options,  unfortunately it takes at least a day to
learn about each one....have tried so far with bootb and uploading
from ubuntu via linux, however it never boots from my bin, other
options are tftp boot, nfs  boot, any suggestions? in the meantime
I'll just keep trying

[Pedro]

Hey andrew, you still around? how do I compile a bin from a memory dump??? just point me in the right direction...