PIC18F2550 not identifiable by "Flowcode V3" and PPPv3?!

[BeFu]

Hello,

as English is not my native language the description of my problem is not fluent. I do hope you're understanding anyway and give me its solution.

I've programmed the PIC16F88 which is normally plugged in the MCU-Multiprogrammer EB-006-00-6 with "Flowcode V3" successful. The Multiprogrammer is connected by an USB-Hub to my PC on which "Flowcode V3" is running.
Now I'd like to control the PIC18F2550 by using the USB_PACK which I've installed to "Flowcode V3". The PIC18F2550 is one of the PIC which are suggested In the PowerPoint-Demonstration of the USB_Pack. So I've pulled out the PIC16F88 form the Multiprogrammer before plugging the PIC18F2550. The multiprogrammer is connected to the Flowcode-PC in the same way by an USB-HUB. Also all switches of the Multiprogrammer are in the same position as with an plugged in PIC16F88. XTAL is selected as oscillator in "Flowcode V3".
After connecting the Multiprogrammer to my PC I start "Flowcode V3" an select PIC18F2550 as target for a new flowcode program. The PIC18F2550 is shown in the display image. For the first try my program switches all LED which are connected to PORT B on for 1000ms and then off for 500ms in an endless loop. The simulation of the program is working without any problems.
BUT now the porblem(s) starts:
- By pressing the menu button chip -> target the former selected PIC18F2550 is shown as target
- After pressing chip -> configuration the PIC18F2550 is not displayed in the list of "Select chip:". Also pressing the Button Autodetect fails with the message "PICmicro not found from ID 0x3C00 Please enter the chip name". After entering PIC18F2550 I press OK. Now the failure message "PIC section not found: [18F2550]" appears. I confirm it by pressing OK.
- Now I take the suggestion and press the button Switch to expert screen. There I can "Select Chip:" to PIC18F2550. After pressing Autoddetect PICmicro the failure massage "PICmicro not found from ID 0x3C00 Please enter the chip name" appears again. After writing PIC18F2550 and pressing OK the massage "PICmicro changed to PIC18F2550" is displayed. I confirm this message by pressing OK.
- NOW all seems to be ok. But chip -> compile to chip fails. That means the compilation runs without any problem but transferring the HEX code to the PIC18F2550 fails with additional failure messages.

Can you tell me please what configurations I've to change in order to be able to program the PIC18F2550 in the described way and control it by LabVIEW using the functions of the USB-PACK?

Thank you very much for your suggestions and help.
Regards,

BeFu
- The target is the way -

[Benj]

Hello

Please replace the file in your C:\Program Files\Matrix Multimedia\Common\PPPv3\ directory with file from inside the attached archive.

The chip should auto detect when in the expert mode of the PPP / Flowcode configuration. If it does not autodetect then are you powering the board with a PSU running 12V or over? Have you got the hardware jumpers set to PSU/USB :PSU, USB/ICD :USB.

If the chip is still not being auto detected then do you have an alternative chip you can try.

[BeFu]

Hello

Please replace the file in your C:\Program Files\Matrix Multimedia\Common\PPPv3\ directory with file from inside the attached archive.

The chip should auto detect when in the expert mode of the PPP / Flowcode configuration. If it does not autodetect then are you powering the board with a PSU running 12V or over? Have you got the hardware jumpers set to PSU/USB :PSU, USB/ICD :USB.

If the chip is still not being auto detected then do you have an alternative chip you can try.

Hello Ben,

thank you for sending the actual ppp_config_data3. I've installed it how you've described to the directory D:\Program Files\Matrix Multimedia\Common\PPPv3\ on my computer. I'm powering the multi programmer only by 5V from the USB connection out of the USB Hub.
With the installed ppp_config_data3 the PIC18F2550 is not auto detected in the expert mode neither of the PPP nor of the Flowcode configuration. In difference to the old ppp_config_data3 the LED 1 (supervion of programming voltage is blinking) when I write PIC18F2550 in the window which comes up when the auto detection of the CHIP fails in expert mode.
Have I to power the multi programmer board with 13.5V by an external power supply and set the three JUMPERS of J29 to PSU? I don't want to power the PIC18F2550 with the high voltage of 12V as in that case I'll be not able to program the PIC18F2550 in its LVP mode. Besides I've not found any information in the data sheet whether the PIC18F2550 has an LVP mode for programming as the PIC16F88.
Or have I to switch one of the Jumpers J11, J16 or J 17 to the other side for programming the PIC18F2550 in its LVP mode?
Thank you very much for your suggestions.
Regards,

Bernd Furnier
- the target is the way -

P.S.: I've changed the PIC18F2550 with a new one. But this one is also not auto detected. When sending the order for erasing the CHIP (with PPP) to the PIC18F2550 a window pops up with the failure messages "PIC micro not found from ID 0x3FF8"

[BeFu]

Hello Ben,

thank you very much for your advice and the modified ppp_config_data3 file.

Meanwhile I've found in the datasheet of the PIC18F2550 that you've to configure the PIN RB5/KBI1/PGM as LVP.

After installing your modified ppp_config_data3 and setting the LVP jumpers in the following way the PIC18F2550 is auto detected in the expert mode and I can program it.

Here the jumper settings for the right LVP configuration:

PB3--J11 LVP (its connected to LVP for the PIC16F88)
PB4--J18 LVP
PB5 J17--LVP (connected to LVP for the PIC18F2550)

Regards,

Bernd Furnier
- the target is the way -

[Benj]

Hello Bernd

Ah great glad its working correctly for you now. Yes to program devices using the USB supply you will have to move the jumper for the correct LVP pin and also enable the LVP mode in the expert configuration settings. This mode will be enabled by default when the chips are new but to manually get them into this mode you will have to perform a high voltage program first.