DM520 Manuals?!

  • I just got a DM520 today. I connected it according to the Quickstart quide and switched it on. And...NOTHING!
    The LEDS are flashing on the LAN so there is power.
    I checked the HDMI was setup correctly by unplugging it and putting it into my laptop.
    So it is plugged it and switched on!
    So the box looks dead. I then want to download the manual according to the Quickstart guide it will be found at http://dreambox.de/en/downloads.
    There are no full manuals or troubleshooting guides! So what is with the complete lack of documentation?!
    Help!

  • It seems that Dream doesn't really like to write manuals :frowning_face: Also for previous boxes it took them some time to update the download center. But even so: I don't think a manual has the troubleshoot information you are looking for.


    To narrow down you problem a bootlog (aka serial log) should be helpful. How to do that is explained in various boards or on a German youtube video. The official guide is in a dreambox wiki.
    See:
    https://www.youtube.com/watch?v=NuGyOoQUlBQ
    http://dream.reichholf.net/wiki/Howto:Bootlog


    The process in short:
    1. Install VSCP driver on your PC
    2. Connect the Mini USB Service Port to your PC (you need a Mini USB cable not Micro!)
    3. Start PuTTY or another serial terminal software and set it to "Serial" and the correct COM Port (check Windows Device Manager for a new serial port) and activate logging, click "Open"
    4. Start the Dreambox


    Then please upload the log file created by the terminal software and we will see whats wrong :smiling_face:


    Regarding the terminal software: I'd highly reccomend to use PuTTY. It's the easiest :smiling_face: You can find it there: http://www.chiark.greenend.org…atham/putty/download.html

    so long
    m0rphU

  • Hi m0rphU!
    Thank you for the help :smiling_face:
    Herewith attached the bootlog.


    ---------


    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.10.28 09:24:30 =~=~=~=~=~=~=~=~=~=~=~=


    Dreambox DM5 20



    M0CZS
    L2=1
    LLMB=1
    BrCfg=E30FB7C6
    #@


    BCM973625A0 CFE v15.3, Endian Mode: Little
    Build Date: Thu May 19 18:50:53 2016 (Jann@Cynric)
    Copyright (C) Broadcom Corporation.


    Enabling NAND flash at CS2: A5U4GA31ATS(DEVICE ID=0xC8DC9095), ECC Level=4, Spare Area Size=16
    MACRONIX SPI flash detected: Size = 16MB, Sector Size 4096, Page Size 256


    CPU speed: 751MHz
    DDR Frequency: 1061 MHz
    DDR Mode: DDR3
    Total memory(MEMC 0): 512MB
    MEMC 0 DDR Width: 16
    Boot Device: SPI
    Total flash: 16MB
    RTS VERSION: rts_hevc10_1067
    ETH0_PHY: INT
    ETH0_MDIO_MODE: 1
    ETH0_SPEED: 100
    ETH0_PHYADDR: 1


    Initializing USB.


    CFE initialized.




    ***** DREAMBOX SSBL *****


    Not interrupted yet, trying autoboot or rescue loader, hit any key in the next 500ms to cancel
    Proceeding with autoboot.. You can try aborting with Ctrl+C
    DM FABTEST CFE starting up
    Device eth0: hwaddr 00-09-34-FF-00-01, ipaddr 192.168.200.10, mask not set
    gateway not set, nameserver not set
    Loader:elf Filesys:raw Dev:flash0.kernel File: Options:bmem=192M@64M console=ttyS0,1000000 root=/dev/nfs nfsroot=192.168.200.1:/srv/nfs/prodtest_dm520 ip=192.168.200.10
    Loading: 0x80001000/7448768 0x8071b8c0/240128 Entry address is 0x805af9b0
    Closing network eth0
    Ethernet Cable unplugged
    Starting program at 0x805af9b0


    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.4-3.9-dm520 (ghost@Client) (gcc version 4.8.1 (GCC) ) #3 SMP Thu May 26 17:47:31 CEST 2016
    [ 0.000000] Fetching vars from bootloader... found 13 vars.
    [ 0.000000] Options: moca=0 sata=0 pcie=0 usb=1
    [ 0.000000] Using 512 MB + 0 MB RAM (from CFE)
    [ 0.000000] bootconsole [early0] enabled
    [ 0.000000] CPU revision is: 0002a065 (Broadcom BMIPS4380)
    [ 0.000000] FPU revision is: 00130001
    [ 0.000000] Determined physical RAM map:
    [ 0.000000] memory: 10000000 @ 00000000 (usable)
    [ 0.000000] memory: 10000000 @ 20000000 (usable)
    [ 0.000000] bmem: adding 192 MB RESERVED region at 64 MB (0x0c000000@0x04000000)
    [ 0.000000] Initrd not found or empty - disabling initrd
    [ 0.000000] Zone PFN ranges:
    [ 0.000000] Normal 0x00000000 -> 0x00030000
    [ 0.000000] Movable zone start PFN for each node
    [ 0.000000] Early memory PFN ranges
    [ 0.000000] 0: 0x00000000 -> 0x00010000
    [ 0.000000] 0: 0x00020000 -> 0x00030000
    [ 0.000000] PERCPU: Embedded 7 pages/cpu @81606000 s6336 r8192 d14144 u32768
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129536
    [ 0.000000] Kernel command line: bmem=192M@64M console=ttyS0,1000000 root=/dev/nfs nfsroot=192.168.200.1:/srv/nfs/prodtest_dm520 ip=192.168.200.10
    [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    [ 0.000000] Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
    [ 0.000000] Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
    [ 0.000000] Memory: 313536k/524288k available (5874k kernel code, 210752k reserved, 1152k data, 248k init, 0k highmem)
    [ 0.000000] Hierarchical RCU implementation.
    [ 0.000000] Additional per-CPU info printed with stalls.
    [ 0.000000] NR_IRQS:160
    [ 0.000000] Measuring MIPS counter frequency...
    [ 0.000000] Detected MIPS clock frequency: 751 MHz (375.761 MHz counter)
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] Calibrating delay loop... 749.56 BogoMIPS (lpj=374784)
    [ 0.010000] pid_max: default: 32768 minimum: 301
    [ 0.010000] Mount-cache hash table entries: 512
    [ 0.011000] Initializing cgroup subsys cpuacct
    [ 0.012000] Initializing cgroup subsys devices
    [ 0.012000] Initializing cgroup subsys freezer
    [ 0.013000] SMP: Booting CPU1...
    [ 0.017000] Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
    [ 0.017000] Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
    [ 0.018000] CPU revision is: 0002a065 (Broadcom BMIPS4380)
    [ 0.018000] FPU revision is: 00130001
    [ 0.027000] SMP: CPU1 is running
    [ 0.027000] Brought up 2 CPUs
    [ 0.030000] devtmpfs: initialized
    [ 0.034000] NET: Registered protocol family 16
    [ 0.035000] USB0: power enable is active high; overcurrent is active low
    [ 0.040000] bio: create slab <bio-0> at 0
    [ 0.041000] SCSI subsystem initialized
    [ 0.041000] usbcore: registered new interface driver usbfs
    [ 0.042000] usbcore: registered new interface driver hub
    [ 0.042000] usbcore: registered new device driver usb
    [ 0.043000] Advanced Linux Sound Architecture Driver Version 1.0.25.
    [ 0.044000] Bluetooth: Core ver 2.16
    [ 0.044000] NET: Registered protocol family 31
    [ 0.045000] Bluetooth: HCI device and connection manager initialized
    [ 0.045000] Bluetooth: HCI socket layer initialized
    [ 0.046000] Bluetooth: L2CAP socket layer initialized
    [ 0.046000] Bluetooth: SCO socket layer initialized
    [ 0.047000] cfg80211: Calling CRDA to update world regulatory domain
    [ 0.048000] Switching to clocksource wktmr
    [ 0.057000] NET: Registered protocol family 2
    [ 0.075000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    [ 0.076000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.077000] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.078000] TCP: Hash tables configured (established 16384 bind 16384)
    [ 0.079000] TCP: reno registered
    [ 0.080000] UDP hash table entries: 256 (order: 1, 8192 bytes)
    [ 0.080000] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
    [ 0.081000] NET: Registered protocol family 1
    [ 0.082000] RPC: Registered named UNIX socket transport module.
    [ 0.083000] RPC: Registered udp transport module.
    [ 0.083000] RPC: Registered tcp transport module.
    [ 0.084000] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 0.087000] NFS: Registering the id_resolver key type
    [ 0.088000] SGI XFS with security attributes, large block/inode numbers, no debug enabled
    [ 0.090000] msgmni has been set to 612
    [ 0.091000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    [ 0.092000] io scheduler noop registered
    [ 0.093000] io scheduler cfq registered (default)
    [ 0.093000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.095000] serial8250.0: ttyS0 at MMIO 0x10406800 (irq = 62) is a 16550A
    [ 0.095000] console [ttyS0] enabled, bootconsole disabled
    [ 0.095000] console [ttyS0] enabled, bootconsole disabled
    [ 0.100000] loop: module loaded
    [ 0.101000] brcmstb_nand: NAND controller driver is loaded
    [ 0.102000] tun: Universal TUN/TAP device driver, 1.6
    [ 0.102000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
    [ 0.225000] bcmgenet: configuring instance #0 for internal PHY
    [ 0.245000] bcmgenet bcmgenet.0: (unregistered net_device): link down
    [ 0.246000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.247000] ehci-brcm ehci-brcm.0: Broadcom STB EHCI
    [ 0.247000] ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
    [ 0.279000] ehci-brcm ehci-brcm.0: irq 66, io mem 0x10480300
    [ 0.285000] ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
    [ 0.286000] hub 1-0:1.0: USB hub found
    [ 0.286000] hub 1-0:1.0: 2 ports detected
    [ 0.287000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [ 0.288000] ohci-brcm ohci-brcm.0: Broadcom STB OHCI
    [ 0.288000] ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 2
    [ 0.289000] ohci-brcm ohci-brcm.0: irq 67, io mem 0x10480400
    [ 0.355000] hub 2-0:1.0: USB hub found
    [ 0.356000] hub 2-0:1.0: 2 ports detected
    [ 0.356000] Initializing USB Mass Storage driver...
    [ 0.357000] usbcore: registered new interface driver usb-storage
    [ 0.358000] USB Mass Storage support registered.
    [ 0.358000] i2c /dev entries driver
    [ 0.359000] lirc_dev: IR Remote Control driver registered, major 253
    [ 0.359000] usbcore: registered new interface driver btusb
    [ 0.361000] TCP: cubic registered
    [ 0.361000] NET: Registered protocol family 10
    [ 0.363000] NET: Registered protocol family 17
    [ 0.364000] Bluetooth: RFCOMM TTY layer initialized
    [ 0.364000] Bluetooth: RFCOMM socket layer initialized
    [ 0.365000] Bluetooth: RFCOMM ver 1.11
    [ 0.365000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 0.366000] Bluetooth: BNEP filters: protocol multicast
    [ 0.366000] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    [ 0.367000] L2TP core driver, V2.0
    [ 0.368000] Registering the dns_resolver key type
    [ 0.368000] PM: CP0 COUNT/COMPARE frequency does not depend on divisor
    [ 0.370000] EBI CS2: setting up NAND flash (primary)
    [ 0.371000] NAND device: Manufacturer ID: 0xc8, Chip ID: 0xdc (Unknown NAND 512MiB 3,3V 8-bit)
    [ 0.372000] brcmnand brcmnand.0: 512MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, BCH-4
    [ 0.372000]
    [ 0.374000] Bad block table found at page 262080, version 0x01
    [ 0.375000] Bad block table found at page 262016, version 0x01
    [ 0.376000] nand_read_bbt: bad block at 0x000002760000
    [ 0.377000] nand_read_bbt: bad block at 0x0000034a0000
    [ 0.377000] nand_read_bbt: bad block at 0x00000b940000
    [ 0.378000] nand_read_bbt: bad block at 0x00000e220000
    [ 0.379000] nand_read_bbt: bad block at 0x000015fe0000
    [ 0.380000] Creating 3 MTD partitions on "brcmnand.0":
    [ 0.381000] 0x000000000000-0x00001f500000 : "rootfs"
    [ 0.383000] 0x000000000000-0x000020000000 : "entire_device"
    [ 0.385000] 0x00001f500000-0x00001fa00000 : "kernel"
    [ 0.386000] EBI CS0: setting up SPI flash
    [ 0.387000] spi_brcmstb spi_brcmstb.0: 1-lane output, 3-byte address
    [ 0.387000] spi_brcmstb spi_brcmstb.0: master is unqueued, this is deprecated
    [ 0.388000] m25p80 spi0.0: found mx25l12805d, expected w25q128bv
    [ 0.389000] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
    [ 0.603000] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 120.614000] IP-Config: Guessing netmask 255.255.255.0
    [ 120.614000] IP-Config: Complete:
    [ 120.615000] device=eth0, addr=192.168.200.10, mask=255.255.255.0, gw=255.255.255.255
    [ 120.616000] host=192.168.200.10, domain=, nis-domain=(none)
    [ 120.616000] bootserver=255.255.255.255, rootserver=192.168.200.1, rootpath=
    [ 120.617000] ALSA device list:
    [ 120.618000] No soundcards found.

  • Uhm... Better attach the log as a .txt file to your post :winking_face: And the log looks suspiciously short. Is this really everything?


    What I see so far is this:

    Code
    Not interrupted yet, trying autoboot or rescue loader, hit any key in the next 500ms to cancel


    It seems that the Box didn't boot properly... Maybe it has booted in the rescue loader. You can try to access the rescue loader with your webbrowser on http://192.168.200.10

    so long
    m0rphU

  • Hi,



    I tried again (text file attached).
    Someone phoned in the middle of booting and I left the device to its own devices for five minutes.
    I got the following in addition to the usual.



    [ 307.616000] VFS: Unable to mount root fs via NFS, trying floppy.
    [ 307.618000] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
    [ 307.618000] Please append a correct "root=" boot option; here are the available partitions:
    [ 307.619000] 1f00 513024 mtdblock0 (driver?)
    [ 307.620000] 1f01 524288 mtdblock1 (driver?)
    [ 307.621000] 1f02 5120 mtdblock2 (driver?)
    [ 307.621000] 1f03 16384 mtdblock3 (driver?)
    [ 307.622000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
    [ 307.623000] Rebooting in 180 seconds..


    Both 192.168.200.1 and 192.168.200.10 are "unreachable" when put in my browser. My computer is directly branched to the DM520 with an ethernet cable.


    Any other ideas or shall I return the unit to the supplier?


    Ps - I am thinking about flashing a bootloader...

  • DreamUp was used for all older boxes. It does not work on DM520 anymore. And you shouldn't need to update the secondstageloader.
    Also, please use the official source and not some forum: http://dreamboxupdate.com/open….2/unstable/images/dm520/


    Your log shows that the box is some strange state. I.e. I've never seen that line and it seems to be some test programm?

    Code
    DM FABTEST CFE starting up


    What you can try is the regular procedure to flash a new image. As r.benamin said, the box should be connected to your router or another DHCP server for that procedure:
    1. Turn on the Box with the switch on the back
    2. When the Button light up, press it and keep it pressed until the lights start to blink
    3. Check the TV screen if an IP is shown. If not, you might check the Router for the IP
    4. Navigate to the IP with your browser


    A tip for this is to use the same hand for steps 1 and 2, because it won't work if your too fast :winking_face:

    so long
    m0rphU

  • m0rphU thanks for your help and patience. Without you you I'd have no idea! I am replacing a dead DM800HD (RIP) which was why I bought a DM520HD and hence depreciated approach.
    I had a peek through the grill inside the box and can see the ribbon cable from the front panel is not connected to anything. The connector is just floating there in air.
    My problem with the DM520 is that there is no HDMI output and no lights at the front of the box. The only indication of life was the LEDs on the LAN port. The ribbon cable not connected to anything explains that.
    May I open up the box and plug the cable into the board without invalidating the warranty?

  • Thats a DM525.
    My DM520 looks like the attached photo below. I have circled in red where the front panel ribbon cable connector looks like it should go. Its the only 8 pin male on which the plug fits and the ribbon reaches.
    I dropped the DM520 with a friend who repairs TVs in his spare time - if he can get the front panel lit up then I can flash firmware.
    This may take a day or two.

  • Did you already suceeded in flashing an image? That might do the trick as it looks like the entire OS is missing. Another option would be reflashing the so called 'rescue loader'. But that might turn your box into a brick, so you better wait.

  • I followed the Quickstart guide and then came to the forum when I could not find any manuals and started this thread.
    I have tried and failed at connecting via ethernet, the only way, I am informed to flash the box. So I suspect the unit was a brick before I got it out of the box.
    I cannot put the DM into rescue mode. The front panel is dead - no lights. I opened up the box and found the front panel is not connected by the ribbon connector to the main board and was floating in thin air.

    Since, I could not determine which way round the 8 pin female plug goes on because it can fit both ways I have given the DM520 to a friend who repairs TVs in his spare time to figure out.

  • Did you already suceeded in flashing an image? That might do the trick as it looks like the entire OS is missing. Another option would be reflashing the so called 'rescue loader'. But that might turn your box into a brick, so you better wait.


    How can I flash or reflash the rescue loader without an ethernet connection?
    Can it be achieved by using the service mini usb port?