This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

F2802x 60MHz Flash wait states

I just noted that the flash wait state settings used by the F2802x v2.10 drivers appear to be different to ones I had been using previously that I think original came from a project based of the blinking LED example project.

My older projects use:

Paged read wait states (FBANKWAIT.PAGEWAIT) = 3

Random read wait states (FBANKWAIT.RANDWATI) = 3

OTP wait states (FOTPWAIT.OTPWAIT) = 5

Whereas the newer settings are 2, 2 and 2 respectively ...

I tried perusing the device datasheet but table 6-51 seems to mandate using 2, 2 and 3 respectively

Which set is correct?? 

Thanks

  • Toby,


    Table 6-51 is correct. Flash and OTP waitstates needs to atleast 2, 2, 3 when using the device at 60 MHz.

    At 60 MHz, you should use waitstates shown below:-

    PAGE WAIT STATE => 2

    RANDOM WAIT STATE => 2

    OTP WAIT STATE =>3

    Regards,

    Manoj

  • Hi Manoj,

    thanks for the clarification. I'm wondering if I make this change to the flash.c driver file in the v220 device support drivers, will I need to rebuild the driverlib.lib for the change to have effect?

    Thanks

  • Yes, you need to rebuild.

    -Manoj

  • Hi Manoj, 

    Only getting back to this now. Just looking into rebuilding. I have added the project from v220/f202x_common/project  to CCS and built with the flash states updated and the compiler version updated from 6.1.0 to 6.2.9.

    CCS is warning that the project contains unresolved buildable linked resources. And I'm thinking this is the "Release" build configuration lib output as it is marked with a yellow exclamation icon overlay in the project explorer pane. The release configuration is not included with the project so I went ahead and built it with the debug configuration. And this seems to have completed without issue.

    Is there any optimization that might be recommended for building the library for release?

    Else, is this all I need to do to have the library updated?

    Thanks