If you really try to flash it first times, you should do a backup of the full flash chip.
On one of the pictures on the wiki page i see a spi nor flash... That means it should be relatively easy to restore such backups in any case with a cheap hw programmer.
Probably you could do a backup of all mtd partitions from inside the stock fw and store it on a thumb drive.
Yup, @CHKDSK88's first image was a killer image, because it overwrote a JBOOT-reserved-like partition without the JBOOT didn't boot.
It could be restored with a spi programmer (and of course a full backup).
Yes, very first image was a brick maker. This device have a small recovery linux. Without this router don't start.
I made changes with jboot image builder and after that i make preliminary working image.
Work with DIR-510L stopped after openwrt forum crash. I don't have a device, so I can't work alone.
Yes I have the device, and I want to try to get OpenWRT running. I've used it for several years with stock firmware, but it has become unreliable. I was thinking of factory reset, but then I remembered there was some effort on getting OpenWRT running which is much preferred since stock firmware is poor. However, I'm not able to dedicate time for a couple of weeks.
In the meantime, I need some education on how this process works. I've flashed routers with OpenWRT and DD-WRT before, but the process I've seen described is quite different. I need to understand what's going on better.
Should I get an SPI programmer? What is the recommendation?
what is the process for capturing the backup before starting?
what is JBOOT? mtd partitions?
Understanding combination of serial access with PUTTY as well as file transfer with TFTP?
And download through the builtin httpd: http://192.168.0.1/dir-510l-whole-flash.bin
3. JBOOT is closed D-link bootloader. Mtd layout You can find here: https://openwrt.org/toh/d-link/d-link_dir-510l_a1
4. Serial console is nescessary. In this router TFTP isn't used.
Every vendor have his own system. This router was maked by Amit for D-Link. JBOOT bootloader causes that work with this devices is different. You can upload images by JBOOT recovery web interface.
Just found this thread after digging through my notepad, finding a sketch from the time just before the forum disappeared. I was on the old thread, but none of the later posts were recovered. However back then I had tried to find the circuit around the embedded MSP430 controller that handles the power and charging:
I remember there were some weird effects when switching the device on and booting OpenWRT - you just couldn't switch it back off without detaching the battery.
The slider switch "Router <-> OFF <-> charger" is connected to a MSP430 Microcontroller (Pins 9/10), just as the two LEDs (Pins 18/19) and the bq24195l battery charger (i2c, Pins 14,15).
MSP430 connects to MT7620 via UART (MSP430 Pins 3/4, apparently 4800 8N1), but I couldn't make sense out of the communication protocol yet.
The binary that handles communication to that chip in the stock firmware seemed to be mcuinfo_cdm56cdl, but I don't have the tools and skills required to reverse engineer that properly to find out how to talk to it (so we could at least shutdown the device, maybe even read the battery status): https://onlinedisassembler.com/odaweb/kLPxxGw5
So, is anyone still on this? I have a device to test
@s_2, I have the device but have not had a chance to get back to working on it. Maybe in the next month or so?
I've installed OpenWRT on more traditional routers, but this one seems substantially more complex, so I'm trying to learn enough so I don't brick it trying. I already learned about backing up via the serial console, JBOOT, etc. Now you are saying there is a companion MSP430 microcontroller that is doing some other functions for power and charging? Since I don't use the DIR-510L as a charger, or in self-powered mode, I'd be happy to disable that and remove the battery and only power it over USB. Do you have any schematic, photos, or other notes you can share?
I think the latest version even contained the GPIOs for enabling the USB Hub ports, I don't have specific notes about those though. The only scribble I found on paper was this about MSP430, wanted to make a nice and clean schematic with EAGLE, but then the forum was gone and I never continued
I think I will have some time next month (one week of vacation after christmas). As far as I remember, I had destroyed the MSP430 UART connection on one device while testing, but I might find the issue with the new microscope soon
By the way, there also seems to be somewhat acceptable support for MT7610E by now, which should probably be included when someone intends to build a new image:
I think it should be /dev/ttyS0 according to the strings in the binary that controls the chip in the stock firmware, not sure whether it's the same UART that would also enumerate as ttyS0 in openwrt.
It's difficult to follow the traces within the multi-layer pcb, I have no clue yet as to where exactly they are physically connecting to MT7620.
Upon attaching the battery, MSP apparently sends some version info at 600 Baud, then switches to 4800. But I broke the UART connection on my device back then (probably cut some trace with oscilloscope probes), so even after flashing back to stock it will show battery charge always at 0% (curiously it can still be switched off using the slider).
I will have to find my board within the piles of electronics boxes and have a look at the bootlog again for the mtd layout / position of the wifi calibration data (or am I just confusing this with the ART partition of ar71xx? what exactly do you need from the full flash, just the layout or some binary blob that is the same for all DIR510 ?)