Hi all,
I'm hoping someone can help. Up to last week, my M52259DEMOKIT has been working fine (well, except for single stepping) with its OSBDM interface.
Today, I tried it again and the USB gives 3-dings, and it says it can't find an appropriate driver.
Between then and now I've likely modified my config of CW 4.7 (I have CW7.1, CW5.9, and CW4.7 all installed, for CFV2, CFV1, and HSC12 development).
I might have installed some MPLAB compilers, too.
The problem seems to root from the VID/PID coming from the OSBDM device -- it doesn't match any VID/PID in any INF file...
From Device Manager, it is: USB\VID_15A2&PID_0035\5&7BEA176&0&1
Can anyone tell me:
1. what is the VID/PID *supposed* to be for the OSBDM on the M52259DEMOKIT? You can find this in Device Manager under Properties -> Details -> Device Instance ID
2. what INF file is supposed to match this in /windows/inf? All I find is this:
C:\WINDOWS\inf>grep -i vid_15a2 *.inf
OpenSourceBDM.inf:"Open Source BDM (LibUSB-W32)"=LIBUSB_DEV, USB\VID_15A2&PID_0021&REV_0001
bulkusb.inf:%USB\VID_0425&PID_0467.DeviceDesc%=BULKUSB.Dev, USB\VID_15A2&PID_0001
oem11.inf:"CodeWarrior USB TAP"=Install, USB\VID_15A2&PID_50B3
oem11.inf:"CodeWarrior USB TAP"=Install, USB\VID_15A2&PID_50B3
C:\WINDOWS\inf>
Obviously, none of those will match.
I am completely stuck now doing 52259 development, and fear I will need to reinstall the OS (I've already reinstalled CW7.1 with no success).
Boy, it is almost worth paying the extra $$$ for the EVB over the DEMOKIT just to not have to deal with OSBDM.
Thank you for any help.
-- Rich
解決済! 解決策の投稿を見る。
Well, I figured it out... There was no magic reprogramming of a BDM going on (well, there was, but it was most likely a different BDM -- I believe only the P&E's support a firmware upgrade procedure thru CW).
If you find that your BDM spontaneously changes VID/PID and is no longer recognized by Windows, check to see if you accidentally installed J5 on the DEMOKIT board (connected to IRQ/TPMCLK). Apparently both personalities are built into the same firmware, and that jumper causes a switch -- you want the jumper removed.
Sorry for the noise. I figured I'd at least post the resolution in case anyone else ever has the issue.
-- Rich
I ordered another M52259DEMOKIT and it works fine and does *not* return VID/PID 15A2/0035 -- it returns 0425/1001.
So now I would like to know how did my BDM VID/PID get reprogrammed?
I do remember CodeWarrior 4.7 telling me it had to update BDM firmware, but I assumed it was updating the one on the HCS12, not the one on the 52259 -- it didn't even give me a chance to object!!! :smileysad:
Now I would like to know how to restore my old M52259DEMOKIT to working order.
Please can anyone tell me:
1. why some software (presumably CW4.7) reprogrammed my M52259DEMOKIT BDM, and how to prevent it from happening again in the future, and
2. how to fix my old M52259DEMOKIT and restore its BDM to VID/PID 0425/1001, like my new one.
Thanks.
-- Rich
Well, I figured it out... There was no magic reprogramming of a BDM going on (well, there was, but it was most likely a different BDM -- I believe only the P&E's support a firmware upgrade procedure thru CW).
If you find that your BDM spontaneously changes VID/PID and is no longer recognized by Windows, check to see if you accidentally installed J5 on the DEMOKIT board (connected to IRQ/TPMCLK). Apparently both personalities are built into the same firmware, and that jumper causes a switch -- you want the jumper removed.
Sorry for the noise. I figured I'd at least post the resolution in case anyone else ever has the issue.
-- Rich
No problem on the "noise". In fact, it's valuable trouble-shooting information. Thanks for sharing, and sorry that we could not help you. That is a unique problem, to say the least.
---Tom