Hello!
While creating a circuit based on KL43Z I realized, that after giving it to an end user I need to allow easy updates of software and configuration data.
Firstly, preventing the code from being read and at the same time giving an easy Click&Go interface for updates?
How can it be done?
Thank you for any suggestions!
已解决! 转到解答。
Hi
Probably the simplest method is to use USB-MSD. There are various reasons which make it very attractive (and generally the preferred solution):
1. It works with Windows, MAC, Linux (and may such systems)
2. It doesn't need drivers or installation
3. Simply plug in the USB cable, which also supplies power
4. No software needed at the PC side since it uses whatever file manager it has
5. Drag and drop file onto the device as it appears as a hard drive
The same is possible for adding configuration data (eg. it appears as two drives - one called "Upload" and one called "config", for example).
The software is protected since it can't be read back (unless it should be, or it can be password-protected).
That is, it works much the same as the OpenSDA loading on the Freedom boards.
Proven solution for KL43 available at µTasker FRDM-KL43Z support
Regards
Mark
Kinetis: µTasker Kinetis support
KL43: µTasker FRDM-KL43Z support / µTasker TWR-KL43Z48M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
Hi
Probably the simplest method is to use USB-MSD. There are various reasons which make it very attractive (and generally the preferred solution):
1. It works with Windows, MAC, Linux (and may such systems)
2. It doesn't need drivers or installation
3. Simply plug in the USB cable, which also supplies power
4. No software needed at the PC side since it uses whatever file manager it has
5. Drag and drop file onto the device as it appears as a hard drive
The same is possible for adding configuration data (eg. it appears as two drives - one called "Upload" and one called "config", for example).
The software is protected since it can't be read back (unless it should be, or it can be password-protected).
That is, it works much the same as the OpenSDA loading on the Freedom boards.
Proven solution for KL43 available at µTasker FRDM-KL43Z support
Regards
Mark
Kinetis: µTasker Kinetis support
KL43: µTasker FRDM-KL43Z support / µTasker TWR-KL43Z48M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
Mark Butcher - thank you for an answer.
Since I can't send you a private message - would I be able to use mbed and your bootloader at the same time?
I want to use mbed since I think it allows me to connect and use SSD1306 LCD more easily (there is a library for this bootloader)
Hi
I haven't used mbed libraries so can't be sure but usually there is no problem using libraries from one source in a different project.
Note however that the uTasker project also includes character LCD, graphical LCD, TFT, OLED and segment LCD support
http://www.utasker.com/docs/uTasker/uTaskerLCD.PDF
http://www.utasker.com/docs/uTasker/uTasker_SLCD.pdf
and can simulate their operation, meaning that it if often even easier to use.
If your question is more about loading applications from different sources with the uTasker loader then this is no problem. The following is a general guide, whereby many MQX, Arduino, mbed and other applications have been used with it: Configuring Foreign Applications to work with the uTasker Serial Loader
Regards
Mark
Kinetis: µTasker Kinetis support
KL43: µTasker FRDM-KL43Z support / µTasker TWR-KL43Z48M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
Hi Piotr
I have sent you links to the "Developer's" version of the project which contains integrated suport for all K, KL, KV, KE and KEA parts (including your KL43). [Next version also incluing KW2x support].
Binary files can be loaded to the FRDM-KL43Z using its USB-MSD OpenSDA loader. Also KDS and CW allow loading binary files to any board with its supported debuggers.
Once you have the compete package you can build and define your preferred output format - supported tool chains/IDE are:
KDS, CW6x, IAR, Keil uVision, Atollic, Rowley Crossworks, CooCox, Greenhills, standalone GCC and VisualStudio simulation - detail at the compiling page: µTasker Kinetis Compiler Information
This means that the same code will build with any of the compilers and you can change between them if you want without any effort; the same is true for target processors - all code can run on any Kinetis part (as long as the part has the peripherals required for the application) by changing maximum 3 project defines (and possibly redefining the specific pins to be used by the particular HW).
Regards
Mark
Kinetis: µTasker Kinetis support
KL43: µTasker FRDM-KL43Z support / µTasker TWR-KL43Z48M support
For the complete "out-of-the-box" Kinetis experience and faster time to market