EB-006-00-9 Driver issue

[bobingabout]

I just receaved a new HP7631 PIC Development center, which includes the latest programmer board EB006-V9, or EB-006-00-9 according to the board.

After constructing it, I boot up my computer, and install the EB006 driver from the supplied CD, and then connect the programmer.

Windows identifies the device as an EB006 Multiprogrammer, but fails to detect the correct driver for it.

So I went on your website, looked up the EB006, and downloaded the "Latest" driver from the EB006 page, and tried again. samme result.

Just for your information, the computer is running Windows XP, I think SP3, but I can't be certain.
(It was maintained by IT services untill they wrote it off and let me keep it in september when they installed a windows 7 computer. windows 7 SP1 64bit will be the final target platform, but before I get IT to install it on the network, I need to test run it myself on XP.)

Also, for the V9, when I finally get the drivers working, which software should I be using to program it? mLoader or PPPv3?

[DavidA]

Hi Bob,

It looks like for Windows XP this device is not detected automatically, for windows Vista and above this should be detected as a WinUSB device.

I will put something together which includes the .*inf file to allow the device to be detected.

EB006v9 will use mLoader to program.

I will reply to this topic with the solution shortly

[bobingabout]

I took it up to IT services, and asked them to try it on one of their Windows 7 test computers.

Same problem, it can't find a driver for the device.


On the topic of what software I need, do I need PPPV3 installed at all, or just mLoader?

[bobingabout]

Okay, the problem isn't "Exactly" the same, on windows 7 it does fail to find the device driver, just like XP, however in windows 7 you can "force" it to use the EB006 driver, and it will accept it, windows XP will not.

But the end result is the same, in that mLoader responds by telling me that no prgrammer is connected.

[Benj]

Hello,

Here is the driver for the v9 board, you currently need to install it via the Windows device manager.

EB006v9 Driver and INF.zip

(4.81 MiB) Downloaded 1227 times

Let us know how you get on.

[bobingabout]

Okay, I downloaded this driver, and extracted it on the test machine to a directory.
Then I plugged in the EBlocks programmer, and it asked to install a driver.
So I pressed to look in a location, set the location to the extracted directory, and it detected the files.
It then proceeded to install the driver.

And then when it finished installing the driver, came up with the following error: "Windows cannot load the devvice driver for this hardware. The driver may be corrupted or missing. (Code 39)"

A restart required me to install the driver all over again, with the same result.

[Benj]

Can you send us a screen shot of the device in device manager.

We have done a fair bit of testing with the board here on Win7 and 8 and so far everything has been working well. Restart shouldn't be required.

As an after thought, Have you extracted all the files out the driver zip file, these files all need to be extracted and located together to allow them to install correctly.

[medelec35]

My experience with EB006 V9 on a 64bit win7 machine.

After connecting EB006 V9 to usb it sated the usual driver not installed successfully etc.
Within device manager browsed to extracted directory and after selecting yest to install anyway, I got the message not installed successfully again.
Tried again this time I got the message:

EB006V9 message.png

(33.96 KiB) Downloaded 19752 times

Restarted PC and now:

EB006V9_1png.png

(3.45 KiB) Downloaded 19752 times

Odd how it did not work the first time but it did work on the second attempt

Martin

[bobingabout]

Okay, Starting with windows XP

Attempting to install the driver seems to work, untill it "Finishs", at which point I get this.

Windows XP Driver Install.png

(15.06 KiB) Downloaded 19777 times

And as you can see afterwards, lookinig at it in the Devicce Manager shows this

Windows XP Driver.png

(27.6 KiB) Downloaded 19777 times

As you can see, the driver installs, but doesn't work (or at least it tells me it doesn't work).

Since I can only post with a max of 3 attachments, continued in next post.

[bobingabout]

Windows 7.

From the begining, Attempting to install the driver provided on the supplied ELSAM V2.4 disk, I get this result

Windows 7 Disk Driver Install.png

(10.07 KiB) Downloaded 19775 times

As you can see... it doesn't like the driver.


Next step, using the driver provided in this forum gives me this result.

Windows 7 Driver.png

(13.92 KiB) Downloaded 19775 times

This seems to work, but then when I try and perform most actions within mLoader, I get the following

Windows 7 programmer.png

(4.37 KiB) Downloaded 19775 times

This is mLoaderV3 as supplied on the ELSAM V2.4 disk, so, I'm thinking it's the wrong version for this board.

Tested on both Windows 7 32bit and 64bit, with the same results.

[medelec35]

Hi Bob,
I used the driver posted here:
http://www.matrixmultimedia.com/mmforum ... 459#p57603
Not tried with the drivers on the disk.

I will also try with mloader when I get home this evening.

Martin

[Benj]

Hello,

The driver on the ELSAM disk is for EB006 v8 and previous. The driver provided here in the forums is the current version.

David is currently looking into mLoader and will hopefully come up with a fix shortly. Again the version of mLoader supplied on the ELSAM disk is not the current version and will not work with the v9 boards.

[bobingabout]

I guess my next question is, Why provide a disk for a V8 board with a V9 board?

I'll use this driver, and wait for mLoader, then report what happens.

[Benj]

Hello,

That's a good question, I thought the ELSAM disk had been scrapped years ago. I'll go and have a word and see what the state of play is.

[DavidA]

Hello Bob,

I have updated the mloader on the web, please try that and load up mloader.exe when the device is plugged into your machine. This should allow you to see if the device is detected by mloader as it should be recognised as a device.

[bobingabout]

I don't mean to be rude or anything here, but, Aparantly, you didn't upload the latest version, you re-uploaded the version that was already online... or so it apears.


After Ben mentioned yesterday that I shouldn't be using the version from the ELSAM disk, I looked and downloaded a version of mLoader with a download date of 2011, version 3.1.1.2.
Today, I downloaded the "new" version with todays date. it also apears to be version 3.1.1.2. (checking the details tab of file properties in windows to get the version information here.)
Also All the files apears to be the same as in the zip from yesterday (Name, Filesize etc).

I even downloaded again on a different computer to make sure it wasn't some kind of cache issue, same result.

Could you double check this for me?


In any case, mLoader recognises that the EB006 is there, and communicates with it (on windows 7 anyway, on windows XP, it still can't see it).
However, whenever I try to send a HEX file, I get the error: "mLoader Error. Unknown chip type in data file."

Edit: I suppose information worth sharing is that the hex file I'm trying to send was created from the latest version of MPASM, part of MPLab V8.92, and it is for a PIC16F84A.
One of the first things I did was replace the chip that came with the developement board with a PIC16F84A, for the simple reason that I've never used a PIC16F1937, and I havn't had chance to look up anything about the chip yet, I'm just trying to send files that I already have.

[DavidA]

Hello,

Please try this later version of mloader as it contains some more diagnostic.

Unfortunately i dont have an 16F84A to check here if it is detected correctly.

http://www.matrixmultimedia.com/temp/mLoaderv3.zip

[JohnCrow]

Hi

Just connected my V9 board to Windows 7 X64

It searched for and downloaded the correct driver all ok.
When trying to send a file Flowcode 6 showed a dialog box saying device not detected, press reset button (Similar to the ECIO)
But it didn't detect the board.

I rebooted windows, and now all seems to work fine, that dialog does not appear and the file is sent to the 16F1937 and runs ok.
Using Mloader V3 (exe dated 04/03/14).

[bobingabout]

I think you linked the wrong files, that apears to be source code...

It does contain a Debug build though, so I'm trying that.

it incorrectly detects my EB006 as "PIC Device" EB031, and locks up if you try and send a file to the programmer.

[DavidA]

Hi,

Apologies, yes that is the completely wrong and also very old version. Please try again at the same link:

http://www.matrixmultimedia.com/temp/mloader.zip

[bobingabout]

Okay, this took a little bit more testing than usual.

First thing first, if you don't choose the right chip when you try to program, it flips out and "Forgets" the programmer, and only unplugging the programmer and plugging it back in will make it detectable again.


If you select the right chip, Erase works fine.
Sending the file brings up the error message that you can see in the screenshot, pressing continue apears to try to send the program, the Prog LED on the board even lights up

However... as you can see in the text window in the programming software, it fails to varify the code onchip, and furthermore, the chip do anything, the program doesn't run.

here's a screenshot.

Sending Error.png

(206.88 KiB) Downloaded 11991 times

[bobingabout]

Okay, just to be thorough, I looked up how to program a 16F1937 that came with the programmer, just to try it in the default state... these are the results of my attempt to send the data file in mLoader:

Unknown chip type in data file

Board Type: EB006 v9
IsOpen : no
ID from Board: 65504
Chip CmdLine:
USB Hardware: USB\VID_12BF&PID_0021&REV_0000
USB Description: EB006 Multiprogrammer
ADCval: 225.088435
Location: ParseCsvFile.cpp @ 291 (ParseCsvFile::FindChipFromID)


Bad field entry in data file

Board Type: EB006 v9
IsOpen : no
ID from Board: 65504
Chip CmdLine:
USB Hardware: USB\VID_12BF&PID_0021&REV_0000
USB Description: EB006 Multiprogrammer
ADCval: 225.088435
Location: USBPPPDriver.cpp @ 3148 (USBPPPDriver::GetScriptName)

[DavidA]

Hello,

Thanks for the diagnostic, we have seen these numbers come out before.

Are you connecting to the EB006 v9 via a USB hub?

If so can you try with it plugged directly into the computer?

[bobingabout]

Stright into a USB port on the front panel of the PC.

When I get a chance, I can try plugging it in different ports on the back.

[bobingabout]

I tried it in every port in the computer, except 1, because that port has my KVM switch with keyboard and mouse plugged into it.

on some ports, the "Bad field entry in data file" error would often show up, on other ports, not at all. my guess is this is the error related to a USB hub? a further guess would be that because there are quire a few USB ports on the computer, there could be a hub built into the motherboard.

on all ports, there is almost always 1 of 2 errors that show up, there was 1 occassion when it did actually program without any dialogue boxes popping up, but only one.
The first of the 2 errors is the "Unknown chip type in data file" error mentioned previously.
The other error is as follows:

On board chip does not match the given chip

Board Type: EB006 v9
IsOpen : no
ID from Board: 9283
Chip CmdLine: 16F84A
USB Hardware: USB\VID_12BF&PID_0021&REV_0000
USB Description: EB006 Multiprogrammer
ADCval: 225.088435
Location: USBPPPDriver.cpp @ 383 (USBPPPDriver::Write)

The onboard chip was in fact a 16F84A, the strange thing is it would show up occassionally, without me changing anything. I'd just press the send button several times in a row, and I'd get either this error, or the first one.


In any case, every single attempt to program the chip, even the time when no dialogue boxes showed up, I receaved these messages in the program message box:

File sending!
File sent with 1 warnings:
1: Flash memory not verified - may be due to code protect

Code protection is turned off in the config, and on no occcassion of attempting to program the chip, did the program run.


I will further add that to make sure there is no error with my program, I removed the chip, programmed it with my V8 board, and placed it back in the V9, and it did run as intended, so there is no problem with the running side of the V9, I'm just having trouble programming with it.