topic Re: Debug with Demo Board over Win 7 x64 in 8-bit Microcontrollers

Debug with Demo Board over Win 7 x64

sebasira — Wed, 22 Sep 2010 09:23:06 GMT

Hello everybody... after reading a lot of threads and following peg's advises, I decided to run CW 6.1 on a win 7 64-bits PC, using a DEMO JM Board to debug other MCU rather than JM, in this case is a QE

Well, as you may know CW 6.1 could not be installed on win 7 x64. So, doing as this thread said, I copied an installed CW 6.1 from a win XP x32 PC. Now the CW 6.1 IDE runs over win 7 x64. The problem is that I cannot use my demoJM to debug because it's not recognized.

I try what kef suggested HERE, copying PEUSBW2.DLL and wdapi900_32.dll (renamed as wdapi900.dll) to CW\prog (also I try to CW\prog\P&E) and nothing happend. I think it may be necesary to notice that my win 7 PC didn't have any of these files... HiWave still couldn't find the board.

Then I try this thread. Here they talk about 4 files, each has a different version number according to the CW version in use. I think I may not understand quiet well this part. Should I name the downloaded files as in my folder? I mean replace the old ones, with the new ones renamed as the old ones.

Well, in my CW 6.1 installation I've got:

- ICDrs08_dll_v109.dll

- ICD08z_dll_v153.dll

- prog08z_dll_v153.dll

- prog08z_dll_v155.dll

- progrs08_dll_v108.dll

Wich names should I use? I'm confused

A couple of questions:

1) When first install P&E drivers v10 (on win 7), I install them in C.\pemicro... Is that ok? Is it irrelevant?

2) Inside c:\Program Files(x86)\Freescale\CodeWarrior for Microcontrollers V6.1\Drivers I have driver version 9, because I copied it from the win XP PC... Is it fine? Or should I put there the v10 driver?

I'm having the same problem as layman in the first post here (look for the attached JPG). Except that under "Device Manager" I've got:

Jungo

+---------- PEMicro USB and Serial Interface (i00)

+---------- PEMicro USB and Serial Interface (i01)

+---------- WinDriver

Please, any clue would be appreciatted. Thanks in advance!!!

Re: Debug with Demo Board over Win 7 x64

kef — Wed, 22 Sep 2010 13:14:55 GMT

Sebastian,

do you see multilink listed in connection dialog? It should be listed in (I think) Port: combo box. If multilink is listed, then IMO you installed CW V6.x on Win7 64bits properly.

Did you try to connect to native DEMO modules with project setup to target native DEMO board chip? I mean if you have DEMO board for QE128, then your project must be setup for QE128 and nothing else. I think someone reported previously that he couldn't connect even to native chip but in different package. I doubt different package was a problem, but maybe it was different maskset with different SDID/PARTID register.

With that drivers DLL's trick I was able to install CW6.3 on Win7 64bits machine and connect to DEMOQE. Both S08QE128 and MCF51QE128 modules were working.

Re: Debug with Demo Board over Win 7 x64

donw — Wed, 22 Sep 2010 13:45:31 GMT

Like sebastian, I have done all the tricks suggested to get CW6.1 running on WIN7 64 bits with a

DEMOJM board. (JM60)

I get the same problem, the debuger's 'connection manager' does not find the USB device:

Port 'undetected....'

and the DEMOJM red 'power' led does not come on.

There seems to be something odd about the JM board...

(my board won't connect to CW 10.0 debugger either. So far P&E and FS can't suggest a solution)

Re: Debug with Demo Board over Win 7 x64

kef — Wed, 22 Sep 2010 14:01:42 GMT

Hm, maybe it's really something wrong with DEMOJM.

Red light is driver OK light, or is it target power OK light? If driver OK light doesn't come, then something is really weird with drivers. Maybe thay are incompatible with DEMOJM? Did you try to download latest V10 drivers from P&E micro and installing them? If still no go, then it's question for P&E, why their drivers don't work with DEMOJM.

Re: Debug with Demo Board over Win 7 x64

donw — Wed, 22 Sep 2010 14:07:10 GMT

the red light is the 'driver connected' light . the USB 'power on' light is on.

All works OK on a XP system, or on WIN& 64bit, under VM running xp.

what is the driver file concerned?

Re: Debug with Demo Board over Win 7 x64

kef — Wed, 22 Sep 2010 14:59:42 GMT

"Driver connected" light is independent of codewarrior. No light means driver is not working properly. Adding required PEUSBWD2.DLL and adding&renaming wdapi900_32.dll from here makes sense only if multilink lights are working properly.

Re: Debug with Demo Board over Win 7 x64

donw — Wed, 22 Sep 2010 15:06:52 GMT

So what is required to get it to connect?

Re: Debug with Demo Board over Win 7 x64

kef — Wed, 22 Sep 2010 15:50:22 GMT

I don't know. You may try downloading latest P&E drivers and Driver Test software from www.pemicro.com and see if it can be solved. If not, then try asking P&E support.

Re: Debug with Demo Board over Win 7 x64

sebasira — Wed, 22 Sep 2010 20:21:36 GMT

The DEMOJM has 2 lights:

- GREEN: USB connected (maybe driver OK too) is as the BLUE light on the BDM with plastic case

- RED: BDM power ON, as the ORANGE light on the BDM with plastic case

I don't see the Multilink listed on the connection dialog. It says:

Undetected. Disconnect/Connect USB cable. Click Refresh List [FAQ #29]

I do this with the demo board disconnected from my MCU target. Because the detection in the connection dialog is INDEPENDET with the target connection/disconection... If the BDM is detected properly, then it says that it can't connect to the target or maybe the reset line is holded.

So I didn't try with the daugther card, because in my opinion that won't change anything. I assume it's a driver problem because if you try debugging on a PC without BDM driver the same thing will happend because the BDM cannot be detected. I also assume that it's not an especific problem of the JM demo board... I have an AC demo board too, I'll try that in order to discard that is a JM specific problem.

Please, looese just a minute and take a look at this JPG here. This is a "picture" of the problem that layman has with DEMOQE board. I've got the same problem, with a little difference. In the JPG, under Device Manager layman has:

Jungo

+---------- USB Multilink 2.0

+---------- WinDriver

But when I plug the demo JM board I have

Jungo

+---------- PEMicro USB and Serial Interface (i00)

+---------- PEMicro USB and Serial Interface (i01)

+---------- WinDriver

That's the reason I think it's driver problem. I understand nothing about Device Drivers, DLLs, or anything related to that, so I don't know where to go from here. I only install driver v10 from P&E site, and I don't know why it appears two times.

Also, I think it may has to be with the trick related to the files listed on my first post... I remember that someone says that if the name wasn't change properly (v1.54 to v1.56) it won't work.. so wich name should I put to them????

Re: Debug with Demo Board over Win 7 x64

sebasira — Wed, 22 Sep 2010 20:25:56 GMT

One more thing.. Yesterday I entered at P&E site and they say the de Driver Test application is not modifyed to work with win 7 x64... So I cannot asure you it's a driver problem

Re: Debug with Demo Board over Win 7 x64

kef — Wed, 22 Sep 2010 23:56:06 GMT

I found my DEMOQE and got temporary access to Win7 x64 machine, on which I did that dlls trick (I'm still working on WinXP x86).

1) Yes, red light is target power light. Green light is driver ok light.

2) Device manager shows exactly the same 3 items under Jungo tree:

Jungo

+---------- PEMicro USB and Serial Interface (i00)

+---------- PEMicro USB and Serial Interface (i01)

+---------- WinDriver

Starting hiwave and ... oops. Dialog box appears (see attached picture) and I connection dialog doesn't see multilink connected. So it's not enough to copy wdapi900.dll. It must be installed somehow. Probably it was worked for a while in trial mode. Beta version of CW for MCUs V10, were I found this required wdapi900*.dll, had some installation files around this dll, install.bat or something. I'll try to find these files, though it's likely I deleted them...

Re: Debug with Demo Board over Win 7 x64

kef — Thu, 23 Sep 2010 00:30:10 GMT

I also got weird notice in hiwave command box. Driver did not initialize etc. So I guess your setup is the same like mine. Problem is wdapi900 is not properly installed.

Re: Debug with Demo Board over Win 7 x64

sebasira — Thu, 23 Sep 2010 03:40:16 GMT

As I said before, I don't understand device drivers... looking on the web, for wdapi900.dll and it's installation, I've found this.

in the linked page, at the end. ITEM 6, says something about distribute wdapi dll... Maybe that can give someone a clue.... Sorry if that's off-topic, as I knew nothing about DLL.

Best Regards

Re: Debug with Demo Board over Win 7 x64

peg — Thu, 23 Sep 2010 03:55:21 GMT

Hello again Sebastian,

It seems to me your problems are more to do with running on Windows 7 than anything else.

I do not have any experience here.

Just offering a few pointers to hopefully make your detective work easier.

Try to get a setup working on a WinXP machine first to prove everything works.

Use an older demoboard to prove the setup first, (I think you said you had one?)

Use the demoboard with a daughtercard only first.

Only when you have the daughter card MPU working try to debug through the demoboard to a remote device.

Re: Debug with Demo Board over Win 7 x64

kef — Thu, 23 Sep 2010 23:21:42 GMT

Sebastian, unfortunately wdreg*.exe trick doesn't work. Wdreg for x86 doesn't work on x64 system; and wdreg for x64 seems to not updating required registry keys or something.

But CW V10 should work anyway. Maybe not for debugging debugging everything, but at least original DEMOJM daugther cards must be OK.

Re: Debug with Demo Board over Win 7 x64

sebasira — Fri, 24 Sep 2010 00:28:34 GMT

Well, I think that's what I'll do for know... work with demo JM with JM daugther card... Until I found a way to solve this problem

Thanks all of you!!!

Good Luck

Re: Debug with Demo Board over Win 7 x64

kef — Fri, 24 Sep 2010 04:21:45 GMT

I made my expired driver working again on Win7 x64. .. By installing NoICE www.noicedebugger.com . Now wdapi900 trick is working again :smileyhappy:. But I wonder, will it work forever or expire again after some time? Does anybody knows what's evaluation period of Jungo WinDriver? Did you also expire "P&E driver licensing problem"?

Re: Debug with Demo Board over Win 7 x64

sebasira — Fri, 24 Sep 2010 10:06:59 GMT

What? So you make it work?

How yo did it, kef? Just intalling noICE?

If you made it, and I can make it too, it would be really funny... I spent ALL my entire day creating a partition in my notebook with win 7, creating a win XP installer with SATA HDD drivers.... Then the trying to achieve the dual boot... and after that looking like crazy for XP drivers... Never the less, I'd preffer working under win 7

Re: Debug with Demo Board over Win 7 x64

sebasira — Fri, 24 Sep 2010 10:12:00 GMT

I was so excited I didn't see your questions...

No, I've got no idea about Jungo WinDriver expiration. And againg no, I didn't get the P&E Licensing problem.

But know that I'm remembering I think I saw this, once, long time ago... It was because I was installing and evaluation version of codewarrior. Since then, I've never get that message again.

Re: Debug with Demo Board over Win 7 x64

kef — Fri, 24 Sep 2010 13:15:28 GMT

Sebastian

Yes, installation of NoICE fixed driver licensing problems, at least for a while. Now in CW debugger's Connect dialog I see USM-ML-12 listed. Connection to DEMOQE board also is working.

Like I said before, with DEMOQE connected, in device manager I have axactly the same Jungo items like you. Try checking if you did these steps on Win7 x64:

1) P&E drivers V10 or later have to be installed

2) take this zip file http://forums.freescale.com/freescale/attachments/freescale/CWCOMM/7202/1/cw_win7_dlls.ZIP

3) unpack it (two DLL's) into <CW root>\prog folder

4) rename wdapi900_32.dll to wdapi900.dll

After this is done, you should see multilink listed in debugger connection dialog.

If it's old P&E driver licensing issue, try installing NoICE.

-------------- update ---------------------

No, my problems aren't solved. After rebooting machine I started CWdebugger and it again complained about P&E driver licensing. ..Ok, starting NoICE - it works. Closing NoICE. Starting CW debugger - hooray, it's happy again, doesn't complain about driver licensing and even sees multilink and is able to target using multilink.

It seems something is really bad with driver installation on my machine. I'll try to reinstall it. If it doesn't help, then workaround will be to execute NoICE after avery rebooting of Win7.