16
µTasker general / Re: uTaskerConvert problems
« on: December 31, 2019, 05:05:25 AM »ok, thanks.
News:
Nov 2020: uTasker i.MX RT V1.4.12 is productive - with complete secure loading concept.
Follow uTasker updates at www.twitter.com/uTasker !!
Online Forum registration has now been disabled. Please send an email to an address at the bottom of the home page with your preferred user name and email address if you would like an account.
Return to uTasker main site: www.utasker.com
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.
17
µ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.
18
µ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
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
19
NXPTM 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
20
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 ??
Regards
21
STTM 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)
22
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 13, 2019, 11:21:12 PM »I have add manually the app_hw_stm32.h file to the project, but though I have enable the define STM32F746G_DISCO, when I go to the app_hw_stm32.h, all the instructions for STM32F746G_DISCO are disabled.
I have closed and reopened the project, but they are always disabled.
23
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 13, 2019, 10:54:07 PM »
Yes, I saw, thanks.
I have replace _KINETIS by _STM32 and enable the define for the STM32F746G_DISCO, but there is none app_hw_stm32.h file to add the rest of parameters that you said in before post.
I have replace _KINETIS by _STM32 and enable the define for the STM32F746G_DISCO, but there is none app_hw_stm32.h file to add the rest of parameters that you said in before post.
24
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 13, 2019, 10:34:06 PM »ok, thanks.
I have replace _KINETIS by _STM32 and enable the define for the STM32F746, but there is none app_hw_stm32.h file to add the rest of parameters that you said in before post.
25
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 12, 2019, 12:07:24 AM »Ok, thank you Marc.
Are you planning to add NXP RT1020?
26
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 11, 2019, 02:04:47 AM »Now I have open the uTaskerV1.4.3_STM32, and this compile but there is nothing for the F746
27
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 11, 2019, 01:58:28 AM »Hi
Are you using the open source version on GITHUB or the professional version?
Regards
Mark
I do not understand what do you mean, I work with the sources STM32_uTaskerV1.4.9_pre_20.12.2016
Only the uTaskerV1.4 compile, but Im not sure if this is for STM32F746 bootloader by SD
28
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 11, 2019, 01:44:31 AM »
Hello Mark, thanks for your reply.
Im confused, several versions, but most fail when I try to compile.
What version I must use for a Bootloader by SD, with the STM32F746 ?
I have open the STM32_uTaskerV1.4.9_pre_20.12.2016. I load the three Applications and I compile.
uTaskerboot --------> fail (debug.c:2778: undefined reference to `fnUpTime')
uTaskerSerialBoot --> fail (debug.c:2778: undefined reference to `fnUpTime')
uTaskerV1.4 --> This compile.
What of the three I must use for a Bootloader by SD for a STM32F746 ?
Im confused, several versions, but most fail when I try to compile.
What version I must use for a Bootloader by SD, with the STM32F746 ?
I have open the STM32_uTaskerV1.4.9_pre_20.12.2016. I load the three Applications and I compile.
uTaskerboot --------> fail (debug.c:2778: undefined reference to `fnUpTime')
uTaskerSerialBoot --> fail (debug.c:2778: undefined reference to `fnUpTime')
uTaskerV1.4 --> This compile.
What of the three I must use for a Bootloader by SD for a STM32F746 ?
29
STTM STM32 and STR91XF / Re: Compile for STM32F746 fail
« on: June 08, 2019, 02:54:43 PM »I have open and compile de uTaskerSerialBoot, this do not fail when compile, but in config.h is not the F746 available.
How can I configure uTasker to work with SD bootloader with STM32F746 ?
Thanks.
30
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