V4 cannot ID my chip on compiling..

For Flowcode users to discuss projects, flowcharts, and any other issues related to Flowcode 4.
To post in this forum you must have a registered copy of Flowcode 4 or higher. To sign up for this forum topic please use the "Online Resources" link in the Flowcode Help Menu.

Moderator: Benj

Post Reply
pic-newbie

V4 cannot ID my chip on compiling..

Post by pic-newbie »

Hi, Have just recieved flowcode V4, having upgraded from 3, and have run in to a few problems I can't seem to resolve. I'm attempting this install on a fresh and fully updated 32 bit Windows XP Proffesional install with a USB EB006 board and a PICF12F629 chip.

First things first, I have installed the driver from the V4 CD, (Matrix_USB_Board_Driver_install.exe). When I checked the installed driver, it was dated 08/09/2005, is this the latest one ?

The problem arose when I attempted to compile a program to the chip, I recieve an error when the programmer starts saying "Could not ID the onboard chip - assuming it is the one specified in the configuration, i.e. PIC12F629." You can click OK and then recieve a message saying "PICmicro has not been erased, continue ?" To which I said Yes. The process eventually fails, the entire log follows below.

I have tried several chips and have recieved the same error message. All help appreciated.

------------------------------


File name: C:\Program Files\Matrix Multimedia\Flowcode V4\Tools\PPP\Test 1.c
Generated by: Flowcode v4.2.3.58
Date: Thursday, January 07, 2010 10:43:02
Licence: Professional
Registered to: Brian Jarvis


http://www.matrixmultimedia.com


Launching the compiler...
C:\Program Files\Matrix Multimedia\Flowcode V4\BoostC\boostc.pic16.flowcode.exe -v -t PIC12F629 "Test 1.c"
BoostC Optimizing C Compiler Version 6.95 (for PIC16 architecture)
http://www.sourceboost.com
Copyright(C) 2004-2009 Pavel Baranov
Copyright(C) 2004-2009 David Hobday

Licensed to FlowCode User under Single user Pro License for 1 node(s)
Limitations: PIC12,PIC16 max code size:Unlimited, max RAM banks:Unlimited


Test 1.c
Starting preprocessor: C:\PROGRA~1\MATRIX~1\FLOWCO~1\BoostC\pp.exe "C:\Program Files\Matrix Multimedia\Flowcode V4\Tools\PPP\Test 1.c" -i C:\PROGRA~1\MATRIX~1\FLOWCO~1\BoostC\include -d _PIC12F629 -la -c2 -o "C:\Program Files\Matrix Multimedia\Flowcode V4\Tools\PPP\Test 1.pp" -v -d _BOOSTC -d _PIC16


.........

Test 1.c success

success

Return code = 0

Launching the linker/assembler...
C:\Program Files\Matrix Multimedia\Flowcode V4\BoostC\boostlink.pic.exe -ld "C:\Program Files\Matrix Multimedia\Flowcode V4\BoostC\lib" libc.pic16.lib flowcode.pic16.lib rand.pic16.lib float.pic16.lib "Test 1.obj" -t PIC12F629 -d "C:\Program Files\Matrix Multimedia\Flowcode V4\Tools\PPP" -p "Test 1"
BoostLink Optimizing Linker Version 6.95
http://www.sourceboost.com
Copyright(C) 2004-2009 Pavel Baranov
Copyright(C) 2004-2009 David Hobday


Caution: argument of 'delay_us' calls must have a value of 1 or more
Caution: Delay inaccurrate: 'delay_us', Delay overhead:0.01ms, Unit delay:0.001ms, Delay resolution:4 units
Warning unreferenced functions removed:
FCI_FLOAT_TO_STRING in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
FCI_NUMBER_TO_HEX in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
FCI_STRING_TO_INT in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
FCI_STRING_TO_FLOAT in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
Wdt_msDelay in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
Wdt_Delay_S in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
Wdt_Delay_Ms in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
isinf in: C:\Program Files\Matrix Multimedia\Flowcode V4\FCD\internals.h
FCD_SWITCH0_ReadState in: C:\Program Files\Matrix Multimedia\Flowcode V4\Tools\PPP\Test 1.c

Building CASM file
Memory Usage Report
===================
RAM available:64 bytes, used:36 bytes (56.3%), free:28 bytes (43.7%),
Heap size:28 bytes, Heap max single alloc:27 bytes
ROM available:1024 words, used:145 words (14.2%), free:879 words (85.8%)



success

Return code = 0

Launching the programmer...
C:\Program Files\Matrix Multimedia\Common\PPPv3\PPPv3.exe -cs 2 -chip PIC12F629 -nogui "Test 1.hex"
Sending program...
Saving OSCCAL
Erasing the PICmicro

................

Writing program memory
Writing configuration memory
Writing id-locations
Reading program memory
Reading configuration memory
Finished reading PICmicro contents
Programming failed: <config1>
That took 7.953 seconds

Return code = 0

FINISHED

pic-newbie

Re: V4 cannot ID my chip on compiling..

Post by pic-newbie »

Apologies for the bump but I have not yet been able to resolve this, can anyone offer any assistance at all ?

medelec35
Matrix Staff
Posts: 9521
Joined: Sat May 05, 2007 2:27 pm
Location: Northamptonshire, UK
Has thanked: 2585 times
Been thanked: 3815 times

Re: V4 cannot ID my chip on compiling..

Post by medelec35 »

If you get a pop-up saying 'can't ID on-board chip' then programming data via USB is not getting to chip or Power Supply is wrong voltage (too low)
Don't forget to plug-in recommended power supply to programmer otherwise will not program chip. My programmer works 100% OK with 12V Regulated supply, but if you used a 12V unregulated supply then voltage out would be higher than 12V and nearer to recommended 14V. If you are not sure then would assume a 14V Power supply can be purchased direct form matrix. But if you not got a power supply plugged in, then on-board green LED will not be on and you will get a separate pop-up stating no power to chip during programming.

My drivers are dated: 19/12/2007
When I install software for my E006 programmer:
1st I downloaded latest ppp from
http://www.matrixmultimedia.com/software/PPPv3.exe
I found this by going to the main page of http://www.matrixmultimedia.com and followed links For Eblocks hardware.
Then Install ppp
Now plug in programmer to USB
With some windows operating system you need to manually install drivers by using 'Browse my computer for drivers software'
then Browse to C:\Program Files\Matrix Multimedia\Common\PPPv3\Driver (or if using 64bit windows C:\Program Files (x86)\Matrix Multimedia\Common\PPPv3\Driver)


I did have a problem with programming my board at first, This was down to J12/J13/J14 (USB/ICD2) jumper being a tad Doggy. Just move it up/down slightly to make better contact. With a doggy jumper connection, the on-board yellow LED will still flash during programming, but signals will not reach chip.
Does the original chip that was on programmer program?
Important, only one chip can be on programmer at a time, this may sound obvious, but can be over looked if you are in a rush... over worked and stressed (like me :p) etc.
Also make sure J29 (PSU/USB is in PSU).
Hope this helps.
Martin

User avatar
Steve
Matrix Staff
Posts: 3434
Joined: Tue Jan 03, 2006 3:59 pm
Has thanked: 114 times
Been thanked: 422 times

Re: V4 cannot ID my chip on compiling..

Post by Steve »

The chip is being programmed, but the config value is failing when it is read back. It could be that the config word you are sending is inappropriate for that chip (e.g. it attempts to set certain config settings that are unimplemented in that chip). It could also be that the chip is damaged in some way.

It does not sound like a problem with the EB006 itself.

medelec35
Matrix Staff
Posts: 9521
Joined: Sat May 05, 2007 2:27 pm
Location: Northamptonshire, UK
Has thanked: 2585 times
Been thanked: 3815 times

Re: V4 cannot ID my chip on compiling..

Post by medelec35 »

pic-newbie wrote: I recieve an error when the programmer starts saying "Could not ID the onboard chip
Steve, would it still display error message, if it was just a config problem?
If was being programmed, then above message would not be displayed?
Not saying your wrong of course, Just showing "Could not ID the onboard chip", yet software stating it was programmed is contradicting and confusing?
Martin

User avatar
Steve
Matrix Staff
Posts: 3434
Joined: Tue Jan 03, 2006 3:59 pm
Has thanked: 114 times
Been thanked: 422 times

Re: V4 cannot ID my chip on compiling..

Post by Steve »

No - you're right, I missed that initial message. Then this looks to me like the wrong chip is in the board, it is damaged, or that 2 chips are in there at the same time.

I know that these chips do pose some problems to program, especially when they are set to use an internal MCLR and an internal clock. Try to identify the chip when the switch is in the XTAL or RC setting - one of these seems to give better results. There are also settings within the PPP options screen for raising the Vdd line before or after the MCLR line. Sometimes these can have an effect.

pic-newbie

Re: V4 cannot ID my chip on compiling..

Post by pic-newbie »

Thanks for your help guys, and apologies for the delay in geting back to you, had to attend to other things.

Taking your points in order;
Power is from a Matrix power supply, and has been tested and is ok.
I will be looking into the drivers' position later.
Have checked that all jumpers are in the correct positions, all OK. Have removed and re-inserted them several times.
Definitely only one chip at a time. (If I start plugging in two at a time then I will definitely give up this game)!
I am also replacing the USB Cable just to be sure.

One other observation, I'm using the internal oscillator on the 12F629 and the code reads:
"Sending Program"
"Saving OSCCAL"
"Erasing the PICmicro"

I belive that there should be more lines, giving the value of OSCCAL,and a line saying that the OSCCAL value has been re-inserted.
Is it posible that the OSCCAL Value has been permanently erased and this is giving me some of the problems?

.
I have taken all your points and had another session with the program and have managed to get a very simple program running on the internal clock.
I am going to play around and expand the set up to see if there are still problems and exactly where they are, then report back

Also when sending program to the chip, if you get a mesage "Configuration word(s) check failed" together with the note below it about PIC code protection: i.e. "NOTE: If the PIC is code-protected ...........even if the program has been sent correctly".
Does that mean that the program has failed or not? I find this comnunication a little ambiguous.

Thanks once again for the help

medelec35
Matrix Staff
Posts: 9521
Joined: Sat May 05, 2007 2:27 pm
Location: Northamptonshire, UK
Has thanked: 2585 times
Been thanked: 3815 times

Re: V4 cannot ID my chip on compiling..

Post by medelec35 »

Just had a thought, have you got any hardware plugged into your programmer, or connections from either +5V or 0V going to port B or chip via any free IC socket connections?
My line if though is if the lines used for programming are held at 0V or +5V then you will get Can not ID on board chip.
Martin

User avatar
Steve
Matrix Staff
Posts: 3434
Joined: Tue Jan 03, 2006 3:59 pm
Has thanked: 114 times
Been thanked: 422 times

Re: V4 cannot ID my chip on compiling..

Post by Steve »

Regarding the message "NOTE: If the PIC is code-protected ...........even if the program has been sent correctly"...

All this is saying is that the chip is being read back as different to the program that was sent, which is what it will read like if code protection is on. In this situation, the programming utility cannot confirm that the chip has been programmed correctly.

pic-newbie

Re: V4 cannot ID my chip on compiling..

Post by pic-newbie »

Hi guys, thanks for your continuing help, I think we have success.
We seem to have had two problems at the same time.
First, one of my USB ports does not see the programming board and
Second,I have Removed the tick from "Use IncX Cmd" box in the USB options window;
(I was advised to do this when I had problems with Flowcode3).
Have changed ports and unticked the above and am now in buisness.
Thanks once again.

PS: Is there anywhere a description of what does what in the Config menus of flowcode? For instance your comment about
manipulating Vdd? Obviously it must be useful but a few lines on why would be helpful. Also while I am on the subject,
I have looked at the "An Intruduction to Microcontroler programing" CD. It tackles the basics but would it not be a good idea
to cover AtoD, DtoA, PWM, etc etc, I feel that a little more help in the learning area would pay off in less questions in the forum.

pic-newbie

User avatar
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: V4 cannot ID my chip on compiling..

Post by Benj »

Hello

The chip configurations are explained in the device datasheet under configuration settings. A to D and PWM are very simple once you get to grips with them. Have a play around with the macros and properties available. The component help files should also shine some light onto their usage.

Post Reply