Not able to communicate with s26kl128 Nor flash

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Mayur_Sj
Level 1
Level 1
5 sign-ins First reply posted First question asked

I am able to communicate with the same family device with larger density (S26KL256)which is  and able to read the its ID using ID (Autoselect) Entry command I used same sequence to read the IID of S26KL128 Nor flash but I am getting all FFFFF. I think the device is not turning on properly for S26KL128 but it works for S26KL256. Even though both are of same family the S26KL128 is not responding. Do I have to turn ON that device differently I used same code to read IId from the device do I have to power on the device differently do we have to ramp up the voltage instead of directly setting it to 3.3V?

0 Likes
1 Solution
Yuvraj
Moderator
Moderator
Moderator
250 replies posted 25 likes received 100 solutions authored

Hi,

Thank you for contacting Infineon Technologies.

 

The S26KL128 does not need to be powered up differently. We can use the same power-up sequence as the S26KL256.

 

From the datasheet in the session Command / address bit assignments

 

Yuvraj_0-1672724696717.png

 

 

We are thinking the address bits for 36-16 (128Mb) and 44-37 (128Mb) are incorrect. Since the address space is in 16-bit-WORD, for example, address bits of 1Gbit (0-2 and 16-38 à total 26 bits) can be used for 64M-WORD (2^26) which is 128MByte (= 1Gbit). Address bits of 128Mbit (0-2 and 16-35 à total 23 bits) can be used for 8M-WORD (2^23) which is 16MByte (= 128Mbit).

Even so, there's nothing problem with supporting 128Mb since the 36-16 eventually supports up to 256Mb. I presume the best description would be

 

44-38 (512Mb)

44-37 (256Mb)

44-36 (128Mb)

Reserved

Reserved for future address expansion.

Reserved bits should be set to ‘0’ by the host controller

37-16 (512Mb)

36-16 (256Mb)

35-16 (128Mb)

Row and upper column address

Half page component of target address.

 

Also

Could you please double-confirm the full OPN of S26KL128S and S26KL256S? Since there is the option to select DCARS and non-DCARS parts, DCARS parts require extra PSC+PSC# differential signal pairs for timing calibration, the DCARS device will not work properly if the PSC+PSC# signal left floating.

 

Yuvraj_1-1672724696729.jpeg

 

Hope the above information clarifies your query.

 

Regards,

Yuvraj 

View solution in original post

0 Likes
7 Replies
Mayur_Sj
Level 1
Level 1
5 sign-ins First reply posted First question asked

Sorry 3.0V*

0 Likes
Yuvraj
Moderator
Moderator
Moderator
250 replies posted 25 likes received 100 solutions authored

Hi,

Thank you for contacting Infineon Technologies.

 

The S26KL128 does not need to be powered up differently. We can use the same power-up sequence as the S26KL256.

 

From the datasheet in the session Command / address bit assignments

 

Yuvraj_0-1672724696717.png

 

 

We are thinking the address bits for 36-16 (128Mb) and 44-37 (128Mb) are incorrect. Since the address space is in 16-bit-WORD, for example, address bits of 1Gbit (0-2 and 16-38 à total 26 bits) can be used for 64M-WORD (2^26) which is 128MByte (= 1Gbit). Address bits of 128Mbit (0-2 and 16-35 à total 23 bits) can be used for 8M-WORD (2^23) which is 16MByte (= 128Mbit).

Even so, there's nothing problem with supporting 128Mb since the 36-16 eventually supports up to 256Mb. I presume the best description would be

 

44-38 (512Mb)

44-37 (256Mb)

44-36 (128Mb)

Reserved

Reserved for future address expansion.

Reserved bits should be set to ‘0’ by the host controller

37-16 (512Mb)

36-16 (256Mb)

35-16 (128Mb)

Row and upper column address

Half page component of target address.

 

Also

Could you please double-confirm the full OPN of S26KL128S and S26KL256S? Since there is the option to select DCARS and non-DCARS parts, DCARS parts require extra PSC+PSC# differential signal pairs for timing calibration, the DCARS device will not work properly if the PSC+PSC# signal left floating.

 

Yuvraj_1-1672724696729.jpeg

 

Hope the above information clarifies your query.

 

Regards,

Yuvraj 

0 Likes
lock attach
Attachments are accessible only for community members.

Hello,

Thanks for the response

Our device does not have DCARS feature so that will not be issue in our case. The address bits which we are addressing for 128 Mbit device should also apply for 256 Mbit device at least for IID as we are sending command as per the data sheet which are same for 128 and 256 and we are keeping reserved field to 0 but some how I am getting FFFF but it is working for 256 density one. Our routine for extracting IID is attached below.

0 Likes
Yuvraj
Moderator
Moderator
Moderator
250 replies posted 25 likes received 100 solutions authored

Hi,


We have checked your code and it looks fine to us.

Can you please provide waveform (logic analyzer) traces with us.

 

Regards,

Yuvraj  

0 Likes

Hello,

Can you suggest which pins do you require I will probe those pins 

0 Likes
Yuvraj
Moderator
Moderator
Moderator
250 replies posted 25 likes received 100 solutions authored

Hi,

Can you please provide all the signal lines? in order to analyze we need all the signals. 
IO#0 is important since our manufacture ID is 0x01 which will be seen on io#0.

Regards,

Yuvraj 

0 Likes

Ok will provide you the trace the weird part is I am able to erase program and read back program value from the device correctly but not able to read the IID

0 Likes