Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ssinfod

Pages: [1]
It all makes sense to me now..


OK, it's getting more clear to me but I got a few more questions while we are on that subject.

Q1) Is it exact to say that there are actually 3 bootloaders available ?
 *mbed bootloader (default with the board)
 *P&E bootloader (.SDA) file
 *uTasker bootloader (uTaskerSerialBoot_FRDM-K64F_KBOOT_HID_UART_MSD_SDHC.bin).  (a.k.a uTasker Serial Loader)

Q2) If I program the "uTaskerSerialBoot_FRDM-K64F_KBOOT_HID_UART_MSD_SDHC.bin" file to the FRDM-K64F with the mbed bootloader then do I loose the current mbed bootloader ?
(Is it overwritten?)
Otherwise, is there any co-habitation between the mbed and the utasker bootloader ?

Q3) Can I use the KDS flash utility with uTasker Serial loader or do I need to change the bootloader to the P&E bootloader (.SDA) while doing development in KDS ?

Q4) What happens if I use KDS to program a .S19 generated by the uTasker project while having the uTasker serial loader present in the FRDM-K64F.
 Do I loose the uTasker bootloader ?
 Where is the uTasker bootloader located in memory ?

For now, I suppose the uTasker bootloader is not erased because the uTasker project settings does not erase and write to the specific zone of memory where the uTasker bootloader is located. Right ?

If this is true, then it should be possible to send the .S19 with the serial bootloader (when in the field) or with the KDS Flash Utility (while doing development).

Q5) At some point my goal is to have a robust bootloader that I can use in the field for remote update. (Over Serial or Ethernet)

I suppose that the mbed bootloader or the P&E bootloader are more lab's development tools that actual 'in the field' bootloader.
Therefore, I'm leaning toward replacing the mbed bootloader by the utasker bootloader as quickly as possible. (So I will be closer to my final 'in the field' configuration)

Do you consider that the utasker bootloader (for Kinetis) is reliable enough to be used in the field for remote / in the field update ?

Thanks for patience,


I have a Freescale FRDM-K64F board and I have a simple question.
By default, the dev kit came with the mbed bootloader.

Now, I want to program the BIN file from here:

Here are my questions:
Q1) Can you use the KDS (Kinetis Design Studio) with the integrated OpenSDA to burn this software ?

Q2) Otherwise do I have to buy a JTAG programmer to change the bootloader in the FDRM-K64F ?
Example P&E Universal Multilink :

Q3) What is the recommended reader/writer (programmer) software for the Freescale Kinetis ?
Is there any tool (similar to CFFlasher of the Coldifre ) but for the Kinetis ?


STTM STM32 and STR91XF / STM32F746G-DISCO configuration
« on: November 14, 2016, 06:39:08 PM »

I downloaded and extracted the file "".

The utasker STM32 webpage says that there is 'out of the box' support for the "STM32F746G-DISCO" board.

However, I don't see any "STM32F746G_port.h" in the "\uTaskerV1.4.3_STM32\Hardware\STM32" folder.

Is the support files of this board only available in the commercial version of uTasker STM32 ?

Also, I would like to know what is the general status of utasker for the STM32.
Indeed, the last release (1.4.3) has been made on 2014-05-24. (which is more than 2 years old)
Is there active development of the STM32 branch of uTasker ?
Is it recommended for new development (new project) ?

On a similar subject, recently Qualcomm did purchase Freescale/NXP.
Does it have any impact on the uTasker RTOS developement ?

What is the general status of uTasker ?
Is it planned to be supported for another few years ? (Should I consider Freertos instead of uTasker ?)

Thanks for your time,


NXPTM M522XX, KINETIS and i.MX RT / Re: TICK_RESOLUTION explanation.
« on: April 27, 2016, 10:20:09 PM »

I still don't understand where you get the 70000 ms in the comment.
Is it by dividing:  2^32 / 60000000 = 4294967296 / 60000000 = 71.58  seconds
Does it mean that we could use as a valid value: #define TICK_RESOLUTION 70000 ?

Finally, is there a relation between TICK_RESOLUTION and uTaskerMonoTimer ?
Let say that I set TICK_RESOLUTION to 10. Is there a maximum value for the uTaskerMonoTimer DELAY_LIMIT parameter ?

Thanks again,

« on: April 27, 2016, 01:55:04 AM »

I'm using uTasker on the Coldfire M52233.
I have a question regarding this line from config.h:
  #define TICK_RESOLUTION 50

What are the "correct" values of this define ?
I'm planning to set TICK_RESOLUTION to 10 on the Coldfire M52233 with a 60 MHz clock.
Is there any problem to do this ? Would it also work if I set it to 1 ?

I see a comment on the same line but I don't fully understand its meaning and how it was calculated...
  // 50 ms system time period - max possible with M5223X at 60MHz (with prescaler) PIT would be about 70s!

Any explanations would be great.


NXPTM M522XX, KINETIS and i.MX RT / Re: M522XX V2 Project Code
« on: March 07, 2016, 08:22:22 PM »

I'm trying to build and run "" on the M52233DEMO board. I'm using CodeWarrior 10.5 Special Edition.

I have 3 questions:

Here is what I have done so far but I have compilations errors:

1) Downloaded "" and unzipped it to "C:\Users\phd\workspace\uTaskerV1-4"
2) Then, I Imported the project in CodeWarrior 10.5. I selected the folder "C:\Users\phd\workspace\uTaskerV1-4" for the importation.
Note: In the importation I have the following warning. (See attached picture: "CW10.5_Warning.png")
References to the ${workspace_loc:{<resource>} macro were found in the project settings. Using this macro could cause unexpected errors when the resource is not open or available in the workspace. Using the ${ProjDirPath} macro is preferable. ...

3) Then I perform a "Build All" and I have 80 errors related to "GLCD.c" in "/uTaskerV1-4/uTasker/uGLCDLIB"

What is wrong with GLCD ? (I mean this is the out of the box configuration ?)

I also see the following folder "C:\Users\phd\workspace\uTaskerV1-4\Applications\uTaskerV1.4\M522XXCodeWarrior_CW10"
Do you have to import from this folder instead of "C:\Users\phd\workspace\uTaskerV1-4\" ?
What do I have to do with ".lcf" file in this folder "C:\Users\phd\workspace\uTaskerV1-4\Applications\uTaskerV1.4\M522XXCodeWarrior_CW10\Project_Settings" ?

I also want to build this project for the M52233DEMO board.
What do I have to change to build the project for the M52233DEMO ?
This is what I tried:
1) "Project Properties", "C/C++ Build", "Settings", "Coldfire CPU", and set "Processor Family (-proc)" to 52233 ?
2) Also I verified the define in "Applications/uTaskerV1.4/config.h". (around line 112)
        //#define M52235EVB                                                // EVB Board for M52235
        #define M52233DEMO                                               // DEMO Board for M52233

Do you have to change something else ?
What target should I use for the build ?  (My choices are: MCF52259_Internal_RAM, MCF52259_Internal_Flash, MCF522XX_Boot_Flash, SerialBoot)

It seems the uTasker project doesn't have the EWL library.
I would like to add it to the project so I have the C standard library with stdio.h (printf, scanf) and also stdint.h, stdbool.h and math.h (ex: cos/sin).

Can you tell me what to change to enable the EWL library in CodeWarrior 10.5 ?

Thanks for your time,

Pages: [1]