[SOLVED]Programming a EP7312 from Cirrus Logic with J-Flash

ismu · Nov 15th 2011, 11:33pm

Hi!

I try to download a bin file in a EP7312 (cirrus.com/en/pubs/manual/ep73xx_um-f.pdf for datasheet...) but I get a

Source Code

- ERROR: Programming failed @ 0x0 - Block Lock-Bit Detected
- ERROR: Programming failed @ 0x2 - Block Lock-Bit Detected

I can connect to the target, read it, erase it,find CFI compliant device, but writing to it is not working(see log at end of the message). The EP7312 don't seems to have any protection/locking features(as far as I know!)

I also had to remove the option "Automatically unlock sectors if necessary" in global setting, this option make the J-Flash program to crash.

Any help will be greatly appreciated!

Following is the log :

Source Code

Connecting ...
- Connecting via USB to J-Link device 0
- J-Link firmware: V1.20 (J-Link Ultra Rev.1 compiled Sep 6 2011 16:34:45)
- JTAG speed: 5 kHz (Fixed)
- Initializing CPU core (Init sequence) ...
- Initialized successfully
- JTAG speed: 7143 kHz (Auto)
- J-Link found 1 JTAG device. Core ID: 0x0F0F0F0F (ARM7)
- Reading CFI info ...
- CFI info read successfully
- Connected successfully
Programming target (32784 bytes, 1 range) ...
- ERROR: Programming failed @ 0x0 - Block Lock-Bit Detected
- ERROR: Programming failed @ 0x2 - Block Lock-Bit Detected
- ERROR: Failed to program target
Disconnecting ...
- Disconnected

Display All

SEGGER - Alex · Nov 17th 2011, 8:48am

Hi,

The EP7312 don't seems to have any protection/locking features(as far as I know!)

The EP7312 does not, but the flash itself may have one.
Did you check the nWP pin of the flash?
We had some customers which had this pin floating on their hardware which caused similar problems.
Sometimes it is more worst because it works most of the time and sometimes it does not.

Best regards
Alex

ismu · Nov 17th 2011, 2:59pm

Good suggestion!

After reviewing almost every pages of the EP7312 data sheet and the ARM7 documentation, this was the next point I was about to check on my design(should check this earlier!)

ismu · Nov 17th 2011, 5:41pm

Hi again,

As I said on the first message, the option "Automatically unlock sectors if necessary" make the program J-Flash (version 4.36e) crash when it try to soft unlocking sectors.

The document UM08003_JFlashARM.pdf mention a Lock / Unlock sectors in the Target menu elements, but they are not present in my version of J-Flash (does it appear only when particular flash devices are selected?).

Is it possible to manually unlock sector using other software provided by segger (ex. j-link commander)
or to use an older version of J0-Flash (in case the my crash problem was introduced recently)

Thanks in advance

SEGGER - Alex · Nov 17th 2011, 9:33pm

Hi,

As I said on the first message, the option "Automatically unlock sectors if necessary" make the program J-Flash (version 4.36e) crash when it try to soft unlocking sectors.

Sorry, I overlooked that. Already fixed in the current version (V4.36i).

Explicit unlocking is not necessary, since J-Flash does this automatically, if necessary.

Best regards
Alex

ismu · Nov 17th 2011, 11:10pm

I didn't saw that version "i" was out, I will try it tomorrow!

ismu · Nov 18th 2011, 3:53pm

Thanks, it works better with version i

Now that I can download with J-Flash, this bring me another question(but I will start a new thread for this)

SEGGER - Alex · Nov 21st 2011, 8:48am

Hi,

Good to hear.
So we consider this one here as solved.

Best regards
Alex

Source Code

Source Code

Share