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 - LuisHS

Pages: [1] 2 3


In order to route all the ports of this microcontroller with pitch 0.65mm, is a 4-layer PCB enough or may more layers be needed?

So far I have only used 1mm pitch BGA microcontrollers with the Kinetis MK66, and 0.8mm pitch with the RT1064. With the RT1064 it's already costing me enough to be able to route a good number of ports for a project, and that with a pitch of 0.8mm, and 4 PCB layers.

Working with PCBs with 6 layers or more, and with such small vias for that 0.65mm pitch can already make the PCB quite expensive.

NXPTM M522XX, KINETIS and i.MX RT / Re: RT1064, boot from SD.
« on: March 08, 2023, 05:36:56 PM »

Thanks Mark
And wouldn't it be possible to always boot from SD, without having to copy to flash?

I saw this article from McuonEclipse where they explain how to boot an application from SD, the processor starts the ROM bootloader, then loads the image from the SD card into RAM (ITC) and then runs it. In that configuration no internal or external FLASH memory would be needed.

They also explain that the application is copied from SD to ITC RAM from where it runs, but that this limits the program to a maximum of 64k, which seems very little to me.

In your answer you tell me that in ITC+DTC the size of the program would be 512K, that is much more than the 64k indicated in mcuoneclipse. So this leaves me confused.

To always boot from SD, without copying to Flash, would it always be done using the Rom bootloader that would copy to ITC from where the program would run, and what would be the maximum size of the program that could be run?


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 / Re: uTasker for Kinetis MK64
« on: March 08, 2023, 02:39:19 AM »

Thanks mark.
Regarding the i.MX RT, do you know if I can configure the boot to be done from an SD card?

If so, could I have my encrypted firmware on that SD card? So that the microcontroller can boot my firmware from SD and also have other files of my application stored on that same SD card, such as some configuration file, all using FatFS.

In that case, I suppose that a bootloader would not be necessary, the SD card would already have the boot firmware and it would be enough to copy the SD card or create an SD formatted in FAT32 and copy the boot file with my firmware.

As for the RT1062 and others you refer to, you sell them too, they are 0.8mm pitch??, I have not worked with pitches smaller than 0.8mm because the PCBs would be more expensive and I suppose that the soldering process in oven can also be more delicate.

NXPTM M522XX, KINETIS and i.MX RT / Re: uTasker for Kinetis MK64
« on: March 07, 2023, 03:24:00 AM »

Thanks mark
Do you know where I can order some MK66s ?, sold out at all vendors until 2024.

I have some projects made for MK66 that I will eventually try to migrate to RT1024 or RT1064, but until I can do that conversion I would like to be able to get some MK66 so I can continue to build my boards with MK66. That's why ultimately, I wanted to try to see if these MK64 that I have here can be used as a replacement by overclocking to 168Mhz, I know it's not ideal, but it would be the last option due to the shortage of chips.

On the other hand, I wanted to ask you some questions about the use of the uTasker SD bootloader with the RT1064.

1.- The uTasker binary is encrypted so that it cannot be extracted from the chip in commercial products?.
2.- The user firmware that will load the uTasker bootloader is encrypted with your program as it was done with the MK66 or it must also be encrypted with the NXP system to encrypt binaries.

I find it confusing to work with i.MX since in these the protection against reading and extracting the program is not like with the Kinetis with chip reading protection, but rather encrypting the binary before loading it on the chip, with a key that must be previously write in the chip so that it decrypts the binary at runtime. So now to use uTasker on the RT1064, it sees that there is a conflict in the encryption, on the one hand there is the encryption of the i.MX RT and on the other hand the encryption of uTasker on the binary to be loaded (in my case by SD).

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 / 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.

NXPTM M522XX, KINETIS and i.MX RT / Re: uTasker for i.MX RT series
« on: January 10, 2021, 03:20:58 AM »
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. ?

NXPTM 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?

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 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

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.

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?

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?



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


Pages: [1] 2 3