v3 dev board doesn't work anymore please help me
v3 dev board doesn't work anymore please help me
first i want to thank you guys for the wonderful board - HP-488-00! in the beginning i met a problem with my ripple PSU, but i sort it out followed you advice in the forum. i started with programming in MPASM. had my LCD and ADC working on PIC16F88. it was working perfect to one week ago wen i tried to upload my new programm but unsuccessful. Since then i've got the message:Could not ID the onboard chip. my PSU is 13.0V in point Vpp, the last programm in the Pic Micro's memory still running, i tried to read it in LVP mode without success. when the PSU is unpluged the PPP software says: Slave pic micro has no power. And when the USB cable is disconnected i've got message: USB cabe is not connected. Which means your chip and firmware are OK.
need help pease
need help pease
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: v3 dev board doesn't work anymore please help me
Hello
It sounds like your chip may have either become damaged or write protected. Either way you will not be able to reprogram the device. This can happen if the Code Protect and Data Protect settings are enabled in the PPP config screen. This seems even more likely as the system cannot ID the chip.
Just as a check,
J20 should be set to USB with horizontal connections
J29 to PSU with horizontal connections
Jumpers above J5 to I/O with horizontal connections
Jumpers next to PortC Default with horizontal connections.
Also please make sure that you have no external circuitry connected to PortB. Switching the Oscillator switch to RC mode also helps sometimes.
If none of the above works for you then I recommend getting some new PICmicro chips. You can either order free samples from Microchip.com or you can buy from us, Microchip direct or your favorite retailer. The chips tend to be fairly inexpensive. Approx Β£1-3 per chip depending on its functionality.
It sounds like your chip may have either become damaged or write protected. Either way you will not be able to reprogram the device. This can happen if the Code Protect and Data Protect settings are enabled in the PPP config screen. This seems even more likely as the system cannot ID the chip.
Just as a check,
J20 should be set to USB with horizontal connections
J29 to PSU with horizontal connections
Jumpers above J5 to I/O with horizontal connections
Jumpers next to PortC Default with horizontal connections.
Also please make sure that you have no external circuitry connected to PortB. Switching the Oscillator switch to RC mode also helps sometimes.
If none of the above works for you then I recommend getting some new PICmicro chips. You can either order free samples from Microchip.com or you can buy from us, Microchip direct or your favorite retailer. The chips tend to be fairly inexpensive. Approx Β£1-3 per chip depending on its functionality.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: v3 dev board doesn't work anymore please help me
thanks for your quick reply Benj.
i checked the jumper configuration - it is same.
Forgot to tell you, that i tried with another brand new picmicros 12F675 and 16F684, ordered through Farnell together with your dev-board.
I suspect that the problem comes from multiplexers U3 or U6 but can't be sure without oscilloscope.
Is it normal, that on my dev brd R33=100Kohm and R4=47kohm different than diagram's values respectively 10Kohm and 10Kohm?
And when i've got the message: Could not ID the onboard chip, the LED1 flashes 0.3s on and 0.3s off.
thanks.
i checked the jumper configuration - it is same.
Forgot to tell you, that i tried with another brand new picmicros 12F675 and 16F684, ordered through Farnell together with your dev-board.
I suspect that the problem comes from multiplexers U3 or U6 but can't be sure without oscilloscope.
Is it normal, that on my dev brd R33=100Kohm and R4=47kohm different than diagram's values respectively 10Kohm and 10Kohm?
And when i've got the message: Could not ID the onboard chip, the LED1 flashes 0.3s on and 0.3s off.
thanks.

- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: v3 dev board doesn't work anymore please help me
Hello
Yes the values 100K and 47K are correct to the parts list I have here.
If you have tried other brand new chips and your board is still not programming or detecting any devices then yes there sounds like a problem.
If you like you can return the board to me at the following address and I will arrange a replacement for you.
Ben Rowland
The Factory
23 Emscote Street South
Halifax
HX1 3AN
Please remember to include your name and address in the package so I know who the item came from and where to sent the replacement.
Yes the values 100K and 47K are correct to the parts list I have here.
If you have tried other brand new chips and your board is still not programming or detecting any devices then yes there sounds like a problem.
If you like you can return the board to me at the following address and I will arrange a replacement for you.
Ben Rowland
The Factory
23 Emscote Street South
Halifax
HX1 3AN
Please remember to include your name and address in the package so I know who the item came from and where to sent the replacement.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: v3 dev board doesn't work anymore please help me
Thank you Benj, for your offer. Unfortunately I've made some hardware changes, which make my development board probably out of warranty. The changes are: de soldered multiplexer chip u3(did this before to read about mux burning fix) and two soldered capacitors instead 10uF ripple cap's. the time wise warranty is still active. I've just bought it a month ago.
So if there is no option to claim warrantable repair, was thinking as a last try, to buy a new programmer's chip with ppp firmware and the mux U3 and u6. Could you please give me a quote.
if doesn't work the only option is to get another (Microchip's) programmer and connect them via ICSP.
thanks.
So if there is no option to claim warrantable repair, was thinking as a last try, to buy a new programmer's chip with ppp firmware and the mux U3 and u6. Could you please give me a quote.
if doesn't work the only option is to get another (Microchip's) programmer and connect them via ICSP.
thanks.
Re: v3 dev board doesn't work anymore please help me
hello benj and matrix multimedia, I am very grateful, the last solution worked for me and my board is alive again. Thank you for the great support.
Last edited by tsecko on Tue Jan 24, 2012 10:10 pm, edited 1 time in total.
Re: v3 dev board doesn't work anymore please help me
Hello Benj and Steve,
I have also a problem with the PPP programming chip.
I use the EB-006-00-6 board with the PIC16F877A chip on it. At work we have several boards but one board doesn't recognize the chip. I tried to program the chip but I allways have the message: "Could not ID the onboard chip - assuming it is the one specified in the configuration screen, i.e. PIC16F877A" meanwhile LED1 is flashing.I use SourceBoost to program it but when I use Flowcode (version 3.4.7.48) I have the same message.
When I remove the PPP chip and replace it by another one (coming from an other, working board) then there is no problem. What can I do? Do I also have to send this chip back to your company?
Greetings.
I have also a problem with the PPP programming chip.
I use the EB-006-00-6 board with the PIC16F877A chip on it. At work we have several boards but one board doesn't recognize the chip. I tried to program the chip but I allways have the message: "Could not ID the onboard chip - assuming it is the one specified in the configuration screen, i.e. PIC16F877A" meanwhile LED1 is flashing.I use SourceBoost to program it but when I use Flowcode (version 3.4.7.48) I have the same message.
When I remove the PPP chip and replace it by another one (coming from an other, working board) then there is no problem. What can I do? Do I also have to send this chip back to your company?
Greetings.
- Steve
- Matrix Staff
- Posts: 3433
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
Re: v3 dev board doesn't work anymore please help me
If the board is under warranty then we will replace the "PPP" chip for free. If not, there will be a small charge to cover our costs.
Please contact us via this page:
http://www.matrixmultimedia.com/contact2.php
Please contact us via this page:
http://www.matrixmultimedia.com/contact2.php
-
- Flowcode V4 User
- Posts: 16
- Joined: Sat Jan 17, 2009 4:22 am
- Has thanked: 4 times
Re: v3 dev board doesn't work anymore please help me
Hi, I have problem with HP 488, I am trying to compile the program using Flow-Code 4, but my pc cannot detect the USB cable..I use another machine, its still comes with same message. "USB cable is not connected", Lastly I try with PPP v3, also comes with same message. Is the board or firmware damage? What should I do? For your information, this HP 488 was run before.
Kind regards:
Sufre
Kind regards:
Sufre
- DavidA
- Matrix Staff
- Posts: 1076
- Joined: Fri Apr 23, 2010 2:18 pm
- Location: Matrix Multimedia Ltd
- Has thanked: 58 times
- Been thanked: 258 times
- Contact:
Re: v3 dev board doesn't work anymore please help me
Hello Sufre,
Ensure you are powering the board correctly, and that the jumpers are in the right locations, also try other chips if you have some available, also ensure that only one chip is on the board at a time.
Ensure you are powering the board correctly, and that the jumpers are in the right locations, also try other chips if you have some available, also ensure that only one chip is on the board at a time.