Major changes in this new release:
- FreeRTOS V9.0.0 with static memory allocation.
- Shell with single character I/O function.
- FatFS File System with extra shell commands for memory dump and file creation.
- Segger SystemViewer library updated to V2.36a
FreeRTOS component has been updated to the V9.0.0 release which supports as main feature static memory allocation for tasks, queues, semapore, mutex, etc to have a completely statically allocated RTOS. See “FreeRTOS V9.0.0 with Static Memory Allocation” for details.
The Shell has added a SendCh() method to send a single character to a standard I/O channel:
The FatFS component has now a method and shell command to dump a file in hexadecimal format with ASCII on the side. The following shows a hex dump of a file with “hello world\r\nagain” in it:
CMD> FAT1 printhex test.txt 0x00000000: 68 65 6C 6C 6F 20 77 6F 72 6C 64 0D 0A 61 67 61 hello world..aga 0x00000000: 69 6E -- -- -- -- -- -- -- -- -- -- -- -- -- -- in--------------
The command ‘create’ has been added to the shell for FatFS to create an empty file.
The Segger SystemViewer libraries have been updated to V2.36a. The host viewer comes with several improvements.
The toolbar has a direct way to zoom-in and zoom-out plus a toolbar icon for the cursor position:
I hope this new release is useful. The new release is available on SourceForge here: https://sourceforge.net/projects/mcuoneclipse/files/PEx%20Components/
See “McuOnEclipse Releases on SourceForge” how to download and install it.
Happy Updating 🙂
Nice! Thanks Erich
Do you know when NXP will release the RTOS Plugin (same as Seggers SystemView)?
Do you prefer to use a custom Eclipse install or simple use KDS?
Which is your go to FRDM board?
I don’t know the date. Currently I prefer the KDS install for myself and my students, as it is pretty much the custom Eclipse install, and would be pretty much the same as with a custom install.
I usually order FRDM boards at Mouser, sometimes at element14/Farnel.
As I told you in previous messages I am new to this world of Kinetis. With the help of your tutorials I am starting to take the control of this enviroment. I managed to mount the FreeRTOS with the PE and read the ADC on a FRDM-KL46Z, which is the starting point of my project.
After updating the MCU on ECLIPSE I tried to use the shell but something is wrong with the USB inizialitation and I can’t compile. When I add the component on the PE I accept all the components that are needed. The USB component created shows an error in the Inherited USB init. If I disable the inherit USB init, the error on the PE disappears, but when I try to compile there are errors on the
/* Kinetis KL46Z48 */
NVIC_ICER = (1<<24); /* Disable interrupts from USB module (Interrupt Clear-Enable Register) */
The NVIC_ICER isn't defined.
Surely its a matter of configuration but I wasn't able to find the error.
Regards and thanks in advance
Could you try the USB CDC project for FRDM-KL46Z on GitHub here:
You will need the USB_Init, otherwise the USB peripheral is not initialized. Make sure you use the Init_USB_OTG component for Kinetis.
If you disable the USB Init in the component, it has to be available âoutsideâ the USB component.
I hope this helps,
Erich, I took your class in Austin on FreeRTOS debugging with Mark Ruthenbeck assisting you. It was a great class. You scanned my contact info. My name is Sayre Swarztrauber.
I’m familiar with FreeRTOS on other processors. I’d like to jump start a new FreeRTOS 9 project on the Kinetis KV5x Tower board with Ethernet, SPI flash and a couple of serial ports. For the development environment I’ll have KDS, Processor Expert, JLink, Percepio and Segger System View – just like your class (except PEx). Do you think this all will work with the new KV5x Tower board? Is everything ready yet? Do you foresee and issues? Can you point me in the right direction? Is there any paid support I can get from Professional services or elsewhere?
good to hear that you liked that class, thank you!
I do not have a KV tower board, and I have no experience with the V family. But for KV5 there is no support for it with Processor Expert, so that option would be an issue with your setup. It does support some KV1x and KV3x, but again no KV5. My advice would be to use something which is supported, or at least supported by the Kinetis SDK. Otherwise having all the drivers will be a challenge.
About professional services: see http://www.nxp.com/support/nxp-professional-services:PROFESSIONAL-SERVICE
I hope this helps,
Thank you for your quick response.
I need the KV5x for the peripherals – especially the HSADC’s and Ethernet. I’m moving from the DSC 56F84789. I had a meeting with Mark Houston where he really convinced me on the merits of the KV5x series as a replacement for the DSC’s.
I am not sure what you mean when you say that there is no Processor Expert for KV5x. At FTF with the help of Greg Hemstreet I set up my laptop with the KV5x on KDS with an SDK and PEX. As a result there is an SDK built in the vault for SDK_1.3_TWR-KV58F220M on kex.nxp.com. It says that FreeRTOS is an optional component but I can’t find it in the SDK.
So I downloaded the SDK for KV5 from the website. PEX seems to work ok, but I cannot find any beans for FreeRTOS. That’s as far as I got it. I am a newbie to Kinetis and SDK. I was hoping to be able to load a FreeRTOS bean and then bring up some example project and get the SystemViewer and Percepio working. I’d like to see the screens that you showed in your latest MCU on Eclipse blog.
Thanks for your help.
I missed the fact that there is a KV5x available on kex.nxp.com. I’m downloading it right now to see what is included. I believe it should have Processor Expert components in it. In that case, you can use the McuOnEclipse FreeRTOS: https://mcuoneclipse.com/2015/12/05/tutorial-freertos-projects-with-kinetis-sdk-v1-3-and-the-sdk-project-generator/
I am trying the June 25 Component release for the first time, and am have a problem generating code that includes the FreeRTOS component. It seems that it wants to have KSDK, even though my MCU is not supported with the SDK, and I have the KSDK box un-checked in the configuration. Something I’m missing?
Thanks in advance!
LikeLiked by 1 person
Don’t worry, it is not using the SDK if you are not using it. The KinetisSDK component is default in to ‘none’. It is a simple wrapper only. So have it added, and with the setting to ‘none’ you are fine.
The thing is that technically I have to reference that component, even if it is not used.
I hope this helps,
LikeLiked by 1 person