1.easyopenjtag Usage Tutorials

write code using Easyopenjtag or Openjtag

If the Openjtag burning write bare board program appears, "No CPU is detected (ID=0XFFFFFFFF)" Reason should be

1. Development Board not power on
2. Jtag line is not connected.

Reference video	The No. 0 Lesson 1th Section _ Just contact the Development Board interface wiring Tool The No. 0 Lesson 2nd Section _ Just contact the Development Board Burn writes the bare board procedure "
This document uses the environment	Win7 32-bit Win7 64-bit

2.1 Easyopenjtag (hereinafter referred to as EOP) and Openjtag (OP) Introduction

The difference between the two is explained in detail in a table below.

Unit	Patent development of hundred questions net	Patent development of hundred questions net
Applicability	2410,2440,6410, etc.	2410,2440,6410, etc.
Burn Write Range	Can burn to nor flash,nand Flash	Can burn to nor flash,nand Flash
Voltage Range	3.3~5v	1.2~5v
Serial level	TTL level	RS232 level
Interface	3 JTAG interfaces, A 4-pin socket (Leads to 5v/gnd/txd/rxd four feet)	2 JTAG interfaces, 1 x DB9 serial port
Driver Program	Same	Same
Program Burn Write	Same	Same
Program debugging	Debug bare metal, Uboot,linux kernel via JTAG protocol	Debug bare metal, Uboot,linux kernel via JTAG protocol
Maximum Benefits	Burn the code directly into NAND flash, Debug bare metal, Uboot,linux kernel	Burn the code directly into NAND flash, Also with USB to serial port function, Debug bare metal, Uboot,linux kernel

Op or EOP supports burning code to nor flash or NAND flash, while the jlink on the market can only burn code to nor flash.

2.2 Recommended Downloads Summary of Burn-write methods

Program Download burn write can be divided into 2 steps: Download, burn write.

Download and burn-write are different concepts

Download	Via USB (e.g. DNW), network download (e.g. TFTP), code down to SDRAM
Burn Write	NAND flash-driven NAND flash write function to write code in SDRAM into NAND flash

It is strongly recommended that:

1. Use Op/eop to burn the disc \bin\uboot.bin to NOR flash

2. Burn the bare-metal code directly into NAND flash using OP/EOP

While the Uboot,linux kernel of NAND flash, the root file system is stored in the following location:

Partition	Content	Nand Flash Address Assignment
Bootloader Partition	Uboot partition	0-----------------------256k
Environment variable Partitioning	Environment variables	256k------------------256k+128k
Kernel partition	Linux kernel	256k+128k----------256k+128k+2m
ROOTFS partition	Root file system	256K+128K+2M----256M

Storage location You can enter print on the uboot command line to know:

To view the environment variable mtdparts:

Mtdparts=mtdparts=nandflash0:256k@0 (bootloader), 128k (params), 2m (kernel),-(Root)

2.3. Connect PC, EOP (or op), JZ2440 Development Board

Special Note:

The OP and Eop connection methods, driver installation, program burning method are all identical, only in EOP as an example.

The full picture of EOP is as follows:

Wiring diagram for JZ2440 and EOP: