On 4.2.2015 13:16, Jens Bauer wrote:
> Hi Tomas.
>
> On Wed, 04 Feb 2015 09:18:14 +0100, Tomas Vanek wrote:
>
>> I made a quick research and found these new families potentially
>> unsupported:
>>
>> SF4: K11_M50 K12_M50
>>          KL16_M48 KL26_M48
>> SF5: K21_M50 K21_M120 K22_M50 K22_M120 K24_M120 K63 K64
>>          KL16_M48 KL26_M48
>> SF6: KL17_M48 KL27_M48
>> SF7: KV31_M120
>> SF8: KV31_M120
>> SF9: K22_M100 KV31_M100
>> SFA: K02_M100 KV30_M100
> If it's just a matter of adding sector size and flash size, it's easy.
It's quite easy for single one chip type. Not for such (still growing) 
number of families.

>
>> SFx is suffix of data sheet/reference manual name and x equals
>> "granularity" value in existing driver.
>> Existing driver supports SF0, 1, 2, 3.
>> All small chips like Jens's MKE02 are in SF0 family. So the only
>> problem for MKE02 and similar is that driver can not detect it.
> No, unfortunately, the problem is more than that.
> If you flash-program the device, while it's running at the wrong speed, 
> you'll damage the device.
> -Also the registers differ. There is no SIM_SDID register on the KE02, KE04 
> and KE06 devices.
> In addition, there's no "protection" on these devices, like on the K-series.
>
Yes, you're right.
There is not much problem in setting FCLKDIV - I assume every KExx sets 
FEI mode @48MHz at reset (busclk 24MHz).
But indexed access to FTMRE register through FCCOBIX is horrible. K and 
KL have more or less compatible FTFx.
KExx should have theirs own driver. If you write one, I volunteer to 
test a MKE06.

Tom

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to