Topics

1

NXP^TM M522XX, KINETIS and i.MX RT / inherited project for freescale MCF52258 with M5223x hardware file

« on: March 07, 2019, 08:49:17 AM »

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.

2

µTasker general / uTaser Code involved with debugging - how must it be?

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

1)compile
2)make
3)Project/debug
4)run

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.

3

µTasker general / Last CodeWarrior version using uTasker 1.3v

« on: October 25, 2018, 03:19:49 PM »

The project in which I'm working is an industrial applicaction project based on based on coldifre (mcf52259) and it's built using uTasker v1.3 with an old codewarrior version (5.9; although when you click in help button you can read: CW DS for CF Arch 7.2) some time ago.

Currently this CW IDE version is installed in a computer within windows XP OS. But debugging has never worked; the IDE hangs. And XP Ws is totally obsolete, as you know, out of official support.

I would like to install a newer CW version in a computer with windows 10, loading the whole application files, creating the project, being able to compile files and make the fw bin files with the minimum code modifications. So, porting the project.

I know that last versions of CW are not supporting uTasker v1.3, so they may be using the v1.4. But I would like to know if here is anyone who knows what is the last CW version compliant with uTasker 1.3v using the same MCU. I don't need the newest CW version, but some version newest than CW5.9 could be fine to check if debugging is possible, also running out of windows XP operating system.

I was trying to find more information about this kind of question and I also was trying to contact someone in uTasker project, but its web seems to be disabled and contact emails too. I don't know if uTasker project is stopped or I was visiting the wrong link.

Any information will be apreciate and it will be helpful.

Best regards.