topic Re: GDI in MQX Software Solutions

GDI

Orzor — Fri, 15 May 2009 19:30:53 GMT

Hi everybody,

I'm french student and I have a big problem.

I have a M52259DEMOKIT and CodeWarrior say me when I run : "Colfire GDI Protocol Adapter : can't connect".

The ethernet module don't function now.

I don't understand. Help me please.

Kind Regards.

Re: GDI

mjbcswitzerland — Sat, 16 May 2009 20:05:37 GMT

Make sure that you select the OSBDM as debugger when using the M52259DEMO (rather than the PEMICRO_USB).

The following documents may help you too:

http://www.utasker.com/docs/M5223X/uTaskerV1.3_Kirin3_demo.PDF

http://www.utasker.com/docs/M5223X/uTaskerV1.3-Tutorial-M5225X.PDF

Regards

Mark

www.uTasker.com

Re: GDI

Orzor — Mon, 18 May 2009 17:00:57 GMT

Thank Mark,

but I want use a free compiler. I use your solution in few days.

My problem isn't the same. When build the application for exemple HVAC, these are no problem. But when I run this application, these aren't connexion with my PC. The LED next to the Ethernet module flashes.

It's crazy because the initialization is good and my IP is 169.254.3.4 / Mask : 255.255.0.0

I don't know how do.

Kind Regards.

Re: GDI

mjbcswitzerland — Mon, 18 May 2009 17:33:12 GMT

CodeWorrior Special edition is free for use up to 128k code size. You can also use GCC (eg. CodeSourcery Coldfire), which is then unlimited.

If the LAN LED is blinking it means that the PHY has not been initialised.

Have you correctly loaded the program to FLASH? From CodeWarrior you need to use "tools" and delete and existing proigram and then program the new one. Is is not adequate to just connect the debugger since this will not load any code.

Regards

Mark

Re: GDI

Orzor — Tue, 19 May 2009 15:31:32 GMT

Yes Mark, I build the program and I do as Quick Start Guide.

And CodeWarrior say "Coldfire GDI Protocol Adapter : can't connect".

I download CodeSourcery : http://www.codesourcery.com/sgpp/lite/coldfire/portal/release616

The installation program was correct, the PATH has were changed. But I don't know if CodeWarrior uses this compiler. I don't think because CodeWarrior says the same thing.

If you have an idea, thanks.

Re: GDI

Orzor — Fri, 05 Jun 2009 17:01:45 GMT

HI!

In fact, the GDI is the link beetween the debugger and the module.

The memory of my module wasn't good organized. I didn't understand the tools for flashed programmer.

I haven't solution of my problem, I restart my program and my project.

Re: GDI

vier_kuifjes — Fri, 19 Jun 2009 13:33:08 GMT

Hello Orzor,

I am currently experiencing the same problem as you do (see message http://forums.freescale.com/freescale/board/message?board.id=CWCFCOMM&thread.id=2937)

It started when I updated Codewarrior to version 7.1.2, it worked fine with the previous version of Codewarrior (7.1.1a).

I hope Freescale will have an answer to this problem soon.

Re: GDI

nibble — Fri, 19 Jun 2009 15:31:05 GMT

Hi Mark,

same problem here.

I had to revert back to the 7.1.1 patch to get the debugger working again.

regards

nibble

Re: GDI

vier_kuifjes — Fri, 19 Jun 2009 15:35:53 GMT

Hello Nibble,

I think it may well work using the old DLLs, see my other post mentioned above.

Re: GDI

nibble — Fri, 19 Jun 2009 16:07:23 GMT

Hi Marc,

Yes, using the old dll seems to solve the GDI problem.

I've just done a quick test using the HVAC demo project on a M522259DEMO board and, this time, CW 7.1.2 worked flawlessy (just like in 7.1.1).

Having the development environment in a virtual machine helped a lot in this kind of test (do a snapshop before you upgrade, upgrade, test and if something is broken, just rollback to previous state).

Thanks for the tip, regards

nibble