I just updated the devicepage from snapshot to release download urls.
@tmomas thanks. May I ask you to correct the typo there in order to make the backslash appear before the semicolons ? You may need to double it (that is inputing \\) so that it would appear otherwise I guess it won't show up if you tap it only once.
The missing backslash issue is in this line :
setenv bootcmd nand read ${loadaddr} 0x0c0000 0x540000; setenv bootargs; bootm
Maybe you could also write somewhere that V02 works too.
Thank you for your reply. I've tried again, only to see the device failing at exactly the same point when uploading with tftp. I've tried different tftp clients, network configs, nothing seems to make a difference.
@dipswitch 
you're not going to like my answer, but let's play it like Sherlock Holmes. As you know, in his fictional life, he used to say :
"Once you eliminate the impossible , whatever remains, no matter how improbable, must be the truth."
So what remains ? PuTTY !
In the past, I've had trouble with PuTTY (old version) and serial connections. No kidding. I then switched to TeraTerm and indeed, I did not install OpenWrt on my ON100 with PuTTY, but with TeraTerm.
I use the free (in the "free of fees" meaning) version : TeraTerm and not TeraTerm Pro, so I'm not advertising here anything commercial.
Just check this point, or at least, download the most recent version of PuTTY, before giving it another try.
PS : when (if) you'll use TeraTerm, since it's quite ugly (frighteningly ugly), apply some tweakings :
- in the configuration menu (the name may vary depending on your own locale, but it's the 3rd menu from the left, after file and edit , change the Terminal menu item to give it a decent size (in my case 80 x 24).
- in the configuration menu, go to Font, and set it accordingly (in my case Terminal font, Normal style, and size 14).
@dipswitch
I've just now noticed the tftp server's gauge bar, stuck in the middle, so it, apparently, shouldn't have anything to do with the terminal : the router is downloading directly from the tftp server...
But, what if the terminal was sending some kind of interrupt request on its own, after a certain idle time, so that it could halt the download ?
So I guess, you should, in any case, try with another terminal. Get rid of PuTTY and go for TeraTerm, at least for this install (PuTTY is indeed very cool for SSH connections through network).
I did as you suggested, executed the tftp procedure with terraterm. The result is exactly the same. Uploading freezes at exactly 61%. I really have no idea whats causing this....
I just noticed uboot allocates 8mb for its own use. Could this be the problem? Am i right to conclude that the firmware file loads into this 8mb memory area? Since the binary is approx 9mb in size, i'm wondering if there is an environment variable to increase uboot memory allocation size... Albeit just for flashing procedure.
@dipswitch
I'm not an U Boot expert at all, but we can however check your assumption.
emit the "printenv" command in the U Boot session. It will display all the parameters U Boot has.
Post this listing.
I'll do the same, and we'll check the differences one by one.
I will do that. In the meantime, i even succeeded in doing a direct cable connection between my laptop and the on100 (using uboot with static ip settings), transferring that way with tftp, thus eliminating my entire network. Results are the same.
This is my current environment:
Plasma>> printenv
bootcmd=fsload 0x400000 boot.img;autoscr 0x400000
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
mtdparts=mtdparts=nand_mtd:2m(uBoot)ro,2m(dualboot),6m(kernel1),8m(rootfs1),6m(kernel2),8m(rootfs2),470m(datafs),-(misc)
mtdids=nand0=nand_mtd
partition=nand0,1
mtddevnum=1
mtddevname=dualboot
console=console=ttyS0,115200 max_loop=64
bootargs_end=ip=::::DB88FXX81:eth0:none rootfstype=jffs2
nandEcc=1bit
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
autoload=no
image_multi=yes
ethact=egiga0
ethaddr=64:00:F1:21:23:E8
eth1addr=64:00:F1:21:23:E9
serialNo=DNI162404D2
hwVer=ON100-K9_V02
loadaddr=192.168.0.76
gatewayip=192.168.0.1
netmask=255.255.255.0
serverip=192.168.0.76
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=yes
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
pcieTune1=no
Environment size: 1448/131068 bytes
Here is mine.
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
mtdparts=mtdparts=nand_mtd:2m(uBoot)ro,2m(dualboot),6m(kernel1),8m(rootfs1),6m(kernel2),8m(rootfs2),470m(datafs),-(misc)
mtdids=nand0=nand_mtd
console=console=ttyS0,115200 max_loop=64
bootargs_end=ip=::::DB88FXX81:eth0:none rootfstype=jffs2
nandEcc=1bit
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethaddr=64:00:F1:21:2D:2A
eth1addr=64:00:F1:21:2D:2B
serialNo=DNI162902P4
hwVer=ON100-K9_V02
partition=nand0,1
mtddevnum=1
mtddevname=dualboot
ethact=egiga0
filesize=9c0000
fileaddr=2000000
gatewayip=192.168.1.254
netmask=255.255.255.0
hostname=Host-001
ipaddr=192.168.1.47
serverip=192.168.1.66
bootcmd=nand read 0x02000000 0x0c0000 0x540000 ; setenv bootargs ; bootm
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=yes
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
pcieTune1=no
Environment size: 1542/131068 bytes
I've got it !!!!!!!!!!!!!
your loadaddr is wrong :
loadaddr=192.168.0.76
Mine is :
loadaddr=0x02000000
so you should enter:
setenv loadaddr 0x02000000
saveenv
1 Like
I guess it will be ok after you'll correct the loadaddr.
Go on following the wiki instructions, but pay attention to the aforementioned issue : you need to escape the semicolons with backslashes, in this command :
setenv bootcmd nand read ${loadaddr} 0x0c0000 0x540000; setenv bootargs ; bootm
so you'll enter instead :
setenv bootcmd nand read ${loadaddr} 0x0c0000 0x540000\; setenv bootargs \; bootm
Enjoy !!!
Hurray, it works! Thanks! The onplus finally runs openwrt. What i encountered after flashing:
The dhcp server didnt work, probably duo to old nvram data. What i did is i gave my computer a temporary static ip address, ssh-d into the on100, did a "firstboot" and then "reboot", et voila, the on100 rebooted with factory defaults and the dhcp server went online. 
2 Likes
@dipswitch If your problem is solved, please consider marking this topic as [Solved]. (Click the pencil behind the topic...)
You can also mark the reply that solved your problem:
1 Like
Maybe someone can cleanup the wiki? There are a lot of obsolete entrys there, with references to old lede firmware files. We now know that on100 v2 works, and very important, the corrections in the setenv bootcmd line that @bistrot made.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.