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.

Topics - LuisHS

Pages: [1]
NXPTM M522XX, KINETIS and i.MX RT / RT1064, boot from SD.
« on: March 08, 2023, 03:22:50 AM »

Hello Mark.
I was watching your video to run the program in ITC memory, and I have some doubts.

If I want my application to boot from an SD card, is it essential that it be loaded and run in ITC?
What maximum size can my application have to boot from SD, is that limit the ITC memory size?

Can't configure my app to boot from SD card to run on SDRAM? it's much bigger, and wouldn't limit the size of my program that much.

NXPTM M522XX, KINETIS and i.MX RT / uTasker for Kinetis MK64
« on: March 06, 2023, 06:05:30 AM »
Hi Mark.
I can't find Kinetis MK66s anywhere, sold out at all vendors, but I do have a few MK64s.

My question is can I load the uTasker SD boorloader for MK66 on a MK64 without recompiling the program? My question is what is the uTasker bootloader clock frequency for a MK66, since the MK64 is slower, at 120Mhz, while the MK66 can go to 180Mhz. I use the SD card bootloader for the MK66.

At what frequency is the uTasker clock set for the MK66? I seem to have read somewhere that it was set to 120Mhz, in that case the binary that I compiled a long time ago for the MK66 I suppose would be useful for the MK64 without the need make changes and recompile.

I have made the firmware of my program (to load with uTasker SD bootloader) for the MK66 in MCUXpresso and I suppose that changing the PLL configuration so that it goes to x42 instead of x45 and in this way the clock works at 168Mhz would already work for the MK64. Although the MK64 is for 120Mhz, in Teensy 3.5 you can reclock it to 168Mhz, which is what I would also do in MCUXpresso to be able to use it with the MK64.

NXPTM M522XX, KINETIS and i.MX RT / uTasker for i.MX RT series
« on: January 08, 2021, 05:48:35 PM »

Hi Mark.
Where can I download the uTasker SD bootloader for i.MX RT1062?

I checked your Github and I don't see any option for MCUXpresso i.MX
I would like to test it with RT1020, RT1024 and RT1062.


Hello Mark.

I have a problem using the bootloader by SD card. My program works perfectly if I burn it directly to the microcontroller, a Kinetis MK66, using a Jlink.

But if I load it using the bootloader, the start of the program, that turns on/off several LEDs of a LED matrix works perfectly, so I know that the program has been loaded and is running. But what runs next in the program does not work, several GPIOs activated by interrupts must be read.

Is there anything to consider using the uTasker SD bootloader, if the program to be loaded uses interrupts?.  I tried to compile my program generating Debug and Release versions, with optimization disabled, program start address always 0x8000.


Hi Mark.
Is there a uTasker that works as a bootloader by SD card for the RT1020?


µTasker general / uTaskerConvert problems
« on: December 23, 2019, 10:53:53 AM »
Hello Mark.

I am trying to use uTaskerConvert for a new project and I have problems. The resulting file is not loaded by the bootloader.

All codes are correct, the only thing I notice is that if I encrypt a small-sized program it is when do not load it, for example, 26K once encrypted, however, another program with 75K size does load it. Both encrypted with uTaskerConvert with the same codes.

I know it's because of the size because if I edit the source that loads ok, and reduce it to keep only the main() function empty, to create a small program, the bootloader no longer loads it after converting it with uTaskerConvert.

The parameterization that I use with uTaskerConvert is the one indicated in the manual:

uTaskerConvert uTasker_demo uTasker_update.bin -0x1234 –A748b6531124 –ab627735ad192b3561524512 -17cc - f109

My codes are other, but with the same format and length of fields. Some time ago I had a similar problem and it was because I had defined the first field as -1234 instead of -0x1234, but now it's fine and I'm still having problems.

Why can it be failing me, and only with small programs?

Best Regards

NXPTM M522XX, KINETIS and i.MX RT / Kinetis MK66, how overclock to 240Mhz
« on: October 12, 2019, 06:37:48 AM »

Hello Mark.

I want to apply overclock to a Kinetis MK66, to run at 240Mhz, I know it is possible because with the Teensy 3.6 I can apply an overclock at 192, 216 and 240Mhz, using the same microcontroller.
But I prefer to work with MCUXpresso, the problem is that I don't know how to configure it here, I have tried several combinations of the PLL but it always gives me error. The only sure  is that the maximum frequency of the VCO is 360Mhz according with the datasheet.

Can you help me to apply overclock at 240Mhz with a Kinetis MK66 using MCUXpresso ??


STTM STM32 and STR91XF / Compile for STM32F746 fail
« on: June 08, 2019, 02:31:19 PM »
Hello Mark.

I have run STM32F746 version with Coocox, but when I compile, fail with one error.
How can I solve please ?

Attached capture screen with the error.
\Applications\uTaskerV1.4/debug.c:2778: undefined reference to `fnUpTime'
collect2.exe: error: ld returned 1 exit status

How can I configure for bootloader with SD card and STM32F746 ?

Best Regards

STTM STM32 and STR91XF / STM32F405/407VGT6 Bootloader Configuration
« on: October 02, 2017, 10:43:00 PM »

After the success with uTasker SD Bootloader for Kinetis, I tried to do the same for STM32, I have some questions please:
1.- Not available to use the project in Eclipse ?, I have opened it with Coocox, but I prefer Eclipse if possible.

2.- I want to use for an STM32F405 or STM32F407 with bootloader from SD card by SDIO. It's correct if I choose ST_MB997A_DISCOVERY ?, The SD will not be for SPI, but for SDIO, I'm not sure how select it.

3.- What is the parameter I must configure to enable bootloader from SD card ?. need force boot and not retain loader to enter in boot mode without switches and SD socket with no sd card switch detect.

4.- In config.h I have enable  SDCARD_SUPPORT, but when I go to app_hw_stm32.h  the  "#if defined SDCARD_SUPPORT" is dissabled. What may be the problem ?.

5.- With this bootloader for STM32, the user application must compile also to start in 0x8000 or what is the correct start address for STM32 ?.

6.- There is no "#define DELETE_SDCARD_FILE_AFTER_UPDATE" to allow delete firmware automatically after load ?.
Best regards.

Pages: [1]