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

Pages: [1]
1
Mark, I found the issue! 

I overlooked one parameter setting in CWv6.3 that was different from CWv7.2 setting in my project.  Under "[Project] Settings -> Code Generation -> ColdFire Processor", I had under the "Use .sdata/.sbss for:" window the "All data" selected.  Once I selected "All data smaller than 0 bytes"  the linker errors went away.  See attached for the settings that was causing errors.

I don't know if any of this makes sense to you or not.  If yes explanation would be appreciated.

kind regards,
romeo

2
The pre-processor defines that I have are exactly the same.  What I did I made sure that between CW6.3 and CW7.2 I had all of the same settings and using the same files.  And now I get these link errors (see attached).

you mentioned that:
Quote
The boot loader is only about 2k in size so the free version (limited to 128k) should also be OK too.

Are you suggesting that I develop my bootcode with the free version of CW7.2 and keep on developing my custom application code project on CW6.3 since we already have a license for it?  Hmmm I like the idea  ;D

regards,
s2c97

3
I downloaded the CodeWarrior V7.2 free evaluation software and tried compiling the bootloader code.  And everything compiled successfully.  So this proves that I am fighting some differences between CW v6.3 and CW v7.2.  Too bad that Freescale is charging me $500 to upgrade from v6.3 to v7.2.

4
Actually I am trying just to get the bare minimum boot loader code project compiled.  Since I am interested to port the bootloader code to my project.  The main goal is I want to copy uploaded code to the application part.

regards,
s2c97

5
Ok, that's what I thought as well with CW6.3.  CodeWarrior v6.3 seems to be able to handle the back conversion from v7.0 of the project.  But I keep getting the same link errors and I do not know where it comes from (please see attached).




6
NXPTM M522XX, KINETIS and i.MX RT / CodeWarrior V6.3 with utasker1.4
« on: April 15, 2010, 07:49:36 PM »
First and foremost I did search in the forum for this kind of topic and could not find any similar information.  So if I overlooked please feed me to the right link.

Question 1:  
Will I encounter any issues if I try to compile code of the latest uTaskerV1.4_M5223X with the CodeWarrior v6.3 Build 14 version?

Question 2:
If yes is there any workaround?  Or I will have to upgrade to CodeWarrior v7.0 in order to compile successfully?

The reason for these questions is because I've been encountering link errors that I will address in another post depending on the answers I will receive for the above.

kind regards,
s2c97

7
@aersek
This is really encouraging news to hear from a user that actually ported utasker to the MCF5282.  I really appreciate that you shared your experience and would love to see your base reference code of your version of utasker for the 5282.

I was a little bit concerned with the internal memory flash since it is superFlash technology but discovered (like you mentioned) that it can have a single erase page of 2k which is comparable granularity as the other supported devices.  I'm not to concerned about not being able to do DMA on UART since I will be using it differently.

So I am more confident now to go ahead and invest some time in utasker to port the code to our project and 5282 processor.

kind regards,
s2c97

8
Hi,

I'm in the middle of developing embedded software on the Freescale MCF5282 on our new product and I'm evaluating the option of porting utasker to our target processor.  I'm very interested at the utasker bootloader in particular.

I was wondering if any of you has already done a similar task (on the 5282 or other processors) and if he could kindly share some of his experiences and any technical pointers.

kind regards,
s2c97

9
utFAT / Re: CF card support
« on: April 01, 2010, 10:01:16 PM »
Hi,

like jezc mentionned it would be interesting to hear from aersek (and others) about some pointers on porting utasker over to the MCF5282.

I am going to start a new discussion under "utasker general" regarding porting utasker to non supported processors like the MCF5282 and see if I could get some other members to share their technical experiences.

kind regards,
s2c97

Pages: [1]