Recent Posts

Pages: [1] 2 3 ... 10
1
NXPTM M522XX, KINETIS and i.MX RT / Re: i.MX RT 1020 GPIO and Pin Multiplexing
« Last post by mark on February 13, 2019, 03:31:20 AM »
Phil

I don't know just yet. The i.MX RT parts are crossover parts so not overly big and some have a good amount of SRAM and Flash inside and so are real single-chip devices.

The big parts will tend to be used with Linux and there is no real sense in making something for them since it will never be used.

What I like about the i.MX RT parts too (I don't know the others in any detail) is that one has the feeling that they are an extension of the Kinetis parst since a lot is quite similar and various drivers are almost 100% compatible. It feels like a small embedded processor still but has that extra power (and things like dual Ethernet) - and at a price of about $2.70 in 10k quantity rather attractive!

Regards

Mark
2
NXPTM M522XX, KINETIS and i.MX RT / Re: i.MX RT 1020 GPIO and Pin Multiplexing
« Last post by Phil on February 12, 2019, 08:59:43 PM »
Mark,

What is your plan regarding the i.MX series of application MCU's?  E.g. Are you planning to support these chips?  We are considering an i.MX8 for a project we are considering. We enjoy using uTasker and that would like to use uTasker, if the option exists.

Regards,

Phil
3
NXPTM M522XX, KINETIS and i.MX RT / i.MX RT 1020 GPIO and Pin Multiplexing
« Last post by mark on February 10, 2019, 01:47:34 AM »
Hi All

The following video shows the level of compatibility of uTasker projects with the i.MX RT 1020 (300MHz Cortex-M7) by looking a the GPIO and pin multiplexing philosophies and use of port macros: https://youtu.be/SmFTi8hlba0

The pin mux. spread sheet shown there is attached to this post.

The latest version of the document is included in the project folder: \Hardware\iMX\GPIO_PERIPHERALS

Regards

Mark

4
NXPTM M522XX, KINETIS and i.MX RT / Re: strtok
« Last post by mark on February 07, 2019, 01:59:32 PM »
Phil

Yes I would expect this too but it is the only explanation that I have.

From your call stack everything is OK before you enter the strtok() so the best thing to do is to set a break point on this line and then step into it in disassembler mode (maybe you can also find source level debugging capability on the library) - they you need to step until it fails and see what instruction it is or whether it is due to a bad memory access. If you can identify an instruction failing look it up in the Cortex-M0+ instruction set to see whether it exists. If it doesn't but does exist in the M4 set it will be the wrong library.
Note that if it a library target issue it won't normally take a lot of stepping to find it.

Regards

Mark

5
NXPTM M522XX, KINETIS and i.MX RT / Re: strtok
« Last post by Phil on February 06, 2019, 06:33:25 PM »
Thanks, Mark.

I would think that changing the "Target Processor" in the C Build settings would point to the correct standard libraries.

Regards,

Phil
6
NXPTM M522XX, KINETIS and i.MX RT / Re: strtok
« Last post by mark on February 06, 2019, 02:54:00 AM »
Hi Phil

It sounds to me as though you are using a library for a Cortex-M4 on a Cortex-M0+, which will fail due to it using instructions that the Cortex-M0+ doesn't support.

Therefore check which library is being used (for the strtok()) and adjust it (or rebuild it) for the target in question.

Good luck

Regards

Mark
7
NXPTM M522XX, KINETIS and i.MX RT / Re: strtok
« Last post by Phil on February 06, 2019, 12:17:50 AM »
Attached is the debug trail that shows the hard fault originated from the strtok string parse function.
8
NXPTM M522XX, KINETIS and i.MX RT / Re: strtok
« Last post by Phil on February 06, 2019, 12:12:14 AM »
Snipet of code in question:

void fnDoSwitch(unsigned char ucType, char *ptrInput)
{
   char *arg1;
   char buff[64];
   int i = -1;

   uStrcpy(buff,ptrInput);

   arg1 = strtok(buff, " \r");
...
9
NXPTM M522XX, KINETIS and i.MX RT / strtok
« Last post by Phil on February 06, 2019, 12:09:24 AM »
Mark,

Had something happen today that was rather strange.

I was reusing some code developed on a K64 and using this with a KL27. Interestingly, I ran into a bunch of problems related to the handling of strings. Simple things like defining an array of characters predefined to a 0 or using a strtok string function.  I know we had issues with strcpy and these types of functions but are these issues related?

Finest regards,

Phil
10
STTM STM32 and STR91XF / Arduino Blue Pill
« Last post by mark on January 27, 2019, 11:55:40 PM »
Hi All

I have just completed integration of the Arduino Blue Pill - a < $2.00 development board - and published this video showing the uTasker USB-MSD loader used to load a couple of application configurations:
https://youtu.be/dq-m-Dokq7E

Overview of the board and some binaries: http://www.utasker.com/stm32/BluePill.html

Regards

Mark
Pages: [1] 2 3 ... 10