Differences

This shows you the differences between two versions of the page.

--- dump_spi_flash [2021/04/13 11:59] – finish CH341 part kingkevin
+++ dump_spi_flash [2021/04/14 19:14] – [J-Link] kingkevin
@@ Line 78: / Line 78: @@
 {{:spi_flash:adapter_1.8v.jpg?0x150|}}
+==== MiniPRO ====
+The [[http://autoelectric.cn/EN/TL866_main.html|TL866A]] (aka. MiniPRO) is the next step up, and still cheap (< $30).
+{{:spi_flash:tl866a.jpg?0x200|}}
+Advantages:
+  * supports 3.3-6.5V VCC, allowing to properly power 3.3V and 5.0V flash
+  * has over-current protection, in case you inserted the chip wrongly
+  * does signature checking (this is just a software check though)
+  * supports up to 21V VPP and has flexible pin configuration, allowing plenty of other EEPROM chips or MCU to be flashed
+Disadvantages:
+  * does not support 1.8V (you can still use the same adapter as for the CH341A). the newer TL866II+ claims to support 1.8V, but from the [[https://github.com/radiomanV/TL866/raw/master/docs/TL866II.pdf|schematic]] I don't see how they do this properly
+  * also slow (~ 100 kbyte/s)
+For more information about the device (including reversed schematic), see [[https://proghq.org/wiki/index.php/TL866|this wiki]] or [[https://github.com/radiomanV/TL866|this repo]].
+To dump SPI flash, we will use [[https://gitlab.com/DavidGriffith/minipro/|minipro]].
+<code>
+# search for the right part using the top marking on the chip
+minipro --search 25q32bv
+Found TL866A 03.2.86 (0x256)
+W25Q32BV
+W25Q32BV@WSON8
+W25Q32BV@SOIC8
+W25Q32BV@SOIC16
+W25Q32BV(OTP)
+W25Q32BV(OTP)@WSON8
+W25Q32BV(OTP)@SOIC8
+W25Q32BV(OTP)@SOIC16
+# read the device ID to be sure the connection work (it's not get_id as in the help, but read_id)
+minipro --device 'W25Q32BV@SOIC8' --read_id
+Found TL866A 03.2.86 (0x256)
+Chip ID OK: 0xEF4016
+# alternatively, let it find which 25xx SPI 8-pin flash it is
+minipro --auto_detect 8
+Found TL866A 03.2.86 (0x256)
+Autodetecting device (ID:0xEF4016)
+S25FL032K@SOIC8
+W25Q32@MLP8
+W25Q32(OTP)@MLP8
+W25Q32BV
+W25Q32BV@WSON8
+W25Q32BV@SOIC8
+W25Q32BV(OTP)
+W25Q32BV(OTP)@WSON8
+W25Q32BV(OTP)@SOIC8
+W25Q32FV
+W25Q32FV@WSON8
+W25Q32FV@SOIC8
+W25Q32FV(OTP)
+W25Q32FV(OTP)@WSON8
+W25Q32FV(OTP)@SOIC8
+W25Q32V@MLP8
+W25Q32V(OTP)@MLP8
+device(s) found.
+# now read the memory
+minipro --device 'W25Q32BV@SOIC8' --read spi.bin
+Found TL866A 03.2.86 (0x256)
+Chip ID OK: 0xEF4016
+Reading Code...  40.53Sec  OK
+</code>
+==== BX48 ====
+The [[https://www.batronix.com/shop/programmer/BX48/index.html|Batronix BX48 Batego]] is my high end programmer.
+{{:spi_flash:bx48.jpg?0x200|}}
+Yes, it is expensive (> $500), but the hardware is good, and what you pay for is the support.
+And I have to say that it is excellent.
+Is a chip missing?
+Just ask them and they will swiftly add support for it.
+Note: This device is obsolete now, replaced by the [[https://www.batronix.com/shop/programmer/BX48/batego-II.html|BX48 Batego II]].
+The main difference is that the Batego I does not support VPP > 15V (only required by very old NMOS EPROM).
+It still seems to be supported though.
+The software is [[https://www.batronix.com/shop/software/prog-express/index.html#tabs-4|Prog-Express]], and there is even support for Linux (a bit lagging the Windows release).
+There is an auto-detect function, but I am too concerned it accidentally damages the chip.
+Therefor I still select the target chip by hand.
+On my setup it is not able to open the file dialog to allow me setting where I want to load/save the file (using version 3.8.8).
+To circumvent the issue I open the built-it hex-editor.
+There I can save read/write the data content, and save/load it.
+To get the latest chip database (particularly if the Linux release it lagging), here how I update it:
+<code>
+wget https://www.batronix.com/downloads/ChipDBUpdate/ChipDB.zip
+unzip ChipDB.zip
+sudo mv /usr/lib/prog-express/ChipDB.db3 /usr/lib/prog-express/ChipDB.db3.bak
+sudo mv ChipDB.db3 /usr/lib/prog-express/ChipDB.db3
+rm ChipDB.zip
+</code>
+===== in-circuit =====
+In-circuit flash programming is a lot more tricky.
+The issue is that the flash chip needs to be powered, but the MCU using this memory is probably on the same power real.
+Thus the MCU might use the flash chip, interference with your operation.
+SPI is a point to point connection protocol.
+On the SPI lines there should be only one master.
+This master drive the SCK and MOSI lines in push-pull mode.
+If your programmer sets a line low while the MCU sets it high, a lot of current might go through this line as both device try to drive the line (particularly if not inline protection resistor is used).
+There are several solution to prevent this battle and be able to program the chip:
+  * MCU often have a RST line (active low): driving this line will prevent the MCU to boot and drive the lines, leaving them floating for you to use
+  * lift the VCC pin of the flash chip: now you can power the chip individually, without powering the MCU and preventing to to drive the lines
+  * if there are inline protection resistor on the SPI lines, remove them from the board, preventing the MCU to drive them (be sure to connect your programmer on the flash side of the lines)
+Once this is done, the easiest way to connect to the flash chip is to use a clip.
+This will allow you the clip on all pin of the package, while it is soldered on the board.
+{{:spi_flash:clip.jpg?0x200|}}
+If the flash chip package is not a SOIC (or any where the leads are accessible), such a BGA, you will have to find inline protection resistors, remove them, and connect wires to the pads.
+Now you can use your programmer.
+But it is very important that it sets the right operating voltage.
+Providing 5.0V on 3.3V or 1.8V power rails might damage any of the devices using this power rails.
+Also don't forget to drive the MCU reset line (if this is the solution you are using) since the programmer won't do it.
+==== J-Link ====
+The [[jtag#segger_j-link|J-Link]] is a JTAG programmer, but it recently also got [[https://www.segger.com/products/debug-probes/j-link/tools/j-flash-spi/|SPI programming capabilities]].
+{{:spi_flash:J-Link_BASE.jpg?0x200|}}
+It particularly fits in-circuit programming because it uses the target power instead of providing it, supports 1.8-5.0V, and provides a nRST output to hold the MCU under reset.
+It also allows to [[https://wiki.segger.com/J-Flash_SPI#Custom_Command_Sequences|perform some operations]] before and after talking to the flash chip.
+While it provides a pin to hold the MCU under reset, is does not provide a pin to release reset from the SPI flash chip (which also often has a nRST/nHOLD pin).
+You will have to pull is up yourself if the board doesn't do it already.
+Note that you need hardware [[https://wiki.segger.com/Software_and_Hardware_Features_Overview|version 10 or later]].
+Hardware version 8 does not support SPI flashing, and version 9 releases nCS just before talking to the chip (this seems to be an issue [[https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html|fixed for version 10 with software version 6.86c from 2020-10-06]] but is still present as of 2021-04-14 with firmware version 2021-02-02 and software version 7.00 from 2021-04-08, and setting CS in the init steps does not solve the issue).