8/9/2019 NandPro

1/4

Nandpro supported device interfaces:

USB:LPC2148 Olimex USB header boardHigh performance 16MB/2MinsLibUsb driver

LPT:Parallel Printer Port, SPP modeLow performance, 16MB/35mins (cpu dependant)Dlportio printer port driver

===============================================================================

Seven connections must be made from MAINBRD to the HW device interface.MAINBRD connects as specified to either Olimex board, or a PC printer po

rt.

ArmLpc Olimex LPT MAINBRD

SS EXT1-3 DB25.1 --R--- J1D2.2MISO EXT1-6 DB25.11 -->|-- J1D2.4 Diode, observe polarity!P0.28 EXT2-1 DB25.16 --R--- J2B1.6GND EXT1-26 DB25.18 ------ J1D2.6 or J2B1.12

MOSI EXT1-7 DB25.14 --R--- J1D2.1SCK EXT1-5 DB25.2 --R--- J1D2.3P0.29 EXT2-2 DB25.17 --R--- J2B1.5

===============================================================================

USB Install:Flash the .hex file to the LPC2148.Connect LPC2148 to computer USB.Point "found new hardware" to the "custom.inf"Windows reports: "Your new hardware is ready to use"

USB Hardware:

Connect only wires from EXT connectors to MAINBRD.No resistors or diodes at all. For sure! Do not add them!

===============================================================================

LPT Install:Run the port95nt.exe application to install the DlPortio driver

LPT Hardware:Some parallel ports run at 3.3v others at 5v. The MAINBRD is 3.3 volts.

It is recommend to use 100 ohm series saftey resistors (R)for all lpt connections except for DB25.11 and DB25.18 (GND), as shown

above.Testing with 5 volt lpt and NO resistors didn't burn anything up though.

YMMV :P

For DB25.11 connect diode exactly as shown. It is highly recommended toconnect the diode to the MAINBRD end rather than the PC end of the wire

.Preferred diode is BAT41 or other Schottkey switch diode with low forwa

rd voltage drop.1N4148/53, 1N914, type switching diodes should be also be ok,

8/9/2019 NandPro

2/4

8/9/2019 NandPro

3/4

Read encrypted key vault from a "Virtual Nand" dev:, named vnand.bin, with SPARE:nandpro vnand.bin: -r16 rawkv.bin 1 1

Write encrypted key vault:nandpro dev: -w16 rawkv.bin 1 1

Flash a xell.bin compiler output (no SPARE) to block 40, adding SPARE while flashing:nandpro dev: +W16 xell.bin 40

Read config block from a "Virtual Nand", named vnand.bin, without SPARE:nandpro vnand.bin: -R16 configblk.bin 0x??? 1

Write above config block to dev: adding the SPARE back in:nandpro dev: +W16 configblk.bin 0x??? 1

Write a "small" python.ECC file to "full size" "Virtual Nand" :nandpro vnand.bin: -w16 python.ECC

Write to a dev:, from another RAW file, fixing ECC while writing:nandpro dev: -w16 DumpWithErrors.bin

General Notes:

Reading and writing defaults to the entire device.The start block argumnet is optional and dictates the starting block to program.The ending block is also optional, and end if no block is specified, programmingwill

continue until end of file or end of specified nand size.

Large block nands have different SPARE format than small block nands.The software uses the detected device's SPARE format for all (+) write operations.Files written RAW (-) are not translated in any way.

The "nand size" argument only sets the limit of available blocks for device operations.

It is not hardware related, and need not exactly match the true device.

There is no need to erase before programming.

You can hex edit a block, and use Nandpro to fix its ECC when you write it back.

The "Case" of the command generally indicates if I/O file will contain SPARE ornot

Upper Case: No SPARELower Case: RAW (with SPARE)

The "Virtual Nand" file can be read or be programmed, as if it where a device.The "Virtual Nand" file must be a raw file, containing SPARE.This can be used to extract or inject data from\to an existing raw dump.Example: To inject a "small" python image into an existing

"full size" image, or to extract individual blocks from an existing rawdump.

READING WILL OVER-WRITE AN EXISTING FILE WITHOUT WARNING!NEW LOG FILE WILL OVERWRITE OLD WITHOUT WARNING!

8/9/2019 NandPro

4/4