使用C90LC闪存驱动器来访问数据闪存,也可以使用相同的驱动程序进行阴影闪存吗？

你好迈克，
 
是的，您可以使用相同的驱动程序访问阴影闪存。
 
比较例子
SPC560Dxx用于发现的无操作系统闪存测试应用程序
 
你可以保护阴影行如下：
 
 
 
 
 
 
 
第27章RM0045详细介绍了更多信息。
 
 最好的祝福
 
 二万



以下为原文








Hello Mike ,

Yes , you can use the same driver to access to the shadow flash.

cf example in  
SPC560Dxx OS-Less Flash Test Application for Discovery

you can protect the shadow row as below :

• /*==================== Lock to Protect Shadow Row ====================*/
  

• test_string_print(&SD1,  
  

• ''Lock shadow row: ''
  

• );
  

• returnCode = pSetLock( &ssdConfig, LOCK_SHADOW_PRIMARY, 1, FLASH_LMLR_PASSWORD );
  

• if
  

• ( C90FL_OK != returnCode )
  

• {
  

•    
  

• ErrorTrap(returnCode);
  

• }
  

• returnCode = pSetLock( &ssdConfig, LOCK_SHADOW_SECONDARY, 1, FLASH_SLMLR_PASSWORD );
  

• if
  

• ( C90FL_OK != returnCode )
  

• {
  

•    
  

• ErrorTrap(returnCode);
  

• }
  

• test_string_print(&SD1,  
  

• ''DONErn''
  

• );
  

More informations are detailed in Chapter 27 RM0045.

Best regards

                    Erwan

谢谢Erwan的回复。我有几个与Flash Integration测试应用程序相关的查询。
 
1.“锁定保护暗影行”声明是否仅保护暗影闪光？我想保护完整的代码和数据闪存免受读/写访问。
2.查看代码，我知道它首先将密码写入shadow，然后使用Get和Set lock函数的组合。是否需要按照此序列进行审查功能？
3.此外，对于C-Flash，应用程序执行此Get和Set功能，然后继续执行擦除，空白检查，程序，验证等闪存操作。但对于D-flash，它首先重置锁定状态然后执行闪存操作。这怎么样？
4.在这个应用程序中，我确实看到使用变量'blkLockState'进行D Flash处理，但这不适用于C Flash。怎么样？
5.定义'RUN_IN_FLASH'的地方？还是没有定义？
6.锁定恢复怎么样？我知道在锁定但是使用串行闪存启动的情况下无法恢复MCU，是否可以获得闪存的访问权限？
 
期待您的最早回复，因为我被困在这个审查功能。提前致谢。
麦克风



以下为原文





Thanks Erwan for the reply. I have couple of queries related to Flash Integration test application.

1. Does the statement 'Lock to Protect Shadow Row' protects only Shadow flash ? I want to protect full code and data flash from read/write access.
2. Looking at the code, I do understand that it first writes the password to shadow and then uses the combination of Get and Set lock functions. Is it required to follow this sequence for Censorship feature?
3. Also for C-Flash, the application does this Get and Set functions and then goes on performing the flash operations like erase, blank check, program, verify etc. But for D-flash, it first resets the lock state and then performs the flash operations. How is this?
4. In this application, I do see use of variable 'blkLockState' for D Flash handling but this is not done for C Flash. How is it?
5. Where the 'RUN_IN_FLASH' is defined? or not defined?
6. How about the recovery from lockout? I do understand that it is not possible to recover the MCU in case of lockout but using serial flash boot, is it possible to gain the access for flash memory?

Look forward for your earliest reply as I am stuck for this censorship feature. Thanks in advance.
Mike

你好，Erwan，
 
我尝试了解Flash集成测试应用程序。我正在为我之前关于此应用程序的查询编写答案。请告诉我您的意见，请尽早回答其余的问题。
1.“锁定保护暗影行”声明是否仅保护暗影闪光？我想保护完整的代码和数据闪存免受读/写访问。
迈克：它只保护阴影行/闪光灯。 SetLock函数锁定块以进行编程/擦除。用于此锁定/解锁的密码与NVPWD0 / 1值不同。
2.查看代码，我知道它首先将密码写入shadow，然后使用Get和Set lock函数的组合。是否需要按照此序列进行审查功能？
Mike：没有特定的Get / Set锁定功能序列。该组合可用于验证块是否被锁定以进行编程/擦除。
3.此外，对于C-Flash，应用程序执行此Get和Set功能，然后继续执行擦除，空白检查，程序，验证等闪存操作。但对于D-flash，它首先重置锁定状态然后执行闪存操作。这怎么样？
 
 
4.在这个应用程序中，我确实看到使用变量'blkLockState'进行D Flash处理，但这不适用于C Flash。怎么样？
 
5.定义'RUN_IN_FLASH'的地方？还是没有定义？
Mike：它在“应用程序配置”下定义 - ＆gt;“运行时设置” - ＆gt;在RAM中加载。它是否正确？
6.锁定恢复怎么样？我知道在锁定但是使用串行闪存启动的情况下无法恢复MCU，是否可以获得闪存的访问权限？
 
 
7.我可以使用FlashWrite函数写入Shadow块吗？我想写新的NVPWD0 / 1值来实现审查。
 
最好的祝福，
麦克风



以下为原文






Hello Erwan,

I tried understanding the Flash Integration Test Application. I am writing my answers for my earlier queries about this application. Please let me know your views and please answer for the remaining queries at the earliest.

1. Does the statement 'Lock to Protect Shadow Row' protects only Shadow flash ? I want to protect full code and data flash from read/write access.

Mike: It protects the shadow row/flash only. The SetLock function locks the block for program/erase. The passwords used for this lock/unlock are different from the NVPWD0/1 values.

2. Looking at the code, I do understand that it first writes the password to shadow and then uses the combination of Get and Set lock functions. Is it required to follow this sequence for Censorship feature?

Mike: No specific sequence for Get/Set lock function required. The combination can be used to verify if a block is locked for program/erase.


3. Also for C-Flash, the application does this Get and Set functions and then goes on performing the flash operations like erase, blank check, program, verify etc. But for D-flash, it first resets the lock state and then performs the flash operations. How is this?



4. In this application, I do see use of variable 'blkLockState' for D Flash handling but this is not done for C Flash. How is it?


5. Where the 'RUN_IN_FLASH' is defined? or not defined?
Mike:It is defined under ‘Application Configuration’->’Runtime Settings’->Load in RAM. Is this correct?
6. How about the recovery from lockout? I do understand that it is not possible to recover the MCU in case of lockout but using serial flash boot, is it possible to gain the access for flash memory?


7. Can I use FlashWrite function to write to Shadow block? I want to write new NVPWD0/1 values to achieve Censorship.

Best Regards,
Mike

你好，Erwan，
 
我尝试使用C90LC闪存驱动程序实现审查功能。我正在观察闪存驱动程序的以下错误代码，
0x00000002 - 在闪存操作之前设置EER位。
此错误主要用于FlashInit调用。我尝试从CFLASH.MCR寄存器清除ERR位但不起作用。
 
0x00000700 - 源之间存在不匹配
数据和已检查的闪存中的内容。
此错误适用于FlashWrite调用。
 
两个错误代码都是随机观察到的并且不一致。我已经将C90LC闪存驱动程序用于数据闪存并使用相同的调用，新的ssdConfig指向代码闪存，但仍然存在错误。我无法测试审查功能，因为init和write调用无法正常运行。你能否澄清我是否遗漏了审查功能的任何内容？
 
您在这方面的最早帮助将受到高度赞赏。提前致谢。
 
最好的祝福，
麦克风



以下为原文





Hello Erwan,

I tried implementing the Censorship feature using C90LC flash driver. I am observing following error codes from the flash driver,
0x00000002 - EER bit is set before Flash operations.
This error is mainly for the FlashInit call. I tried clearing the ERR bit from CFLASH.MCR register but does not work.

0x00000700 - There is a mismatch between the source
data and the content in the checked Flash memory.
This error is for FlashWrite call.

Both the error codes are observed at random and not consistent. I have already used the C90LC flash driver for Data flash and used the same call with new ssdConfig pointing to Code flash but still the errors are there. I am unable to test the censorship feature as the init and write calls are not functioning correctly. Can you please clarify if I am missing anything for Censorship feature?

Your earliest help in this regard will be highly appreciated. Thanks in advance.

Best Regards,
Mike