Can flash security settings in the K66 block the SDRAM controller?

jch4416 — Wed, 08 Nov 2017 21:12:29 GMT

I’m hoping you can help us on a problem we are having with trying to use SDRAM on the K66. We have some example code from a K65 reference board and an appnote on how to configure the SDRAM controller that we are following. I am able to see the bus activity with a logic analyzer, and while I see precharge and refresh cycles, the code to set the mode register and read or write produces no bus activity. It seems like there is another setting somewhere that is blocking the SDRAM controller from accessing the SDRAM. Do you have any ideas on this?

Last night I found this in the K66 manual:

9.3.1 Security interactions with FlexBus and SDRAM controller
When flash security is enabled, SIM_SOPT2[FBSL] enables/disables off-chip accesses
through the FlexBus and the SDRAM interfaces. The FBSL bitfield also has an option to
allow opcode and operand accesses or only operand accesses.

There is also this warning in the description of the FBSL bits in the SIM_OPT2 register:

9–8
FBSL
FlexBus security level
If flash security is enabled, then this field affects what CPU operations can access off-chip via the
FlexBus or SDRAMinterface. This field has no effect if flash security is not enabled.
00 All off-chip accesses (instruction and data) via the FlexBus or SDRAM are disallowed.
01 All off-chip accesses (instruction and data) via the FlexBus or SDRAM are disallowed.
10 Off-chip instruction accesses are disallowed. Data accesses are allowed.
11 Off-chip instruction accesses and data accesses are allowed.

I looked through the K66 manual to find that the flash security bits live in the FTFE_FSEC register. I read this register in our code and found that the SEC bits (1-0) are 10b which is the unsecure state. So is it reasonable that since the flash security is not enabled, then the SIM_OPT2(FBSL) bits have no effect and there can be no bus accesses by the SDRAM controller?

To complicate matters, the FTFE_FSEC register is read-only and gets it's contents from the flash security byte in the Flash Configuration Field in the flash program memory (from pg 748 of the K66 Ref manual). How then can I enable the SDRAM controller? Compiler switch for code security? We are using IAR workbench.

Does this make any sense at all?

Re: Can flash security settings in the K66 block the SDRAM controller?

jorge_a_vazquez — Wed, 15 Nov 2017 02:21:09 GMT

Hi Jeff

So is it reasonable that since the flash security is not enabled, then the SIM_OPT2(FBSL) bits have no effect and there can be no bus accesses by the SDRAM controller?

Yes, There shouldn't be any problem if you didn't set the security bit and additional to this, if you are using IAR to download the code, it provably didn't set the security bit, because IAR has to be configured in a specific way to allow this. So, with this information we can conclude that the problem is not related with your security status.

Hope this information could help you, I'm looking forward to your reply. Please don't hesitate to contact me if you have any other question.

Have a great day,
Jorge Alcala

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Kinetis MicrocontrollersのトピックRe: Can flash security settings in the K66 block the SDRAM controller?

Can flash security settings in the K66 block the SDRAM controller?

Re: Can flash security settings in the K66 block the SDRAM controller?