Re: [OpenOCD-user] PSOC4 flash protection

[Tomas V. <to...@us...>]

Juan,

please understand that 'flash protect' command changes protection of 
sectors in the range (first..last) and
leaves protection of other sectors intact. So commands “flash protect 0 
254 255 off“ and “flash protect 0 0 253 on”
are quite different. If you want to set protection for your application 
without care about previous protection
state, you have to issue both commands.

Regarding to newer PSoC4 devices (Cortex-M0+ powered): the patch I 
pointed in the last mail adds
complete support to whole family. Please test and review it if you want 
to help.

KitProg2 native protocol will not be supported as Cypress plans to drop 
it in favor of CMSIS-DAP protocol.
Both KitProg and KitProg2 with latest firmware support CMSIS-DAP, 
unfortunately without Cypress proprietary "acquire".

Tom

On 04.01.2018 10:27, jc....@se... wrote:
>
> Hi Tomas,
>
> Thanks for your reply.
>
> As I mentioned before, the command “flash protect 0 0 1 on” protects 
> the whole memory, even if it should only protect two rows, logically.
>
> For my usage, the command “flash protect 0 254 255 off“ did the job, 
> even if the “flash protect 0 0 253 on” should do the same.
>
> Maybe there is a small but in the psoc4 integration or in the way 
> openOCD handle this command…
>
> Is there any thoughts integrating the M0+ familly of the PSOC4, and 
> the new KitProg2?
>
> There is someon here 
> https://sourceforge.net/p/openocd/mailman/message/35272050/ who has 
> done the search. Maybe if help is needed ( in the way of my 
> possibilities), I could contribue to the support of, at least, the 
> support of the 4100S/4200S family.
>
> Juan-Carlos
>
> *Von:*Tomas Vanek [mailto:to...@us...]
> *Gesendet:* Mittwoch, 3. Januar 2018 16:18
> *An:* jc....@se...
> *Cc:* ope...@li...
> *Betreff:* Re: [OpenOCD-user] PSOC4 flash protection
>
> Hi Juan,
>
> On 03.01.2018 15:09, jc....@se... 
> <mailto:jc....@se...> wrote:
>
>     My concern is about protecting the flash: there are two rows used
>     as EEprom simulation.
>
>     I wanted to protect the rest using the command
>
>     >flash protect 0 0 254 on # as my target has 256 rows
>
>     Unfortunately, when I try to read the content on another machine
>     (Windows and PSOC Programmer tool), I retrieve that the whole
>     flash is write protected.
>
>     I even tried to set the third parameter to 1 ( just one row/block)
>     with the same result
>
> If you want 2 last rows unprotected you should issue on unprotected device
>     flash protect 0 0 253 on
>
> If device is already protected use
>     flash protect 0 254 255 off
>
> If it still does not work, please send output of flash info 0
>
>     BTW, why is the command “program” not supported for the psoc4 devices?
>
> Because PSoC4 flash does not support erase a row.
> There are two workarounds.
> - the preferred one: recompile OpenOCD from git source with change 
> http://openocd.zylin.com/3807 applied
> - or add to your config file
>     psoc4 flash_autoerase 0 on
>
> Tom
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> OpenOCD-user mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openocd-user