Sunday, April 22nd 2018, 6:54am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Date of registration: Dec 30th 2009

Posts: 8

1

Wednesday, December 30th 2009, 1:20pm

samsung flash chip not supported?

i have reciently buy jlink for my project.
i checked j-flash able to communication with mem command.
but jlink arm not able to work all showing this.

Using adaptive clocking instead of fixed JTAG speed
- Initializing CPU core (Init sequence) ...
- Initialized successfully
- Using adaptive clocking instead of fixed JTAG speed
- J-Link found 1 JTAG device. Core ID: 0x220B10E1 (ARM9)
- ERROR: Identify: Unsupported flash type / bus width (210800). Please contact info@segger.com
- ERROR: Unable to identify Flash
- ERROR: Failed to connect

i have send email also.
flash chip is K5L6331CAA
and i don't have chip datasheet.

Wang

Beginner

Date of registration: Dec 15th 2009

Posts: 1

2

Thursday, December 31st 2009, 2:53pm

Me too having a same problem with SAMSUNG NOR K5J6332CTM in my case JLINK arm is able to communicate but not jflash

me too dont have the datasheet :)

Date of registration: Dec 30th 2009

Posts: 8

3

Thursday, December 31st 2009, 3:06pm

as far as i know both of ic use same map and flash driver.
no datasheet available even in payed way.

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

4

Tuesday, January 5th 2010, 3:31pm

Hi all,

without any datasheet it is a bit hard to say, how to support these flashes.
What would be essentially needed is information about the command set to erase/program the flash and the sectorization.

Best regards
Alex

Date of registration: Dec 30th 2009

Posts: 8

5

Monday, January 25th 2010, 4:33pm

sorry for late reply.
jflash command line may help to just dump and rewrite?

no datasheet for this at all.
there are some similar ic may possible to work on this chip?

one more i have Toshiba chip showing same.

CFI details also not possible to read anything possible on this case?

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

6

Tuesday, January 26th 2010, 2:14pm

Hi Austin,

as previously mentioned:
Without a datasheet of the device which gives information about CFI-compliance, command set, sectorization etc.
unfortunately, there is nothing we can do here.

Best regards
Alex

Date of registration: Dec 30th 2009

Posts: 8

7

Saturday, July 10th 2010, 5:13pm

Hello.
i have folloing details for my one of pcb.

SAMSUNG K5L3217AB
ID : 00EC:2609, Samsung

Device : 0x00400000 (4194304)
Flash Interface description : 0x0000 (0)
Buffer size for buffered write : not supported
Number of Erase Block Regions : 2
Number of Blocks in Region #1 : 8
Block size in Region #1, bytes : 0x00002000
Number of Blocks in Region #2 : 63
Block size in Region #2, bytes : 0x00010000
Total number of all Blocks : 71

can you tell me details how do i update flash.csv with this info?

i think nor device you just need Geometry information for this chip which i provide you.
so can you please let me know possible solution to update jlink csv for this chip.

this info is from tool which support this chip perfectly.
i want to make it supported and many more chip in jlink so i can make jlink better then other tools.

regards

hans salim

Beginner

Date of registration: Apr 21st 2010

Posts: 2

8

Saturday, July 10th 2010, 8:31pm

@stanner

in which tools u get this info???

Date of registration: Dec 30th 2009

Posts: 8

9

Tuesday, July 13th 2010, 4:04pm

@ alex
any update on this part?

@hans salim
Russian tool user give me this details.

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

10

Friday, July 16th 2010, 8:46am

Hi,

this flash does not seem to be CFI compliant, otherwise auto-detection should work.
If it is not a CFI-compliant device having the datasheet is the minimum requirement to implement support for this flash device.

- Alex