Messages

16

NXP^TM M522XX, KINETIS and i.MX RT / Re: IAR ColdFire support

« on: March 28, 2011, 08:04:19 PM »

Thanks Mark - must have skipped that one by mistake...

I'll get it & give it a go.

Sorry to have troubled you

Cheers,
    Jez

17

NXP^TM M522XX, KINETIS and i.MX RT / IAR ColdFire support

« on: March 28, 2011, 12:45:12 PM »

Hi Mark,

A while ago, you mentioned that you were considering looking into adding IAR support for the ColdFire projects - have you got any further with this?

I'm getting close to the point where I'll have to choose whether to tackle a new project in CodeWarrior 10.1 or IAR.

Initially I'm likely to have to do some work on the ColdFire project but we do have a longer-term interest in migrating this to Kinetis, so I could use either tool-chain (we curently use IAR for ColdFire & ARM targets) but am still not very comfortable with Eclipse.

Just after an update if possible.

Cheers,
    Jez

18

NXP^TM M522XX, KINETIS and i.MX RT / Re: KINETIS development environments

« on: February 18, 2011, 12:33:21 PM »

Hi Mark,

I've been notified that IAR have issued a warning that it's possible to permanently lock up the Kinetis k60!

Basically if the default linker file from IAR is used & the code reaches adress 0x40C, the NVFSEC register, it's possible to set the mass erase & flash security bits & permanently & irreversably lock the device.

There's a full description of the possible issue & how to avoid it on the IAR support pages (note 77989).

Hope no-one falls foul of this one!

Cheers,
   Jez

19

NXP^TM M522XX, KINETIS and i.MX RT / Re: M52259 TOWER - TFT display and Temperature/humidity sensor

« on: February 02, 2011, 11:13:16 AM »

Hi Martin,

Thanks for the information/confirmation - I'll check with some of my colleagues if they have a similar problem with their native Visual Studio projects (though they're mostly using C# nowadays).

I'll also see if they can try the project with a 'full' version of Visual Studio (rather than express), just in case that's a factor too.

I'll let you know if I find anything more about this.

Cheers,
    Jez

20

NXP^TM M522XX, KINETIS and i.MX RT / Re: M52259 TOWER - TFT display and Temperature/humidity sensor

« on: February 02, 2011, 08:41:42 AM »

Hi Mark,

Yes, doing the clean first has done the trick as you expected! I'd tried a rebuild all with no success, will have to make a note to do a clean every time I change a macro definition, just to be safe!

Thanks again for the excellent support!

Cheers,
    Jez

21

NXP^TM M522XX, KINETIS and i.MX RT / Re: M52259 TOWER - TFT display and Temperature/humidity sensor

« on: February 01, 2011, 02:05:39 PM »

Hi Mark,

I've just tried to build the simulator version without the GLCD support (commented out '#define SUPPORT_GLCD' in config.h) & it's failing to build -

1>Linking...
1>LCDSim.obj : error LNK2019: unresolved external symbol _fnPenMoved referenced in function "int __cdecl fnPenDown(int,int,int)" (?fnPenDown@@YAHHHH@Z)
1>LCDSim.obj : error LNK2019: unresolved external symbol _fnPenPressed referenced in function "int __cdecl fnPenDown(int,int,int)" (?fnPenDown@@YAHHHH@Z)
1>LCDSim.obj : error LNK2019: unresolved external symbol _fnPenLifted referenced in function "int __cdecl fnPenDown(int,int,int)" (?fnPenDown@@YAHHHH@Z)
1>.\Debug/uTaskerV1-4.exe : fatal error LNK1120: 3 unresolved externals

Not a huge problem at present (while I'm running development code on the simulator), but I haven't got the LCD for the tower yet and I think you said it would hang if it's built into the code but not fitted?

Cheers,
    Jez

22

NXP^TM M522XX, KINETIS and i.MX RT / Re: KINETIS development environments

« on: February 01, 2011, 01:47:36 PM »

Hi Mark,

Great - no huge rush for this but it'd be nice (for me at least) to stay with the more familiar IDE etc (and another excuse to avoid Eclipse for a while longer... )

If you want any sanity-checks running on the IAR side, just drop me an e-mail.

I'm still struggling to get the older CW versions running on Win7 Pro x64 (or at least the debugger connection) so the IAR route might be another way to move development onto the newer PC. I'd love to move the newer projects to Kinetis, just need some non-BGA device packages for k60 etc

Cheers,
    Jez

23

NXP^TM M522XX, KINETIS and i.MX RT / Re: KINETIS development environments

« on: February 01, 2011, 11:13:24 AM »

Hi Mark,

My main push will be with IAR v6 (because I already have it & am getting used to it) but I might also continue the struggle with CodeWarrior in the future (there are a few possible projects where the free MQX support in both of these will help me where I can't currently use uTasker).

The CodeWarrior route will probably be useful for people migrating from the other Freescale products (e.g. ColdFire) - I'd use IAR for the ColdFire as well if uTasker supported it!

HTH

Cheers,
    Jez

24

µTasker general / Re: Kinetis support

« on: January 26, 2011, 10:40:51 PM »

Hi Mark,

That's no problem - I'm aware of the differences in the core etc, I'm just keen to get a more powerful (and capable) micro for some future work.

I'll register for that project package for home use and evaluate it - I'm hoping it'll overcome some of the problems I'm having with both existing ColdFire & NXP LPC processors...

Thanks,
    Jez

25

µTasker general / Kinetis support

« on: January 25, 2011, 11:17:20 AM »

Hi Mark,

I've just seen your initial info regarding the support for Kinetis - I've got a K60 tower kit ready & waiting.

Will this be a new project type?

Looking forward to hopefully trying it soon!

Cheers,
    Jez

26

NXP^TM M522XX, KINETIS and i.MX RT / Re: CodeWarrior and Windows 7

« on: January 22, 2011, 09:13:12 PM »

Hi Mark,

I've managed to get CW 7.2 installed onto my Win7 64bit PC in the end (following the advice on the forum as you suggested - thanks!) - it's now building the 52259 Tower demo ok.

Now I need to work out how to get the debug connection to work...in the meantime I guess I'll have to go back to an old XP machine and get the real work done!

Thanks.
    Jez

27

NXP^TM M522XX, KINETIS and i.MX RT / Re: CodeWarrior and Windows 7

« on: January 14, 2011, 09:35:40 PM »

Hi Mark,

Just to update you, I can't get CW7.2 SE to even install on my PC with Windows 7 Professional 64bit...so I'll have to wait for your CW10.1 conversion by the look of things 

I'll have to try installing it on an older PC (again) in the meantime.

Thanks anyway.

Jez

28

NXP^TM M522XX, KINETIS and i.MX RT / Re: CodeWarrior and Windows 7

« on: January 13, 2011, 03:48:17 PM »

Hi Mark,

Do you know if this workaround will work even on 64bit versions of Windows 7?

I'm trying to get things going on Win7 Pro (64 bit) and would like to avoid having to go to CW10 if I can (converting project files/re-building/re-testing & generally fighting with Eclipse etc).

Also, do you currently have any plans to move to newer versions of CW (I'm thinking particularly about the Kinetis parts - glances at the K60 Tower on top of the PC) or will you support these under IAR (being based on the Cortex-M4)?

Cheers,
    Jez

29

NXP^TM M522XX, KINETIS and i.MX RT / Re: M52259 TOWER - TFT display and Temperature/humidity sensor

« on: November 30, 2010, 11:18:28 AM »

Hi Mark,

I've got the MCF52259 Tower kit (no LCD etc - yet!).

Is there support for the Tower in the latest files or will a new SP be required?

I'm trying to get something running between the Tower & the MCF52259 DEMO board...so support for the Tower (with/without other peripherals) would really help!

Cheers,
    Jez

30

µTasker general / Re: IAR EWARM v6.10

« on: November 11, 2010, 11:15:49 PM »

Hi Mark,

I don't think it's such a big change as from v4 to v5 - the later v5 releases (5.506 for example) seem to have the many of the same features (though I mat have missed some of the subtler ones).

There's a bit more to the M4 than M3 + FPU (which is optional - the early Kinetis parts won't have the FPU - probably due very late 2011) - DSP-like instructions (barrel shifter, single cycle 32 bit multiply etc) and lots of subtle improvements to really boost the processing capabilities.

The NXP parts (LPC18xx will be M3-based, the LPC43xx M4-based) are going to offer pin-compatible versions & 43xx will include the FPU from the outset - there are also some very nice peripherals going in there (SPIFI to allow serial Flash to hold code but appear as linear memory, some very nice serial peripherals too and I think there's going to be USB2 high speed support with on-chip PHY too).

NXP peripherals are usually kept compatible, so the effort for the M4 over the M3 might be pretty small.

I'll check up on when the dev kits will be available (Freescale should have the k40 & k60 any day) & get back to you.

We're trying the LPC 1788 in place of the 2478 at the moment - will let you know how we get on with that as well.

Cheers,
    Jez