I've got an IPBox 9000, and am trying to bring the firmware up-to-date.
In the past (18 months ago), I put the NLB image onto it, and am now trying to put a vanilla cuberevo image onto it.
Today, when I put the usb_all_noboot.img image onto USB and try to install via the TV, it just PANICs and reboots.
When I go to the NLB Upgrade firmware page, it tells me that the box is an Abcom9000/CubeRevo.
I've noticed that the image is almost 32Mb - when I 'df -k', I get the following:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock3 16640 16640 0 100% /
none 38908 0 38908 0% /dev
/dev/mtdblock4 10240 5848 4392 57% /var
none 38908 0 38908 0% /mnt
none 38908 48 38860 0% /tmp
tmpfs 38908 0 38908 0% /dev/shm
The NLB GUI Tells me a bit about the box:
machine : DGStation cuberevo board
processor : 0
cpu family : sh4
cpu type : STb710x
Creating 9 MTD partitions on "Onboard_Flash":
0x00000000-0x00040000 : "nor.boot"
0x00040000-0x00060000 : "nor.config_welcome"
0x00060000-0x00260000 : "nor.kernel"
0x00260000-0x01600000 : "nor.root"
0x01600000-0x02000000 : "nor.db"
0x00060000-0x01600000 : "nor.kernel_root"
0x00060000-0x02000000 : "nor.kernel_root_db"
0x00040000-0x02000000 : "nor.all_noboot"
0x00000000-0x02000000 : "nor.all"
Am I right in thinking that the usb_all_noboot.img will overwrite the entire flash?
I don't really understand where Abcom, DGTeam and CubeRevo actually fit together - i.e. where should I be getting my images from? Has anyone got any clues as to what I am doing wrong, as I am keen to put a much more up-to-date image on the box.
Thanks and Regards,
Steve C
trumpton6 / trumpton9
In the past (18 months ago), I put the NLB image onto it, and am now trying to put a vanilla cuberevo image onto it.
Today, when I put the usb_all_noboot.img image onto USB and try to install via the TV, it just PANICs and reboots.
When I go to the NLB Upgrade firmware page, it tells me that the box is an Abcom9000/CubeRevo.
I've noticed that the image is almost 32Mb - when I 'df -k', I get the following:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock3 16640 16640 0 100% /
none 38908 0 38908 0% /dev
/dev/mtdblock4 10240 5848 4392 57% /var
none 38908 0 38908 0% /mnt
none 38908 48 38860 0% /tmp
tmpfs 38908 0 38908 0% /dev/shm
The NLB GUI Tells me a bit about the box:
machine : DGStation cuberevo board
processor : 0
cpu family : sh4
cpu type : STb710x
Creating 9 MTD partitions on "Onboard_Flash":
0x00000000-0x00040000 : "nor.boot"
0x00040000-0x00060000 : "nor.config_welcome"
0x00060000-0x00260000 : "nor.kernel"
0x00260000-0x01600000 : "nor.root"
0x01600000-0x02000000 : "nor.db"
0x00060000-0x01600000 : "nor.kernel_root"
0x00060000-0x02000000 : "nor.kernel_root_db"
0x00040000-0x02000000 : "nor.all_noboot"
0x00000000-0x02000000 : "nor.all"
Am I right in thinking that the usb_all_noboot.img will overwrite the entire flash?
I don't really understand where Abcom, DGTeam and CubeRevo actually fit together - i.e. where should I be getting my images from? Has anyone got any clues as to what I am doing wrong, as I am keen to put a much more up-to-date image on the box.
Thanks and Regards,
Steve C
trumpton6 / trumpton9