Matrix user forums

OK, I am very new so I appologize for my lack of knowledge. I am programming a simple LED blinker, and it simulates just fine in flowcode. I have a 16f677 in the EB006 (8) but when I compile it seems to compile OK to C and ASM then when launching the programmer it pops up the chip config page, I hit autodetect, then OK, and it seems to top there with a return code 0. It does not appear to be programming the chip, as the output pin does not go high/low as I would expect. I am certain this is a user error and am hopeful someone can help me diagnose what step/config I am missing to enable me to get started programming. Thanks for your patience and assistance.


Compiler options: -v -t PIC%p "%f.c"

Programmer options: -cs 2 -chip PIC%p -config

Compiler messages below in the event this assists in diagnosing my problem:

File name: C:\Users\JM\16F677blinker.c
Title:
Description:
Generated by: Flowcode v5.4.0.0
Date: Saturday, February 09, 2013 11:19:26
Licence: Student
Registered to: Jeff XXXXX
Licence key: XXXXXX
NOT FOR COMMERCIAL USE
http://www.matrixmultimedia.com
Launching the compiler...
C:\Program Files (x86)\Flowcode\v5\Tools\boostc\boostc_pic16_flowcode.exe -v -t PIC16F677 "16F677blinker.c"
BoostC Optimizing C Compiler Version 7.04 (for PIC16 architecture)
http://www.sourceboost.com
Copyright(C) 2004-2011 Pavel Baranov
Copyright(C) 2004-2011 David Hobday

Licensed to FlowCode User under Single user Standard License for 1 node(s)
Limitations: PIC12,PIC16 max code size:4096 words, max RAM banks:Unlimited, Non commercial use only


16F677blinker.c
Starting preprocessor: C:\PROGRA~2\Flowcode\v5\Tools\boostc\pp.exe 16F677blinker.c -i C:\PROGRA~2\Flowcode\v5\Tools\boostc\include -d _PIC16F677 -la -c2 -o 16F677blinker.pp -v -d _BOOSTC -d _PIC16 -d _CHAR_INDEX


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

16F677blinker.c success

success
Return code = 0
Launching the linker/assembler...
C:\Program Files (x86)\Flowcode\v5\Tools\boostc\boostlink_pic.exe -ld "C:\Program Files (x86)\Flowcode\v5\Tools\BoostC\lib" libc.pic16.lib rand.pic16.lib float.pic16.lib "16F677blinker.obj" -t PIC16F677 -d "C:\Users\JM" -p "16F677blinker"
BoostLink Optimizing Linker Version 7.03
http://www.sourceboost.com
Copyright(C) 2004-2011 Pavel Baranov
Copyright(C) 2004-2011 David Hobday


Warning unreferenced functions removed:
FC_CAL_Port_Out__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_Out_DDR__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_In__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_In_DDR__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
Wdt_Delay_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
Wdt_Delay_Ms in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_US in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_MS in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINTWDT_MS in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINTWDT_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_GETCHAR in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_GETLENGTH in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_MIDSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_LEFTSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_RIGHTSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOLOWER in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOUPPER in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_COMPARE in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_FLOAT_TO_STRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_NUMBER_TO_HEX in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRING_TO_INT in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRING_TO_FLOAT in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRREV in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRMOV in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_SHEAD in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_SCOPY in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
isinf in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_round in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_floor in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_ceil in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c

Building CASM file
Memory Usage Report
===================
RAM available:128 bytes, used:36 bytes (28.2%), free:92 bytes (71.8%),
Heap size:92 bytes, Heap max single alloc:59 bytes
ROM available:2048 words, used:126 words (6.2%), free:1922 words (93.8%)



success
Return code = 0
Launching the programmer...
C:\Program Files (x86)\Flowcode\v5\Tools\PPP\PPPv3.exe -cs 2 -chip PIC16F677 -config

................Return code = 0

FINISHED

Hi Jeff,
A common thing that prevents a program from ruining on your target device is the configuration settings.

Take a look here:
http://www.matrixmultimedia.com/mmforum ... =26&t=6936

If you still need help then if you post your Flowchart (file ends in .fcf ) Then we can check it out for you.

Martin

I have reviewed the common config issues (Thanks Martin!). I have verified Vdd and Vss at the chip, have chosen 20mhz and HS selected on the oscillator, MCLR is internal, and the rest of the configurable options disabled. I don't have LVP on the 16f677 so I don't believe that is an issue (although tried with external power to the EB006 as well). Given the proper compilation to c and asm/hex, but what appears an aborted programming of the chip I beleive it must be my PPP or settings at this point.

I am trying to upload the flowchart. Here is the c. Does anyone else have this sort of problem?

//************************************************************************************
//**
//** File name: C:\Users\JM\16F677blinker.c
//** Title:
//** Description:
//**
//** Generated by: Flowcode v5.4.0.0
//** Date: Saturday, February 09, 2013 13:36:07
//** Licence: Student
//** Registered to: Jeff x
//** Licence key: x
//**
//**
//** NOT FOR COMMERCIAL USE
//**
//** http://www.matrixmultimedia.com
//**
//************************************************************************************


#define MX_PIC

#define MX_USES_UINT8 1
#define MX_USES_SINT16 0
#define MX_USES_CHAR 0
#define MX_USES_FLOAT 0
#define MX_USES_SINT32 0
#define MX_USES_BOOL 1
#define MX_USES_UINT16 0
#define MX_USES_UINT32 0
//Defines for microcontroller
#define P16F677
#define FC_CAL_PIC
#define MX_ADC
#define MX_ADC_TYPE_3
#define MX_ADC_BITS_10
#define MX_EE
#define MX_EE_SIZE 256
#define MX_SPI_1
#define MX_SPI_1_MISO_PORT portb
#define MX_SPI_1_MISO_TRIS trisb
#define MX_SPI_1_MISO_PIN 4
#define MX_SPI_1_MOSI_PORT portc
#define MX_SPI_1_MOSI_TRIS trisc
#define MX_SPI_1_MOSI_PIN 7
#define MX_SPI_1_CLK_PORT portb
#define MX_SPI_1_CLK_TRIS trisb
#define MX_SPI_1_CLK_PIN 6
#define MX_SPI_1_SS_PORT portb
#define MX_SPI_1_SS_TRIS trisb
#define MX_I2C
#define MX_MI2C
#define MX_I2C_1
#define MX_I2C_1_SDA_PORT portb
#define MX_I2C_1_SDA_TRIS trisb
#define MX_I2C_1_SDA_PIN 4
#define MX_I2C_1_SCL_PORT portb
#define MX_I2C_1_SCL_TRIS trisb
#define MX_I2C_1_SCL_PIN 6

//Functions
#define MX_CLK_SPEED 20000000
#ifdef _BOOSTC
#include <system.h>
#endif
#ifdef HI_TECH_C
#include <pic.h>
#endif

//Configuration data
#ifdef _BOOSTC
#pragma DATA 0x2007, 0x30d2
#endif
#ifdef HI_TECH_C
__CONFIG(0x30d2);
#endif

//Internal functions
#include "C:\Program Files (x86)\Flowcode\v5\FCD\internals.c"

//Macro function declarations


//Variable declarations
#define FCV_TRUE (1)
#define FCV_FALSE (0)



#include "C:\Program Files (x86)\Flowcode\v5\CAL\includes.c"

//Macro implementations



void main()
{
//Initialization
ansel = 0;
anselh = 0;


//Interrupt initialization code
option_reg = 0xC0;


//Loop
//Loop: While 1
while (1)
{

//Delay
//Delay: 1 s
delay_s(1);

//Output
//Output: 1 -> B6
trisb = trisb & 0xBF;
if ((1))
portb = (portb & 0xBF) | 0x40;
else
portb = portb & 0xBF;

//Delay
//Delay: 1 s
delay_s(1);

//Output
//Output: 0 -> B6
trisb = trisb & 0xBF;
if ((0))
portb = (portb & 0xBF) | 0x40;
else
portb = portb & 0xBF;


}

mainendloop: goto mainendloop;
}

void MX_INTERRUPT_MACRO(void)
{
}

Hi Jeff,
your welcome.

We need to get you up and running ASAP
Is suggesting chip is being programmed just fine


I should not make a lot of difference at this stage but if using a Eb006 programmer they have a 19.6609MHz crystal so you will need to select 19660800 Hz

I believe it could be an issue with your hardware?

If you look at your programmer data sheet:
http://www.matrixmultimedia.com/product.php?Prod=EB006
(page 10 ) , your see that port B1 is not supported with 20pin devices in fact a few of portB connections are different.
So I would recommend changing from port B1 to portC1.

If that fails then check your programmer hardware settings.

The important things to check are:

1) Jumper on J18&J10 (next to crystal) is at the side for OSC (side of ICSP header)
2) Switch the other side of the crystal is set on XTAL

Perhaps check to see if jumper is making good contact. lift it a fraction.

If all this fails then if you post your .hex file and flowchart. I can check it out for you.

Martin

OK, still trying. Just to rule out your astute 20 pin issues, I switched to the PIC18f1220 (just to be sure it wasn't that or a bad PIC). I have verified I am on XTAL and the jumpers are as noted. I know you said that the return code 0 after launching the programmer means it is getting to the chip but I still have my doubts there. It stops instantly after I hit OK on the chip configuration window that pops up. I thought I would see some verification/validation once it is programmed in the compiler window as well. Just in case it helps diagnose the issue:
Compiler options -v -t PIC%p "%f.c" (Boost C)
C:\Program Files (x86)\Flowcode\v5\Tools\boostc\boostc_pic18_flowcode.exe (location)
I suspect the compiler is working just fine though.

Programmer Options -cs 2 -chip PIC%p -config
C:\Program Files (x86)\Flowcode\v5\Tools\PPP\PPPv3.exe (location)

Using external program to set configuration options (checked)
C:\Program Files (x86)\Flowcode\v5\Tools\PPP\PPPv3.exe
-cs 2 -chip PIC%p -config

The eb006 (8) can autodetect the chip so it appears to be operational at least to that point. I am not plugging it in and powering it from the USB only. (Could this be LVP issues?)

Here is the compiler output, but I think it is materially the same as previously posted.

File name: C:\Users\JM\18f1220blinker.c
Title:
Description:
Generated by: Flowcode v5.4.0.0
Date: Sunday, February 10, 2013 14:11:02
Licence: Student
Registered to: Jeff Mxxx
Licence key: 7xxxx
NOT FOR COMMERCIAL USE
http://www.matrixmultimedia.com
Launching the compiler...
C:\Program Files (x86)\Flowcode\v5\Tools\boostc\boostc_pic18_flowcode.exe -v -t PIC18F1220 "18f1220blinker.c"
BoostC Optimizing C Compiler Version 7.04 (for PIC18 architecture)
http://www.sourceboost.com
Copyright(C) 2004-2011 Pavel Baranov
Copyright(C) 2004-2011 David Hobday

Licensed to FlowCode User under Single user Standard License for 1 node(s)
Limitations: PIC18 max code size:16384 bytes, max RAM banks:Unlimited, Non commercial use only


18f1220blinker.c
Starting preprocessor: C:\PROGRA~2\Flowcode\v5\Tools\boostc\pp.exe 18f1220blinker.c -i C:\PROGRA~2\Flowcode\v5\Tools\boostc\include -d _PIC18F1220 -la -c2 -o 18f1220blinker.pp -v -d _BOOSTC -d _PIC18 -d _CHAR_INDEX


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

18f1220blinker.c success

success
Return code = 0
Launching the linker/assembler...
C:\Program Files (x86)\Flowcode\v5\Tools\boostc\boostlink_pic.exe -ld "C:\Program Files (x86)\Flowcode\v5\Tools\BoostC\lib" libc.pic18.lib rand.pic18.lib float.pic18.lib "18f1220blinker.obj" -t PIC18F1220 -d "C:\Users\JM" -p "18f1220blinker"
BoostLink Optimizing Linker Version 7.03
http://www.sourceboost.com
Copyright(C) 2004-2011 Pavel Baranov
Copyright(C) 2004-2011 David Hobday


Caution: Delay inaccurrate: 'delay_ms', Delay overhead:0ms, Unit delay:1.00016ms, Delay resolution:1 units
Warning unreferenced functions removed:
FC_CAL_Port_Out__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_Out_DDR__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_In__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
FC_CAL_Port_In_DDR__x in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_IO.c
Wdt_Delay_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
Wdt_Delay_Ms in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_US in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_MS in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINTWDT_MS in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINT_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_DELAYINTWDT_S in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Delay.c
FCI_GETCHAR in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_GETLENGTH in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_MIDSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_LEFTSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_RIGHTSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOSTRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOLOWER in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_TOUPPER in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_COMPARE in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_FLOAT_TO_STRING in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_NUMBER_TO_HEX in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRING_TO_INT in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRING_TO_FLOAT in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRREV in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_STRMOV in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_SHEAD in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
FCI_SCOPY in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_String.c
isinf in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_round in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_floor in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c
flt_ceil in: C:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_Float.c

Building CASM file
Memory Usage Report
===================
RAM available:256 bytes, used:38 bytes (14.9%), free:218 bytes (85.1%),
Heap size:218 bytes, Heap max single alloc:127 bytes
ROM available:4096 bytes, used:290 bytes (7.1%), free:3806 bytes (92.9%)



success
Return code = 0
Launching the programmer...
C:\Program Files (x86)\Flowcode\v5\Tools\PPP\PPPv3.exe -cs 2 -chip PIC18F1220 -config

......Return code = 0

FINISHED

I have a pickit 3 but want to get this EB006 board operational before trying that as a workaround. I can't imagine the EB006 is defective this is certainly my own operator error. I appreciate any assistance you can provide.

Hornet125 wrote: I am not plugging it in and powering it from the USB only.

If your not using an external PSU then have you got USB/PSU Jumper connected to USB?

Personaly I believe it would be better to power EB006 via an external PSU so Eblocks connected to programmer. e.g LED or LCD eblock Eblock are powered from external PSU rather then 5V usb from PC.
If that was the case then Jumper has to be on PSU and not PSU,

Have you got 5V across the power supply pins of your target device?

Also some of your configuration settings are wrong.
HS should be selecred for osc type.
Background debug and Low voltage programming should be disabled.

Try the attached file.

Well I may have solved part of my problem. First off, thank you very much. I opened the attached and ran it, with the same results however. In poking around today I saw I could open PPPv3 directly and see what was actually on the chip. I could erase it, verify it was erased by looking at what was on it, then load the compiled hex file into PPP and send it to the chip, and verify it was on the chip. It seems to be Flowcode not properly using PPP on my setup that is stopping the automatic programming. I can manually do it in this manner point forward so at least I should be operational. I uninstalled and reinstalled PPP with no apparent change.

But this minor success of getting the hex file to the chip has me baffled, the PIC is not outputting the high on PIN 12-RB6 (multimeter not picking it up straight off the pin while in the EB006). I thought perhaps it was a impedence or multimeter thing so just in case I set it up on the breadboard driving a transistor controlled LED, but still no output (I did tie MCLR to high with a 100K). Verified 5V to the PIC. My head hurts at this point! But there was progress today manually using PPP so I'll declare a minor victory! I tried your HEX file as well to verify it wasn't my OSC setting. Thanks Martin! I really appreciate your assistance today. We are getting closer by knowing what it isn't! (EB006 works and is recognized by the computer as such, compiler works, PPP working manually, and the PIC can be erased/loaded with the hex file) I now just need to get Flowcode and PPP working together it appears and figure out why it isn't pumping out pulses (Windows 7, 64 bit Presario CQ57, dual intel celeron 1.5mhz 2g ram)

Hello,

You could try clicking Build -> Compiler options and then hitting the restore defaults button. This should hopefully reload all the settings for PPP and get them correct.

If not then you can find the correct settings here.

http://www.matrixmultimedia.com/support ... f=68&t=805

Much thanks to both Ben and Martin for getting this noob back up and running. It was the parameters for me on the programmer (-cs 2 -chip PIC%p -nogui "%f.hex") which somehow I lost the "-nogui" parameter, which I think occurred when I played with a picKit 3. In any case, I am back up and running and able to program away. I learned alot on the juorney and am grateful for your patience and assitance. Now... to transplant the PIC to a breadboard... getting there!