S29JL-J：DQ7，DQ6和DQ5在0到1编程时的状态

嗨，Naoaki san，
最初，或者在一个芯片擦除命令之后，闪存的默认值是1。通过程序操作，您可以将其更改为0。请注意，使它再次1，你需要执行擦除操作。程序操作不会改变0到1。
DQ5＝1可能发生在两种情况下。
1）如果系统试图将1编程到先前被编程为0的位置，则设备可以在DQ5上输出1。只有擦除操作可以将0变回1。在这种情况下，装置停止操作，并且当超过定时限制时，DQ5产生1。
2）DQ5指示程序或擦除时间是否超过指定的内部脉冲计数限制。在这些条件下，DQ5产生1，表明程序或擦除周期没有成功完成。
每当系统最初开始读取拨号位状态时，它必须读取DQ15-DQ0（或DQ7- DQ0对于X8仅设备）至少一次两次以确定切换位是否正在切换。通常，系统将在第一次读取之后记录并存储切换位的值。在第二次读取之后，系统将将切换位的新值与第一个值进行比较。如果切换位不切换，则设备已完成程序或擦除操作。该系统可以读取DQ15-DQ0（或DQ7- DQ0的X8仅设备）的阵列数据在下面的读取周期中。然而，如果在初始两个读周期之后，系统确定切换位仍在切换，系统也应该注意DQ5的值是否高。如果是，系统应该再次确定切换位是否正在切换，因为切换位可能已经停止切换，就像DQ5变高一样。如果切换位不再切换，设备已经成功地完成了程序或擦除操作。如果它仍在切换，则设备没有成功地完成操作，并且系统必须写入RESET命令以返回到读取阵列数据。
谢谢和问候，
普拉迪普塔



     以下为原文
  Hi Naoaki-san,
 
Initially, or after a chip erase command the default value for flash memory is 1. By a program operation you can change it to 0. Please note to make it 1 again you need to carry out a erase operation. A program operation will not change a 0 to 1.
 
DQ5 = 1 can happen under two circumstances.
1) The device may output a 1 on DQ5 if the system tries to program a 1 to a location that was previously programmed to 0. Only an erase operation can change a 0 back to a 1. Under this condition, the device halts the operation, and when the timing limit has been exceeded, DQ5 produces a 1.
 
2) DQ5 indicates whether the program or erase time has exceeded a specified internal pulse count limit. Under these conditions DQ5 produces a 1, indicating that the program or erase cycle was not successfully completed.
 
Whenever the system initially begins reading toggle bit status, it must read DQ15–DQ0 (or DQ7–DQ0 for x8-only device) at least twice in a row to determine whether a toggle bit is toggling. Typically, the system would note and store the value of the toggle bit after the first read. After the second read, the system would compare the new value of the toggle bit with the first. If the toggle bit is not toggling, the device has completed the program or erase operation. The system can read array data on DQ15–DQ0 (or DQ7–DQ0 for x8-only device) on the following read cycle. However, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the system also should note whether the value of DQ5 is high. If it is, the system should then determine again whether the toggle bit is toggling, since the toggle bit may have stopped toggling just as DQ5 went high. If the toggle bit is no longer toggling, the device has successfully completed the program or erase operation. If it is still toggling, the device did not completed the operation successfully, and the system must write the reset command to return to reading array data.
 
Thanks and Regards,
Pradipta.

你好，普拉迪帕塔，
顾客想再现使DQ5 = 1时试图改变点从0~1的程序运行程序。
在客户板上，没有观察到DQ5＝1的状态。
是否有一个程序来复制状态，5 = 1时试图改变点从0~1的程序操作？
最好的问候，
森本



     以下为原文
  Hello Pradipta-san,
 
The customer wants to reproduce the procedure of making DQ5 = 1 when trying to change the bit from 0 to 1 by program operation.
On the customer's board, no state where DQ5 = 1 is observed.
Is there a procedure to reproduce the state where DQ5 = 1 when trying to change bit from 0 to 1 by program operation?
 
Best Regards,
Naoaki Morimoto

嗨，Naoki san，
您正在尝试复制DQ5＝1条件。你能让我们知道你尝试下面的过程和你的观察。
——>；该装置可以输出1的5如果系统试图计划1的一个位置，以前编程0。只有擦除操作可以将0变回1。在这种情况下，设备停止运行，当时间超出限制，DQ5产生1。
谢谢和问候，
普拉迪普塔



     以下为原文
  Hi Naoki-san,
 
You are trying to reproduce the DQ5=1 condition. Can you let us know did you try the below process and your observation.
--->The device may output a 1 on DQ5 if the system tries to program a 1 to a location that was previously programmed to 0. Only an erase operation can change a 0 back to a 1. Under this condition, the device halts the operation, and when the timing limit has been exceeded, DQ5 produces a 1.
 
Thanks and Regards,
Pradipta.
 
 

嗨，Pradipta san，
客户尝试将程序1编程到先前编程到0的位置。
这是为了确认对FRAM进行非法访问时的操作，它不用于实际的大规模生产产品。
根据数据表，它说1是输出到DQ5，但似乎程序结束正常，而DQ5保持0的客户评价（但是，数据仍然是0）。
超过限时后DQ5变成1需要多长时间？
也许客户监控DQ5的时机太早了。
最好的问候，
森本



     以下为原文
  Hi Pradipta-san,
 
The customer tries to program 1 to a location previously programmed to 0.
This is to confirm the operation when illegal access is made to F-RAM, it is not used for actual mass production product.
 
According to the data sheet, it says that 1 is output to DQ5, but it seems that the program ended normally while DQ5 remains 0 in customer's evaluation (However, the data remained 0).
 
How long will it take for the DQ5 to become 1 after the timing limit is exceeded?
Perhaps the timing for customers to monitor DQ5 is too early.
 
Best Regards,
Naoaki Morimoto

嗨，Pradipta san，
你有什么更新吗？
如果0被编程为1，DQ 5月5日的状态为1，或者可能不是？
在这种情况下，差异的原因是什么？
或者DQ5总是1？
最好的问候，
森本



     以下为原文
  Hi Pradipta-san,
 
Do you have any update?
If 0 is programmed to 1, the state of DQ 5 may be 1, or may not it be?
In that case, what is the reason for the difference?
 
Or should DQ5 always be 1?
 
Best Regards,
Naoaki Morimoto

嗨，Naoki san，
我们的团队已经测试了这个序列对房jl064j硅，当我们试图设置位已经编程0，回到1，5设置一定的时间之后，没有立即。
你可以附上这封邮件全记录。
下面是使用的序列：
读取偏移0：0xffff（readop 0）程序0x0抵消0x0（programop 0 0）验证偏移0x0包含0x0作为数据（readop DT（0）显示跟踪）：验证程序的数据tracestry 0x1抵消0x0（programop 0 1）à状态是“暂停”DT（显示跟踪验证）：tracesread切换数据（0xe4）读切换数据（0xa4）读切换数据（0xe4）…
你可以看到它先忙于DQ6的切换6步的痕迹（0xC4–0x84–0xC4–0x84…）然后在一个超时时间开关切换数据：0xe4–0xa4–0xe4–0xa4…这意味着5设置为1。
所以你可以看到，操作无法成功完成。5始终被设置和软件应该能够抓住这个超时事件。
S29 JL064 JJTestLogy.TXT.ZIP
2 K



     以下为原文
  Hi Naoki-san,
 
Our Team has just tested this sequence on real JL064J silicon and when we tried to set bits which are already programmed to 0, back to 1, DQ5 is set after a certain timeout period, not immediately.
You can find the full logs attached to this email.
 
Here is the sequence used:

• Read offset 0x0: 0xFFFF (ReadOp 0)
  
• Program 0x0 to offset 0x0 (ProgramOp 0 0)
  
• Verify that offset 0x0 contain 0x0 as data (ReadOp 0)
  
• dt (display trace): verify traces
  
• Try to program data 0x1 to offset 0x0 (ProgramOp 0 1) à Status is “timeout”
  
• dt (display trace): verify traces
  
• Read toggling data (0xE4)
  
• Read toggling data (0xA4)
  
• Read toggling data (0xE4)
  
• …
  

 
You can see from the traces in step 6 that the device goes first busy with DQ6 toggling (0xc4 – 0x84 – 0xc4 – 0x84 …) then after a timeout period switches to toggling data: 0xE4 – 0xA4 – 0xE4 – 0xA4 … which means DQ5 was set to 1.
So as you can see, the operation can never complete successfully. DQ5 will always be set and the SW should be able to catch this timeout event.

•   S29JL064J_Test_logs.txt.zip 2.0 K