You can verify the update date only via serial connection whe box boots.the boot is updated 3.0, i updated 6 times
i have no log of the upgrade of the boot
i think the boot is not being updated
there any way to know if the boot has been updated from a BH 1.6.5 for example?
I've seen from your log you have connected a USB pendrive with the cfe package inside. I can verify the version of duo cfe this evening when i come back to' homelog upload boot 3.0
Yes, the procedure is the same.Stesso procedimento anche con immagini diverse dalle Blackhole?
Yes, it's an offical upgrade.hey guys,
I'm just wondering this bootloader is the one that Vu+ DUO released ?
BTW, I'm newbie,,, just recently bought a receiver for the very first time ever
Cheers,
BCM73350010
012
Shmoo Version=1.9
MEMC-00000000 RW=00000010 WW=00000047 G=00000001 R=00000008 W=00000013
MEMC-00000001 RW=0000000E WW=00000051 G=00000001 R=00000009 W=00000004 #$
3
COPY CODE
A567
I did a DUO Boot loader update, after that the box is dead now i have a red light only...
The update went well, the front panel declared, "remove usb and reboot", i removed usb and turn off the power switch.......
This is only what i get now from Putty:
Code:BCM73350010 012 Shmoo Version=1.9 MEMC-00000000 RW=00000010 WW=00000047 G=00000001 R=00000008 W=00000013 MEMC-00000001 RW=0000000E WW=00000051 G=00000001 R=00000009 W=00000004 #$ 3 COPY CODE A567
Any ideas?
Uhm..... I should look inside my Duo to report a correct answer ....
telnet:
cat /proc/mtd
new bootloader response:
root@bm750:~# cat /proc/mtd
dev: size erasesize name
mtd0: 07600000 00020000 "rootfs"
mtd1: 00400000 00020000 "kernel"
mtd2: 00400000 00020000 "boot"
mtd3: 00100000 00020000 "cfe"
mtd4: 00080000 00020000 "mac"
mtd5: 00080000 00020000 "env"
mtd6: 00100000 00020000 "nvm"
root@bm750:~#
old kernel:
mtd1: 00200000 00020000 "kernel"
Hi,
Same output here. I'm on a BH 1.6.6 and I wanted to upgrade to the latest version. But first, I wanted to make sure everything is OK. Then I re-checked CFE upgrade (already done since I've got a BH 1.6.6) and I got:
# cat /proc/mtd
dev: size erasesize name
mtd0: 07600000 00020000 "rootfs"
mtd1: 00400000 00020000 "kernel"
mtd2: 00200000 00020000 "boot"
mtd3: 00100000 00020000 "cfe"
mtd4: 00080000 00020000 "mac"
mtd5: 00080000 00020000 "env"
mtd6: 00100000 00020000 "nvm"
So mtd2 size differs from the "right one" (4M). BUT if you see the first post, strictly speaking, that would be OK, since it says boot: 2M.
BTW, no problems so far with BH 1.6.6.
Is there something wrong?
Thanks a lot.
DUO Boot loader updateIncrease update file size up to 128M BytesChange the flash memory map (kernel size : 4M, /boot : 2M)
Ok. Thanks. But What is the right configuration size? 2M (like mine) or 4M? If it's 4M How can I configure that?
Thanks again.
Jose1024
Ok. Thanks. But What is the right configuration size? 2M (like mine) or 4M? If it's 4M How can I configure that?
Thanks again.
Jose1024
This is the thread for duo and not duo2.make more care when postHello there!
I have Duo2
After update for bootloader I see
root@vuduo2:~# cat /proc/mtd
dev: size erasesize name
mtd0: 3d900000 00020000 "rootfs"
mtd1: 3d900000 00020000 "rootfs(redundant)"
mtd2: 00700000 00020000 "kernel"
mtd3: 00200000 00020000 "mac"
mtd4: 3af90000 0001f000 "rootfs"
=====================
root@vuduo2:~# cat /proc/stb/info/vumodel
duo2
Is it OK for my model?
Thank You!