The recorder stops on the control lanes, still does not start. I suspect a firmware glitch.
Does anyone know how to load new firmware on this device? Does it run on startup on some default IP?
I do not have access to the programmer, but I have a USB->TTL cable, but I am not sure about connecting it. I don't see any 4 pins except for one white one next to the VGA jack. There is one more pinout slot but only 3 pins.
DNR recorder 2008NDfr
Marking under the plate AS8-3520D-XHSK V1.01 20130416
You are able to check what software (firmware) you currently have installed.
I can't say it. I got the recorder for diagnostics. However, I have other working ones at my disposal.
gradek83 wrote:
Send full resolution sharp and clear photos of your device and motherboard from both sides.
The spaces in red are the connectors that are used for connections to the display, etc. Designation 1- used by the buttons on the front of the case Designation 2- not used, it could be a UART, but I suppose it's more of another panel to control
I do not see 4 TTL connectors anywhere, not even sockets for soldering, complete zero on both sides
Of course, knowing life under a different name, one could also find this model.
The main chip is not hard to guess is HI3520D
Next to the battery you have SPI FLASH 25Q128, it would seem to rip what is sitting there and save if the system is not damaged.
As for the UART, these 3 pins at the edge of the heatsink can be as UART. How would you connect there through the terminal, you could see if the chipset starts and where it stops.
Of course, these 3 pins can be from the fan power supply to the radiator cooling, so check what voltages you have relative to ground.
Is it to be understood drop by drop the same model?
Yes
gradek83 wrote:
.. Of course, these 3 pins can be from the fan power supply to the radiator cooling, so check what voltages you have relative to ground.
Yes, I also saw that this Oltec HDVR-08HD is similar. For me, BNC is just on the cables.
Unfortunately, I don't have any programmer at my disposal, so I don't know how to see the contents of this flash.
That's what I was thinking about those connectors. You mean the ones I marked in yellow in the picture, right?
Well, that's just how it is. TTL has 4 Pins, and here are 3. So there may be a lack of ground, or rather +3.3V. I will check again with a multimeter, the first measurements a few hours ago of these pins did not indicate any voltage
As for the programmer, I recommend EPZ2010 cheap and useful, and when it comes to the USB-RS232 converter, then EM-USB-01
Have you tried taking out the battery or it won't reset the settings and maybe then it will start. These control stripes may be some kind of test mode launched.
Wasn't there any software on CD with the recorder?
Have you tried taking out the battery or it won't reset the settings and maybe then it will start. These control stripes may be some kind of test mode launched.
Wasn't there any software on CD with the recorder?
Maybe I can explain it in more detail After hours, I configure these and other recorders for one company, and as a favor I was asked to see if the recorder could fix it.
Such situations with this brand, but not only, happened and they were usually sent to the distributor and returned with information that the software could be hacked and therefore does not work.
However, I look at this situation as a programmer and I know that there could be a hack to the software, but there may also be some gap and some memory is clogging up, hence some recorders simply fail in one way or another. Maybe a corrupted flash, maybe a hack or maybe a clogged log and the manufacturer of the recorder made a programming error, etc.
gradek83 wrote:
Have you tried taking out the battery or it won't reset the settings and maybe then it will start. These control stripes may be some kind of test mode launched.
I just took it out all night and no effect. The recorder stands on the lanes :)
These stripes in these recorders will always appear after turning on, and then the soft starts, they are somewhere up to 10 seconds. Nothing happens after them.
Sometimes this happens when someone does not change the default password to the recorder, or someone simply breaks it or in some other way, for example, faulty software is uploaded. Sometimes even the manufacturer itself releases faulty software and problems arise.
Krystian14 wrote:
some memory gets clogged up, hence some recorders just fail in one way or another
For example, in a few cameras I had that it did not load the kernel, it crashed the read error, but it was the SPI FLASH memory that was the fault after a few years, the system simply fell and usually replacing it with a new one and uploading the batch helped.
Krystian14 wrote:
clogged log and the manufacturer of the recorder made a programming error, etc.
Well, exactly nothing can be ruled out for this preview through the terminal of what is displayed there and the bootloader becomes one of the helpful options in the diagnosis.
Krystian14 wrote:
The recorder stands on the lanes
You can see these stripes via HDMI, and if, for example, you connect a camera via BNC, there are also stripes.
And tell me how, for example, you set a static IP address in the PC, say 192.168.0.10 and directly connect the LAN cable with a twisted pair to the recorder, then the network card will establish a connection?. Enter CMD as an administrator and after such a connection, check the arp /a command and the recorder should have the MAC address and look for it after entering arp /a.
Sometimes Wireshark helps me find an IP. The recorders have the fact that they usually do not have a RESET button, which would reset the settings to the factory settings.
P.S now I look and see that apart from HDMI there is also a VGA D-SUB output, so on both outputs you can see these stripes just for accuracy? Of course, as long as the back looks like the one in the attached photo.
Alternatively, check if the program IP-Search-Tool will not find the recorder on the network.
And one more question, do you have a sticker with a barcode on your recorder on the motherboard or housing, e.g. 4108HB-H ...
This is the info I found, but it's general information:
Here, as I see after these stripes, after some time there is an image of the guy and the plate from what I see is similar.
But it's probably hanging at your place and not loading the software.
As a supplement, I found a description of the rest of the sockets, of course, if there is no supplemented electronics, these sockets may simply not be active, but what can be checked with a meter, for example, the voltage on the pins from the fans FAN, it is known that it will confirm whether they are powered or not. Two fans are probably one for cooling the chipset and 2 for cooling the disk or general air circulation.
As for the MCU sockets, it's probably some additional expansion control panels.
You have this USB RS232 TTL cable, then connect to CN11 3 pin and connect and look in Hyper Terminal or via PUTTY for action. The port settings will probably be 115200 8-N-1 but you need to check.
In some registrars they are reset buttons then the wizard mode is activated where basic options are set. So I searched and came across a diagram from the attachment of another recorder with the H3520D system and that's where SYS_RESET is supposed to be, but I don't know exactly if it's about the reboot signal, i.e. the option in the settings, restart or such an external reset.
Pin 63 and 64 only in the picture you can't see because the heatsink covers it, maybe it could be traced and check where the paths lead.
As long as they're connected at all. HERE description you as a programmer may understand something more from it.
From what I can see it is a driver circuit that generates a low-width signal to RSTN.
DRAM: 256 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xEF 0x40 0x18 0x00 0x00 0x00
Spi(cs1): Block:64KB Chip:16MB Name:"W25Q128B"
In: serial
Out: serial
Err: serial
Press CTRL-C to abort autoboot in 0 secondshisilicon #
hisilicon #
The terminal appears. He types anything and nothing, does not respond to any commands. i.e. responds to the Enter key, the # prompt appears again, and that's it
Some KERNEL IMAGE image is uploaded and it loads it to KERNEL, i.e. to the kernel of the system and after unpacking it wants to start from it but it does not start and now as I am not a specialist I can advise you or if you have the opportunity to rip the BATCH from this bone and save it in WU. Further, ripping the batch from the second same device and sending it here or yourself to check if they are different, it may be that, for example, there will be different versions of the firmware and there will be a difference, but anyway, how will you rip from this good working one and program the supposedly bad bone and after it will start it will be ok.
Only now there is an action that you have to unsolder this SPI FLASH memory, insert it into the programmer and then you know. If you do not have a programmer, you can try to solder the batch from good to what does not work and see if it will start. I have the EZP2010 programmer and it gives advice, you only need to remember to check what voltage the memory is for, usually 3.3 and if it is 1.8V, you need an adapter or a converter and the SO8 clip is also useful.
Attention, if you decide on this or that programmer, if you buy it, see where the shipping is from China, but you will have to wait a bit, I used to drive like this.
How do you type Help or ? you don't see something like this:
hisilicon # help
? - alias for 'help'
base - print or set address offset
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fload - fload - load binary file from a filesystem image for system boot
flwrite - SPI flash sub-system
getinfo - print hardware information
go - start application at address 'addr'
help - print command description/usage
lload - lload - load logo file
loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtest - simple RAM read/write test
mw - memory write (fill)
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
squashfsload- fsload - load binary file from a filesystem image
tftp - tftp - download or upload image via network using TFTP protocol
usb - USB sub-system
usbboot - boot from USB device
version - print monitor version
hisilicon #
Enter the command printenv And see if it gives you info like:
U-Boot 2010.06 (May 26 2013 - 06:05:55)
DRAM: 256 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xEF 0x40 0x18 0x00 0x00 0x00
Spi(cs1): Block:64KB Chip:16MB Name:"W25Q128B"
In: serial
Out: serial
Err: serial
Press CTRL-C to abort autoboot in 0 secondshisilicon #
hisilicon #
hisilicon #
hisilicon # help
hisilicon # ?
hisilicon # printenv
Unfortunately, I will not have access to a good registrar. Possibly a second device with the same defect. In this case, buying a programmer will not give me anything.
In this case, buying a programmer will not give me anything.
If you have contact with electronics with laptops, etc., believe me that it comes in handy and often.
Krystian14 wrote:
Is the same happening on your device?
These examples are from the Russian forum I gave not on my example.
Recently, I found the HiTool program that supports chipsets of this type, maybe you will understand it and help you with something, I haven't had a chance to play with it.
Just remember to do everything carefully and thoughtfully so as not to hurt even more. If the program does not start from the HiTool.exe file, you must install Java for me on XP, I can't install newer java, so I ran the eclipsec.exe file and it started.
" The configuration section stores all user settings. If you delete this section, then restart the recorder, it will start with default settings" Example:
I'm closing the topic. The software provided by gradek83 worked properly, but it did not add anything to the case. Generally, there was no meaningful communication with the device through it, you could see a few registers and that's it. Most features not available for this chipset.
No print commands, etc. didn't work as I wrote. Just after pressing ENTER I got the prompt again and nothing else.
I don't have a programmer - maybe these batches will be useful for posterity :)
The recorder was finally sent to the site with the others by the way. After returning, I will not analyze it anymore because I will not determine whether it was reprogrammed or otherwise serviced.
The discussion revolves around troubleshooting a DNR 2008NDfr recorder that fails to start, suspected to be due to a firmware glitch. The user inquires about loading new firmware and accessing the device via UART using a USB-TTL cable. Various responses suggest checking the current firmware, identifying pinouts for UART connections, and using a programmer to read or rewrite the SPI FLASH memory (W25Q128B). The Oltec HDVR-08HD is mentioned as a similar model, and users discuss potential issues with the firmware, including corrupted memory or faulty software. The conversation concludes with the user unable to establish meaningful communication with the device despite attempts to use provided software and commands. Summary generated by the language model.
