EB006 Issue: PIC18f4680

[Enamul]

Hi Team,
I need your kind attention regarding the multi programmer board EB006. We have been using that for couple of months and it was working fine and also fine to-date if we want to write pic like 16f877a, 16f876, 18f452 etc.

But we are struggling to use PIC 18f4680 which has built-in CAN facility and that's the only chip we can have locally right now. The problem is when we try to detect PIC 18f452 it detects but when I do the same for PIC 18f4680 it says "Could not ID the Chip on board"

Please help me to get around the problem.

Enamul

[Benj]

Hello Enamul,

I happen to have a 18F4680 device here and the autodetect is working correctly for me.

4680test.JPG (82.06 KiB) Viewed 11481 times

Do you have more then one of these chips to test to see if it is just the specific device that has the problem?

[Enamul]

Hi,
I have tried that on 18f4680 (3 chips not a single one detected) and then today tried with 18f4580 (bought just today) and same result. Then I thought there might be some problem regarding the version of PPP v3, I have tried with the ppp v3 in FC v5. Then I have found one ppp v3 you have attached for someone else here..
http://www.matrixmultimedia.com/mmforum ... =2&t=10632
Although the ppp shows a registry error.. but opens. The above ppp v3 and ppp v3 in FC 5 seems same version and none of them work..

I don't understand why..it makes me mad.
Is there any setting issue?
Enamul

[Benj]

Hello Enamul,

Open PPP from the v5 folder "Flowcode\v5\Tools\PPP".#

Click on Options -> Options.

Here is a copy of my current settings.

PPP.JPG (40.16 KiB) Viewed 11479 times

If this doesn't work or you already have these settings then try clicking the VDD switching manual override and trying each of the options one at a time.

Let me know how you get on.

[Enamul]

Hi,
Sorry to say...It doesn't work.

Thanks for all of your suggestions but I can't understand what to do now.

Enamul

[DavidA]

Hello Enamul,

Im just going to try and summarise your issue to get a better handle on it:

- Whenever you try and ID an 18F4680 chip it pops up with "Could not ID onboard chip"
- You have tried multiple chips of the same type and it still does the same thing
- The board programs all other chips you have fine including IDing the chip
- This is all with the latest version of PPP that is sent out in v5

A couple of questions then:

- What version of the EB006 are you using EB006-00-X on the board, where X is the version number of the board
- How are you powering the board, is it USB only or using a 13.5v power supply
- Do you have a PICKIT programmer you could use to test identification of the chips with via the ICSP header on the EB006 (board version dependant)
- Are any of the LVP jumpers in the LVP mode? (board version dependant)

Ive just tried to ID an 18F4680 on my EB006 with the basic PPP that comes with v5 and it worked, so its a bit strange why yours does not.

[Enamul]

Hi David,
Thanks for the organized reply..

- What version of the EB006 are you using EB006-00-X on the board, where X is the version number of the board

My one is EB006-00-6

- How are you powering the board, is it USB only or using a 13.5v power supply

Using 13.5v power supply not USB

- Do you have a PICKIT programmer you could use to test identification of the chips with via the ICSP header on the EB006 (board version dependant)

According to Ben PM, version 6 doesn't have this facility.

- Are any of the LVP jumpers in the LVP mode? (board version dependant)

I'm not quite sure is that version 6 feature or not..

Please guide me how to sort out the problem..
Enamul

[Enamul]

Hi Ben/David,
We have a parallel port (old is gold!) programmer which use Epiqwin software to program the chip. We have managed to program 18f4580/4680 chip which clarifies that the chips are in normal quality.

So there must be something went wrong with EB006-00-6 version of multiprogrammer for programming (even detecting) those chip. I have sent a PM to Ben. Is there any issue related to that? If you could test one of those ICs in that version (if you still have any) I think that will be great. If you get the same problem, in that case I can buy a new one.

Please let me know as I want to use MM programmer which provides complete config options for the chips.
Enamul

[Benj]

Hello Enamul,

We have tested here using the v6 EB006 so I don't think that's the issue. I will have a ponder about it because i'm not sure whats currently going wrong here.

Please let me know as I want to use MM programmer which provides complete config options for the chips.

If you configure the device in Flowcode and then compile to hex then the config data is embedded into the hex file and so should still be programmed correctly when using your 3rd party programmer.

[Enamul]

Hi Ben,
Thanks for the information. I was thinking 3rd party programmer is just over-write the configuration bits..As I have few basic options to select in Epiqwin.
Thanks,
Enamul

[Reinier Ott]

Dear David,

I had a comparable problem with ICD and my EB006-00-7. I tried to flash a (simple) 16F88 directly with the 16F88 socket on the board. (Of course , I wired MCLR , PGD, PGC , + 5V and GND correctly to my custom PCB with a self made cable) To avoid conflcts, I was very careful with circuit on my custom board before.
2 times the ICD process was succesful. But than PPP could not reconize the 16F88 anymore. "could not reconize ID on board"
Than I disconnected all cables (Custom ICD cable , 13.5V and USB) and put the 16F88 again in the socket of the EB006 . But unfortunately , the chip was not reconized anymore. Also the same result with a new 16F88, and after restart the board and the PC .

I Thought that the multiprogrammer EB006 is defect.

Fortunately, Now the EB006 is working OK after a couple of swaps of the 3-state jumper USB/ICD2 (I did not understand why ???? )

But, now I'm very uncertain to use ICD again.

I use Flowcode 4 and the EB006-00-7 only

I appreciate suggestions very well

with kind regards,

Reinier

[Enamul]

Hi,
As I'm not sure do you have anything connected in any of the ports, I would disconnect all from ports and try again. It worked for me. So can be true in your case who knows.

[Reinier Ott]

Dear Enamul, David ...

Perhaps this topic is not specific the 18f4680 but I tried again to program a 16F chip to use ICD . I study again the connection and checked all by DMM : all looks fine. The custom board with the PICmicro is very simple (Res of 10k MCLR to VDD : acc. spec , VDD is comming from the EB006 only )

No other peripheral was connected to the board. (only I use a ZIF socked in this case) but connecting to the plain IC socked does not resolve the problem.



I tried with a 16F88 and a 16F887 (Using a ICD cable): Programming obstinate fails. If I replaced back these chips into the ZIF sockets : No problem
Specification of my custom made ICD ribbon cable:

25 cm long.
pin 1 : MCLR
Pin 2 : VDD (+5V)
Pin 3 : GND
Pin 4 : PGD (RB7)
Pin 5 : PGC (RB6)
Pin 6 : n.c.

I used Flowcode V4 (change nothing for programming with ICD cable) . The programmer = EB006-00-7 with PPPv3 and corresponding 13.5 V adapter

I can not find out why the chip is not recognized if I use a ICD cable dictecty connected in the IC of ZIF socket.

Thanks about if you can give me an advise,

With kind regards,

Reinier

[Enamul]

Hi,
Thanks for the picture. I bought a ZIP socket with the similar intention of you but didn't tried yet. I will try and let know whether I can replicate the problem or not.

[Reinier Ott]

Hi Enamul,

Thanks for your quick reply. I'm interesting into your experiences

Thanks,

Reinier