On 28/08/13 23:50, Chris Kilgour wrote:
>> On the part that I'm using, bits 8:7 of SDID are '11' pointing to 4kb sector 
>> sizes.
> The code was developed primarily for Kinetis 'K' series parts.  I 
> exhaustively looked at every K-series data sheet to make the table, but did 
> not look into the other Kinetis series (some of which have been introduced 
> since).
>
> It's possible the 'L' series parts need their own table.  There could be 
> differences in the flash controller too, so we'll have to be careful not to 
> break K-series support.
I checked all of the KL series data sheets that I could find (from a 
KL02 with 32kb up to the KL46 with 256kb) and all have 1kb flash sector 
size.
The KL-series reference manual specifies that SIM_SDID[23:20] define the 
'Kinetis Series ID' as 0001 for 'KL Series'. The K series manuals don't 
say that those bits define the series ID but they are set to zeros (0000 
for K Series?) for the few K series parts that I've checked.
It looks reasonable, then, to check these bits and set 'granularity' to 
0 for KL series parts. I don't think any of the KL series include 
'FlexMemory' so granularity of nvm is not defined.

Apart from setting the granularity and the multi-byte read workarounds, 
the only other thing necessary to get flash working on the KL46Z was to 
force longword programming (set fallback=1 in kinetis_write) as these 
parts don't support the section write command.


------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to