I flashed the version 1.1.0 to my miniMaker, and I was able to connect to it with David's miniMover and print, miniMover report version number 1.1.0. And I was able to flash back to my 1.2.1, and connect to it with David's miniMover and print, miniMover report version number 1.2.1. Also I noticed when I erase the firmware, the serialflash which stores the filament tag information is also cleared. So every time I reload the firmware, I can reuse my old tag. (or whenever I need to reuse my old tag, all I need to do is short the erase jumper and reload the firmware.)
I flashed the jr 2.2.0 firmware to miniMaker, miniMaker boots fine and I was able to connect to it with miniMover, miniMover report Da Vinci Jr. 1.0 and firmware version 2.2.0, however it report x-axis motor error and temperature 178C suggest the motor driver pinout and thermistor temperature table of miniMaker is different from Jr.
Also included firmware dump for miniMaker firmware version 1.2.3
]]>I notice when I connect to miniMaker though SWD, the miniMaker make low noise just like when I push and hold the front LED button after reboot. So I connect to miniMaker using David's miniMover, it report firmware version 1.2.1 normally, but when I push and hold the front LED button after reboot, miniMover shows the firmware version become 1.0.1.
So I hypothesis the miniMaker can boot from two different FLASH memory, when you push and hold the front LED button after reboot or connect through SWD, machine boot from 1.0.1 firmware (bootloader maybe). Otherwise it will boot from the real firmware which is 1.2.1 in my case.
So I go to J-flasher and there is option in configuration to select from 4 different device though JTAG SWD access. So I connect to every single one of them and dumped all the flash content, the 2nd device contain firmware version 1.2.1 and all the others dumped firmware 1.0.1. I have not checked if all there firmware 1.0.1 are all the same or they are different firmware for different chips, but my guess is the MiniMaker-dump.bin nilezon posted in Post#1 is not the real/complete firmware for printer (or maybe he intend to post NFC reader flash content).
I will erase all chips and flash back the 1.2.1 firmware and test if the printer will function as normal, and then I can be sure I can go back to stock firmware.
]]>I got the "J-Link EDU Mini" today, can you help with the JTAG pins on the board?
Sorry for the delay. I'm attaching the wiring scheme for SWD.
]]>To read/write/debug the ATSAM4E8E you need to connect using JTAG or SWD. SWD is easier since it's fewer cables to solder.
You can probably use any SWD reader that support Atmel ATSAM4E8E, including Atmel-ICE and all J-Link debuggers. You can probably also use a BusPirate or other generic SWD device.
So for I have only used Atmel-ICE and J-Link EDU (not Mini), but I'm quite sure the J-Link EDU Mini works as well.
I got the "J-Link EDU Mini" today, can you help with the JTAG pins on the board?
]]>Should work, yes.
I tried the online version and it timed out :-(https://retdec.com/decompilation/
Use the dump (first post).
Select Raw machine code, ARM and Little endian.
Entry address: 0x00000000
VM address: 0x20000000
Thank you very much for the information, the readme file mentioned it use lots of memory, so I'm downloading the standalone version. I'm sure it will end up with codes that I don't necessary understood, but it is fun to see if I can compile it back.
]]>Hi, nilezon, Can this be used to decompile the firmware?
Should work, yes.
I tried the online version and it timed out :-(
https://retdec.com/decompilation/
Use the dump (first post).
Select Raw machine code, ARM and Little endian.
Entry address: 0x00000000
VM address: 0x20000000
ok ordered "J-Link EDU Mini" and spare ATSAM4E8E ICs (I can solder them easily)
Stupid idea. Why we can't erase the flash and program the decrypted firmware, since we have it?
We can. I have downgraded fw this way
]]>Stupid idea. Why we can't erase the flash and program the decrypted firmware, since we have it?
]]>As far as I understand, the firmware is stored after update in Atmel ATSAM4E8E and in MX25L3206E SPI ?
Removing the SPI chip or downgrading the firmware on SPI chip make no difference, the firmware in Atmel always starts.I need something to change/delete/reflash firmware inside Atmel.
Is the recommended device "J-Link EDU Mini" sufficient for this?Sorry Im also new on this low level hardware hacking, but I learning fast. ;-)
The ATSAM4E8E is the main chip of the printer and contains it's own firmware.
The eeprom MX25L3206E is an external "storage" used by ATSAM4E8E to cache the decrypted firmware before updating. It is also used to store known NFC tag details. No code is every run on or from MX25L3206E, it's just storage (a bit simplified).
To read/write/debug the ATSAM4E8E you need to connect using JTAG or SWD. SWD is easier since it's fewer cables to solder.
You can probably use any SWD reader that support Atmel ATSAM4E8E, including Atmel-ICE and all J-Link debuggers. You can probably also use a BusPirate or other generic SWD device.
So for I have only used Atmel-ICE and J-Link EDU (not Mini), but I'm quite sure the J-Link EDU Mini works as well.
I need something to change/delete/reflash firmware inside Atmel.
Is the recommended device "J-Link EDU Mini" sufficient for this?
Sorry Im also new on this low level hardware hacking, but I learning fast. ;-)
]]>Im going to buy one of this Atmel-ICE device. Do I need something else?
What about software?
You probably shouldn't.
The Atmel-ICE can only be used with Atmel chips.
I had to buy an additional J-Link Edu to dump the NFC chip (from NXP).
I think you can use a "J-Link EDU Mini" for all chips on these printers, and it's very cheap (less than $20).
Atmel-ICE uses "Atmel Studio". J-Link devices works with a variety of software, I tried "Segger Ozone" and liked it.
]]>