Recent Posts

Pages: 1 2 [3] 4 5 ... 10
NXPTM M522XX, KINETIS and i.MX RT / Getting Started With a Custom PCB
« Last post by MU on March 14, 2019, 11:34:59 PM »
Hello, I'm new to uTasker and am working with a custom PCB which already has working application code using FreeRTOS. The main goal right now is to get the uTasker Serial Loader working in USB host mode so that field upgrades can be done with a thumb drive. The processor being used is the Kinetis MK20DN512.

I've been reading the Serial Loader User's Guide and forum posts, but could still use some help getting started.

1.) The MK20DN512 processor does not have it's own eval board. When you download the NXP SDK, they point you to the twrk60d100m as the closest option. Should I select this eval board in config.h? If so do I then simply modify the following code to use the correct processor (and change other settings as necessary), or is there a better approach?

2.) Apart from config.h and app_hw_kinetis.h are there any files in the serial loader which will need modified?

3.) Any other tips?


Originally there was the M5223x but not M5225x, which explains the name of the HW file.
When the M5225x came along the same file was used for it (with new options), rather than adding a new one or renaming it.


µTasker general / Re: uTaser Code involved with debugging - how must it be?
« Last post by Genisuvi on March 07, 2019, 11:55:37 AM »
I could fix it. I try to explain here what was happening and the solution:

In one hand I was confused by the fact that we were compiling M5223x.c file for M52258 mcu. By other hand my error images was suggesting me some kind of connector problems. So I was affraid of missing some #define or flag, etc. But googling I found a post about users with the same problem and how fixed it on provider forum: dll problems with Testcfz unity of codewarriors after updating the multilink fw. I assumed that provider fixed it.
So, my suspicions  were focused on multilink device. I went to the PE page and look for current plugins, packages and driver updates. I installed the last package and we finally could debug perfectly!

I hope it could help to other people who face the same situation.


I can answering myself.

I have just found that M5223x supports M5225x subfamily too.
It seems to be another hardware file app_hw_m5223x.h that defines M5225x.
Now, I understand yet.


As I said in other post I have inherited a uTasker 1.3 based project for M52258 coldifre V2 MCU.
Currently the board is programmed with the fw generated by this project and execution seems to be working as expected for years. But looking at the file project organization I have some doubts.
I have no documentation about some decissions. I hope someone can bring me some light to my darkness and clarify if it is all correct and why doing on that way. I share an image:

Linker command files has M5225x Icf extensions file whereas Hardware files compile the M5223X.c file. 
I would like to know if there could be some reason for that. Does it mean that this file is compliant with M522XX device family?

Thanks in advance.
µTasker general / Re: uTaser Code involved with debugging - how must it be?
« Last post by Genisuvi on March 06, 2019, 09:13:01 AM »
Thank you Mark, I will try with this and I will report here the results.

Best regards.

µTasker general / Re: uTaser Code involved with debugging - how must it be?
« Last post by mark on March 06, 2019, 03:45:13 AM »

There is nothing special to be set in the project for debugging.
However, you may be having difficulties with the debugger if the watchdog is enabled - try disabling the watchdog and beware that the M5225x need a power cycle after disabling its setting before it will really disable it.


µTasker general / uTaser Code involved with debugging - how must it be?
« Last post by Genisuvi on March 04, 2019, 05:02:11 PM »
[img][img]I have an old project based on uTasker 1.3 running on MCF52258 uC. We have a legacy code warrior IDE (5.9.0) for coldfire arch. on W7 PC. After compiling we are unable to debug correctly using multilink programmer device (USB). After loading the file and running the application debug, debug seems to be hung after going to the start point. We can' t start the execution thread. Thread doesn' t stop at any breakpoints when application is doing things that means executing some instructions with active breakpoints. So we have the following messages when trying to go to step over, etc.. or next instruction: 1, 2, 3, 4 picture.

The sequence for debugging I have followed:


There could be a lot of causes for this, but I would like to know if our uTasker code is well configurated for debugging and discart uTasker fault. How must be configured a project for debugging? Which uTasker files are involved? what are the variables or elements to be modified for debugging? Which values? I have seen a file called debug.c. Is there the code for debug configuration?

Thank you in advance.
LCD Graphics Library and Simulator / Re: Graphics library and VNC server support
« Last post by mhoneywill on February 27, 2019, 12:24:29 PM »
FYI was just re-reading this topic and realised old source was long gone but look here

Source on Git hub
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 »

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!


Pages: 1 2 [3] 4 5 ... 10