• Visit https://www.embeddedcomputers.net/ for Hardware; Software and all other things related to FlashcatUSB

AZbox Premium HD

BIGIFA

BIGIFA

New Member
Hi all i have the blackcat v1.7 board and i am looking to recover a dead azbox premium hd can anyone assist me please
.
Let me know what info you need

many thanks
bigifa
 
Pictures!!!

Of flash chip, cpu, any thing that looks like a jtag or serial connector, etc.
 
OK so it looks like standard ejtag, but you have to bridge that point in order to activate it
 
U getting anything of serial bud ? , looks like it is non DMA so using blackcat could take a long time to flash it , might be worth just doing bootloader if you get a connection and then using serial for the rest
 
hi buddy long tim no see :) i get output from serial but getting no input

have a look

xosPe0 serial#4251dd175d66b24734028bcb61438a02 subid 0x50
xenv cs2 ok
xosPe0 serial#4251dd175d66b24734028bcb61438a02 subid 0x50
xenv cs2 ok
power supply: ok
dram0 ok (8)
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/0x000a8887).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a7777).
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:15:44:3a
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.

ROMFS found at 0xac080000, Volume name = MIPS_LINUX_XRPC
ac080040 : Name = ., Type = dir, Size = 00000000, Next = 00000040
ac080060 : Name = .., Type = hard link, Size = 00000000, Next = 00000060
ac080090 : Name = vmlinux_xload.zbf, Type = file, Size = 006193ce, Next = 00000000
Checking zboot signature.. it's a zboot file, signature OK.
Decompressing to 0x90020000 ..
Output length: 0x00ed8d90(15568272)
unzip error!!orig_crc=0x22829e3d, crc=0x3ad1d15e
Decompressing zboot file from 0xac080090 to 0x90020000 fail
Error : Internal, code = ffffffff
YAMON>
 
Not too familiar with these boxes ,, been doing some different ones for Digi , so will have to look into these ,,, how bricked is it , does it just give you a welcome screen , and when you say no input , is that you not being able to type after the YAMON command line ?
 
VFD shows booting nothing. on TV cant type anything after yoman and not sure the ctrl+c command is working

(it was digi that fucked this with a moody link to a crap image lol)

Ctrl+C is not working
 
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 210
SPI database loaded: 184 devices supported
Welcome to FlashcatUSB interfacing software, build: 362
Running on: Microsoft Windows 10 Pro (32 bit)
Initializing EJTAG engine
Device connected in JTAG mode: 7.06
Error connecting to target board
 
Hahaha , never trust Digi and his firmwares ...

You need to verify your rs232 is working by shorting tx/rx and seeing if you can type in terminal .. ctrl + C must be working as you got the command prompt ( or did it do that automatically )

found this online , are you using same tut ?
 

Attachments

  • EN - How to recover a booting blocked Azbox - v1.3.pdf
    1.9 MB · Views: 15
on the Jtag header are you getting any voltages , also what chip(s) are on this board , because if they are NOR or NAND then you are shit out of luck with fcusb
 
ok my tx rx isn't working :-( just ordered a new usb ttl adapter but it will be about a month getting here lmao
 
LOL , have a word with digi , he has a brand new one with an ftdi chip in it , doubt he will use it get him to send it to u
 
DIGI not answering just orderd another from a uk seller should have it mid week
 
Must be out doing his dodgy deals again LOL .
You should be able to recover it with that . but would be interesting to see if fcusb would be able to read that box flash
 
OK getting further it seems i have inadvertently fried a voltage regulator so god knows what els has died :-( although i can still mess with the consul the ide and sata is dead so the DOM is not being detected :-(
 
You must log in or register to reply here.
Back
Top