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

Pages: [1]
1
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.

Regards.



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

Regards.


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

4
Thank you Mark, I will try with this and I will report here the results.

Best regards.


5
[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.

6
µTasker general / Re: Last CodeWarrior version using uTasker 1.3v
« on: October 26, 2018, 09:50:18 AM »
I'm so sorry Mark, I just copied a msg tried to be sent before. The email problems refered last line should not be posted. It's solved. The emailing problem was detected in my company email account configuration.

Thank you very much for your quick step guide. I hope it works. I will try to follow your steps.

I agree with you. I 'm also think that one of the solution to avoid future obsolescences is the hardware migration. But it could take more things and work into account: if there is a newest mcu that matches with our current mcu, pinout rerouting pcb, pinout new code configurations and new registers to be writen, peripheral control modifications, functionality testing, etc.. However, I think it will be a point in which this will become the only solution that allows the fw production maintainance, furthermore if Nxp production quit off the micro someday. So It's requires some analysis before, I'm go to start to win some bits of time trying the first quick solution.

Best regards.

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

Pages: [1]