Another AzBox stuck on Booting

C

CableFella

Registered
Messages
1
Hi,

I have just brought my ancient AzBox Premium HD out of retirement. It had old original firmware. So in my wisdom, I used Rescue mode and Jazup 2.6 to update the kernel and put on RTi_Core_1.7.0.

All was well until I tried to change the skin, then I rapidly ended up with Rescue mode and then "BOOTING".

I can see most suggest the JTAG method.

TWO QUESTIONS PLEASE:

1.Is there anything easier?

2. Assuming I do get it working again, is there a kernel/image combination that is stable/reliable ie does not crash if you cough within the Azbox's earshot?

Thank you in advance for your help.
 
A

amyren

Registered
Messages
106
CableFella said:
Hi,

I have just brought my ancient AzBox Premium HD out of retirement. It had old original firmware. So in my wisdom, I used Rescue mode and Jazup 2.6 to update the kernel and put on RTi_Core_1.7.0.

All was well until I tried to change the skin, then I rapidly ended up with Rescue mode and then "BOOTING".

I can see most suggest the JTAG method.

TWO QUESTIONS PLEASE:

1.Is there anything easier?

2. Assuming I do get it working again, is there a kernel/image combination that is stable/reliable ie does not crash if you cough within the Azbox's earshot?

Thank you in advance for your help.
Click to expand...

That sounds strange, that you should need to jtag after changing skin.
Normally the jtag situation should come after flashing wrong image so that the box cant boot at all. (but luckily I've so far never been at that point with my Premium)

Normally you should be able to get an IP on the display with the normal method.You probably did this already, but I repeat this anyway just in case you missed something.
1. turn on the power
2. Press and hold VOL+ on your remote control until the box shows an IP adress on the front panel.
Ofcourse you need to be connected to your LAN network with cable, the box will not be able to connect wirelessly at this point.
 
A

amyren

Registered
Messages
106
another advise. If you get the box going again. jazup is outdated unless you are flashing very old images. I think if you try to flash any image with modern kernel with jazup, you will end up in trouble again.
Use AzUP for the current images. For some situations (old kernel version to new) you must also flash the kernel only first, then back to resque mode and flash the image.
 
A

auxius

Registered
Messages
130
Can someone help me how to prevent this error? is causing this the type of TTL cable i use?


xosPe0 serial#c9d980e5d371a956785968997944df35 subid 0x50
xenv cs2 ok
xosPe0 serial#c9d980e5d371a956785968997944df35 subid 0x50
xenv cs2 ok
xosPe0 serial#c9d980e5d371a956785968997944df35 subid 0x50
xenv cs2 ok
power supply: ok
dram0 ok (9)
dram1 ok (a)
zboot (0) ok
>
**************************************
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use 8KB DRAM as stack.
* Support XLoad format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0/1.
**************************************
Boot from flash (0x48000000) mapped to 0x8c000000.
Found XENV block at 0x8c000000.
CPU clock frequency: 300.37MHz.
System clock frequency: 200.25MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a7888).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x00098887).
Using UART port 0 as console.
Board ID.: "852-E2"
Chip Revision: 0x8634:0x86 .. Matched.
Setting up H/W from XENV block at 0x8c000000.
Setting <SYSCLK avclk_mux> to 0x00000000.
Setting <SYSCLK hostclk_mux> to 0x00000100.
Setting <IRQ rise edge trigger lo> to 0xff28ca00.
Setting <IRQ fall edge trigger lo> to 0x0000c000.
Setting <IRQ rise edge trigger hi> to 0x0000009f.
Setting <IRQ fall edge trigger hi> to 0x00000000.
Setting <IRQ GPIO map> to 0x20090820.
Setting <PB default timing> to 0x10101010.
Setting <PB timing0> to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Setting <PB timing1> to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
PB cs config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
MAC: 00:02:14:19:a4:f3
PCI IRQ routing:
IDSEL 2: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
IDSEL 3: INTA(#15) INTB(#15) INTC(#15) INTD(#15)
Smartcard pin assignments:
OFF pin = 0
5V pin = 1
CMD pin = 2
Setting up Clean Divider 2 to 96000000Hz.
Setting up Clean Divider 4 to 33333333Hz.
Setting up Clean Divider 5 to 25000000Hz.
Setting up Clean Divider 6 to 20000000Hz.
Setting up Clean Divider 7 to 20000000Hz.
GPIO dir/data = 0x76000038/0x76000000
UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
UART1 GPIO mode/dir/data = 0x6e/0x00/0x00
XENV block processing completed.
Found existing memcfg: DRAM0(0x08000000), DRAM1(0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Default boot index: 0
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
Checking zboot file signature .. Not found.
Trying xrpc_xload format .. OK
Checking zboot file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load time total 173/255 msec.
Execute final at 0x91200000 ..



**********************************
* YAMON ROM Monitor
* Revision 02.06-SIGMADESIGNS-01-2.8.0.1
**********************************
Memory: code: 0x11000000-0x11040000, 0x11200000-0x11204000
reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000
Environment variable 'start' exists. After 1 seconds
it will be interpreted as a YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

xrpc failed (9)--- if a xtask is using a cipher or if you reboot
--- xrpc will fail with RM_BUSY
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff
YAMON>
Click to expand...
 
Last edited:
C

candyman2

Donating Member
Messages
71
it look's like you pressed you Ctrl+C keys to late,as soon you start,after few seconds you have to press them 2 Keys. You mind have to try it a few times till you get it right.
 
A

auxius

Registered
Messages
130
candyman2 said:
it look's like you pressed you Ctrl+C keys to late,as soon you start,after few seconds you have to press them 2 Keys. You mind have to try it a few times till you get it right.
Click to expand...

Thanks mate, i will try again.
I use CA-42 not Nokia brand and only has 3 cables inside RX,TX,GRN. it's not Prolific chip, it's Arkmicro and support only windows xp.

maybe it's my cable causing this or it's because i use virtual xp under windows 7.

Im running it on Windows 7 x64 under Windows Virtual PC XP mode.

Firewall is off..do i really need to set static IP? and not DHCP?

just ordered PL2303HX based rs232 ttl to usb and Max232 rs232 for jtag. It will arrive soon.
 
Last edited:
A

auxius

Registered
Messages
130
Problem Solve. My newly arrived Yamon PL2303HX solve the problem. Good thing about this is it works on Win7.

Thank you thank you thank you.
 
You must log in or register to reply here.
Top