WARNING: Do Not Factory Default the TripleX

The Golden Media TripleX is a new receiver with beta firmware. The current 1.2.51 firmware version has a bug in the Factory Default that seems to corrupt the system configuration bin file. This will be a fatal error for a lot of people requiring the receiver to be sent back for a reset.
To avoid this problem, do not do a factory default. If you have problems, reload the firmware or the sat and channel database.

Listed below is TripleX receiver error information from putty that was generated after a factory default was done.

Quote:

---

[MAIN] init finish,errCode=0
[ YWDBASEv_GetData][ 578] error 0x1f40006
[ YWDBL_CommGetVolume][ 288] YWDBLi_CommGetByFldNoWithDefault COMM_VOLUME errType = 0X1F40006 Unknown
[ YWDBASEv_GetData][ 578] error 0x1f40006
[YWDBLi_ScGetByFieldNo][ 101] YWDBL_GetSysCfgField uFieldNo = 15[YWDBL_ScGetResolution][ 496] YWDBLi_ScGetByFieldNo SYSCFG_DEFINITE errType = 0X1F40006 Unknown
########################## uiCompSize[0X00A2251C]================
[*error*][YWFILE_IsDbFileOk:539]===Open file[./AppUserDb/syscfg.bin] failed===
[*error*][YWFILE_ReadFlashToDB:793]===Read [./AppUserDb/syscfg.bin] failed, take [./AppUserDb/syscfgbak.bin] as default===
[*error*][YWFILE_IsDbFileOk:539]===Open file[./AppUserDb/syscfgbak.bin] failed===
[*error*][YWFILE_ReadFlashToDB:799]===Read [./AppUserDb/syscfgbak.bin] failed, take [./AppUserDb/syscfgdef.bin] as default===
[*error*][YWFILE_IsDbFileOk:539]===Open file[./AppUserDb/syscfgdef.bin] failed===


Board: STx7105-PDK [32-bit mode]

---

These are not easy errors to get rid, so be sure to avoid doing a factory default until the firmware is fixed. EB

Well, the above happened to my Alien2 (Triplex almost identical twin), here is procedure that might bring it back to working state:

1) from rs232 (putty, hyperterminal, whatever can connect you to STB):
- type (single line): set bootargs console=ttyAS0,115200 rw ramdisk_size=6144 init=/linuxrc root=/dev/ram0 nwhwconf=device:eth0,hwaddr:00:00:11:11:11:11 ip=192.168.1.3:192.168.1.210:192.168.1.1:255.255.2 55.0:lh:eth0:off stmmaceth=msglvl:0,phyaddr:1,watchdog:5000 bigphysarea=6000
- boot to spark with: nboot.i 0x80000000 0 0x00100000 ;bootm 0x80000000

2) find ip of the stb with scanip22 or whatever other tool and telnet to Spark
- type: insmod /root/spark/modules/i2s.ko
- type cat /proc/mtd
- check whether u-boot is in mtd0 or mtd7 and act accordingly, in my case it was mtd0:
- flashcp -v /dev/mtd0 /storage/c/u-boot.overclock.bin

With a bit of luck you are just fine now and can happily reboot to Spark. u-boot.overclock.bin can be found in latest 1.2.51 E2something image in AppPrg.tar
If Spark was previously erased from NAND, you'll need to reflash it from u-boot first and then try the above procedure. If we would have relocatable u-boot.o things would be simpler (playing with objcopy did not work nice)
If you can't log in with putty via rs232 to u-boot, tough luck, JTAG seems to be the only solution (or RMA). Relocatable bootloader needed.

Not sure whether the problem was fixed in 1.2.54. Hope that this can help someone:)