Messages

1

NXP^TM M522XX, KINETIS and i.MX RT / Re: uTasker for i.MX RT series

« on: January 13, 2021, 04:36:48 PM »

Fine thanks.
One question I have about i.MX with external flash is the way to protect the code, I think NXP provides a utility to load the encrypted code by USB, but I always need to load by SD card.

1.- So with uTasker for i.MX I can load encrypted code from SD to QSPI, and it will be encrypted in the QSPI? This would be to use it with the RT1062 and the new RT1070.

2.- If I started my application from SD, do you know if it is possible to have access to the SD from the microcontroller to have my own configuration files? What I would like is to be able to share the SD to have the startup program and at the same time have my files let it read the microcontroller for my application's configuration data.

For the RT1020, RT1024 and RT1064 I suppose that when using internal flash they do not need to encrypt the code.

2

NXP^TM M522XX, KINETIS and i.MX RT / Re: uTasker for i.MX RT series

« on: January 10, 2021, 03:20:58 AM »

 
Ok.
What is the processor type?
If I order for a full license or a project license, I can use it on all i.MX RT Processors?,  that is on RT1020, RT1024 and RT1062. Or do I have to pay a license for each processor?

Can I create as many keys as I want, or just one?
Provides all sources, such as for Kinetis or just binaries. ?

3

NXP^TM M522XX, KINETIS and i.MX RT / Re: uTasker for i.MX RT series

« on: January 09, 2021, 12:52:10 AM »

How can I buy it and what is the price?

4

NXP^TM 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.

Regards.

5

NXP^TM M522XX, KINETIS and i.MX RT / Re: Bootloader by SD card for the RT1020

« on: May 13, 2020, 11:55:19 PM »

Hello Mark.

I don't quite understand the usefulness of that binary.
How to create the encrypted bootloader, configuring the keys that I want, as it was done with the Kinetis?

I would be interested in an encrypted bootloader for SD cards, such as that of the Kinetis, to be able to configure the keys, and in the case of i.Mx RT, also to be able to encrypt the user program that will load in QSPI or SD, so that it cannot be copied or used on other plates without authorization.

Initially I was going to use the RT1020 in LQFP100, but now I prefer to use the RT1062 in BGA (will be my first PCB for BGA), since it is the processor that uses Teensy 4.0 and 4.1, so I can do the developments and tests with Teensy, and when everything works, then create my own board with the RT1062. Does uTasker support or will it also support the RT1062?

Thank you

6

NXP^TM M522XX, KINETIS and i.MX RT / Bootloader for Kinetis and interrupts problem

« on: March 10, 2020, 10:52:05 AM »

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.

7

NXP^TM M522XX, KINETIS and i.MX RT / Re: Bootloader by SD card for the RT1020

« on: March 09, 2020, 03:57:27 PM »

 
Thanks, I look forward to the version for RT1020 that allows the encrypted bootloader from SD to QSPI.

A question about copy protection:
When the bootloader loads the firmware from SD to QSPI, will the firmware in the QSPI be encrypted?

I have not started working on firmware files signed with the RT1020 yet, but I understand that once the program has been compiled, it can be encrypted before recording it to the boot device (SD, QSPI, hyperflash). Then, in the case of your booloader, in addition to the firmware being encrypted in the SD, once it is loaded into the QSPI from the SD, will it also be encrypted in the QSPI?

8

NXP^TM M522XX, KINETIS and i.MX RT / Re: Bootloader by SD card for the RT1020

« on: March 09, 2020, 02:06:37 PM »

 
Thanks Mark.
Is it possible to update the program from the SD card to the QSPI with your bootloader?

The RT series, having no flash memory, already allows a direct boot from SD, but what I would like is for the boot to always be from QSPI and the firmware can be updated with an SD.

The problem is also that the files must be signed to protect against unauthorized copying. Will this be possible with your bootloader?

 

9

NXP^TM M522XX, KINETIS and i.MX RT / Bootloader by SD card for the RT1020

« on: March 07, 2020, 10:56:39 PM »

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

Regards.

10

µTasker general / Re: uTaskerConvert problems

« on: December 31, 2019, 05:05:25 AM »

ok, thanks.

11

µTasker general / Re: uTaskerConvert problems

« on: December 25, 2019, 07:13:53 AM »

Thanks mark.
I have tried to reduce the value of the magic number, to a lower value and now it works.

I read something in the manual that this value should be as low as the minimum value of the program page size, or something like that. I didn't understand exactly what this means, but it worked for me by reducing the value of this parameter.

12

µ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

13

NXP^TM M522XX, KINETIS and i.MX RT / Re: Kinetis MK66, how overclock to 240Mhz

« on: October 12, 2019, 07:43:22 PM »

Thanks mark.

Then the overclock consists of exceeding the 360Mhz of the VCO, to increase it to 480Mhz?, Since then this is divided by two for the working frequency of the core.

In what source code file can I find these checks?

        #if CORE_CLOCK > 180000000
            #error PLL frequency out of range: maximum 180MHz
        #endif

        #if BUS_CLOCK > 60000000
            #error bus clock frequency out of range: maximum 60MHz
        #endif


 

14

NXP^TM 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 ??

Regards

15

ST^TM STM32 and STR91XF / Re: Compile for STM32F746 fail

« on: June 14, 2019, 09:26:45 PM »

5. For SD card operation share the setup with other boards alreadiy using the SD card controller:
    #if defined STM3240G_EVAL || defined ST_MB997A_DISCOVERY || defined STM32F746G_DISCO
        #define SD_CONTROLLER_AVAILABLE                                  // use SDIO rather than SPI (necessary on STM3240G-EVAL board)

For this option, seem I need define also SDCARD_SUPPORT in config.h.
I must to do it here ??

Code: [Select]

#if !defined TWR_K20D50M && !defined FRDM_K20D50M && !defined FRDM_KL46Z && !defined FRDM_KL43Z && !defined TWR_KL46Z48M && !defined FRDM_KL26Z && !defined FRDM_KL27Z && !defined TWR_KL25Z48M && !defined FRDM_KL02Z && !defined FRDM_KL03Z && !defined FRDM_KL05Z && !defined FRDM_KE02Z && !defined FRDM_KE02Z40M && !defined FRDM_KE04Z && !defined TWR_K20D72M && !defined TWR_K21D50M && !defined TWR_K22F120M && !defined TWR_K24F120M && !defined K24FN1M0_120 && !defined FRDM_K22F && !defined TWR_KV10Z32 && !defined TWR_KV31F120M && !defined K66FX1M0 // boards have no SD card socket
  //#define SDCARD_SUPPORT                                               // SD-card interface (only choose one of these options at a time)
  //#define SPI_FLASH_FAT                                                // SPI flash
        #define SIMPLE_FLASH                                             // don't perform block management and wear-levelling
        #define FLASH_FAT_MANAGEMENT_ADDRESS     (SIZE_OF_FLASH)
  //#define DELETE_SDCARD_FILE_AFTER_UPDATE

I must enable only one of the four options ?
Now there are enable two options

Code: [Select]

  //#define SDCARD_SUPPORT                                               // SD-card interface (only choose one of these options at a time)
  //#define SPI_FLASH_FAT                                                // SPI flash
    #define SIMPLE_FLASH                                             // don't perform block management and wear-levelling
    #define FLASH_FAT_MANAGEMENT_ADDRESS     (SIZE_OF_FLASH)