Matrix user forums

The file for pic16F1827 is "PIC_ADC_23.c" in the "Component" Folder.
I attached my file, which is changed to work.

You can solve this problem with this workaround:
http://www.matrixmultimedia.com/mmforum ... =29&t=8746

@2: I cant' help.

@1: You have to set the clockspeed in a "C-Code"-block manually. In the Datesheet on Page 67 you will see the correct dataword(s).

There are diffrent ways:
ssop:
http://de.farnell.com/wells-cti/656c1202215-001/sockel-smd-ssop-nullsteckkraft/dp/9897623
sop:
http://de.farnell.com/wells-cti/652d0202215/sockel-ic-sop-20pole/dp/9897658
http://de.farnell.com/3m/923665-28/stecker-soic-ic-test-clip/dp/1654361
http://de.farnell.com/3m ...

Jes, I think the problem start at
#define ADRES 0x009B
#define ADRESL 0x009B
#define ADRESH 0x009C
in ..\boostc\include\pic16F1xxx.h
It seems that ADRES should used as an integer for AdresL+AdresH, but Flowcode use only AdresL.

I found a short and nice solution.
I looked at the "UserCode" from ReadAsInt ans ReadAsByte and changed the code from the 1827/1936-Code
short iRetVal;
SampleADC();
#ifdef _BOOSTC
#ifdef ADRES
iRetVal = (adres << 2);
#else
iRetVal = (adresh << 2);
iRetVal = iRetVal | (adresl >> 6);
#endif ...

The results of measuring was wild numbers.

When the numbers jump from 64 - 128 - 192 in "ReadAsByte" and 256 - 512 - 768 in "ReadAsInt", I have the same problem with PIC16F1827 and PIC16F1936.Maybe the problem is the left-right justify or the new Bit's in ADCON0 and ADCON1.

Thanks for the solution.

Hi Jan.
When your posted asm-file is ok, taht will be the reasen getting no problem.
That you have to use a project is corrcet. Without a project and a workingspace you are not able to compile a file.

I remeber another problem I had in the past after changing the ASM-Code.
BoostC create ASM-Code ...

Is it possible to compile a Flowcode-C-file in MPLab using the BoostC compiler? I wont use the "Flocode-BoostC". When my intention will work, I am goining to buy my own BoostC licence.
The reasen is to learn C with the advantage of Flowcode. The C-Code-Block is not as nice as a real C-Code ...

I make a Flowchart with PIC16F1936 and read and write a value out of and into eeprom, but there is a problem:
...
eeprom.c
Starting preprocessor: c:\PROGRA~1\MATRIX~1\FLOWCO~2\boostc\pp.exe eeprom.c -i c:\PROGRA~1\MATRIX~1\FLOWCO~2\boostc\include -d _PIC16F1936 -la -c2 -o eeprom.pp -v -d _BOOSTC -d ...

Hi Jan.
The Error shown in the screenshot say's that there is no "END" at the and of the file (ERORR[129]). At the moment I don't know why because there is an "END". I compiled your asm in MPLab 8.60 and 8.73a and it worked without any problem.
Maybe there is a problem in your projekt, please ...

If you post a screenshot of the error maybe it is possible to say what is wrong.
Which version of MPlab you have installed?
In 8.x there is a new option for absolut or relcoatible Code. Here you have to use the "Absolut"-Code with a flowcode asm-file. When you are not sure which option you use look ...

When I read youre posted c-code I read this:
main{
configuration,
watchdog reset,
puls,
sleep
Loop without watchdog reset (mainendloop: goto mainendloop;)
}
Your Program runs one time, the PIC begins to sleep, the watchdog let the PIC wakeup after ~2.3s but now there is now jump and the PIC runs ~2 ...

[...one month later...]
Are you now poosible to say something about the release date?
I want to use the new PIC16F1Xxx but the HiTechC-Workaround is not the right solution for my projekts.

I have a problem using the PIC16F506 in Flowcode 3.6.11.53.

It is not available . But I think it was in previous versions.

If I choose a PIC16F505 alternatively , I get an error-message, that the FCD is missing or has an error.

But anyway, it seems to work with the c-code

IΒ΄m using a PIC16F818 and I reset the watchdog every few steps with a c-code "clear_wdt();" . I realize delays with loop and a 1ms delay and in the loop also the c-code for the watchdog reset. but I will try to bring in your idea in my initialization

A few versions ago there was a Problem concerning the frequency and the LCDΒ΄s:

http://matrixmultimedia.com/mmforums/viewtopic.php?t=1548&view=next

This Problem is solved in Version 3.2.2. But now the watchdog stops the program. I just compiled an old ( working) program again with the new version ...

Thanks for the answere. Is there another way to configure this chip ? I program the "source code" with Flowcode, then I compile it and put it via Mplab into the chip

I have a problem with a PIC16F631. It is not possible for me to configure this chip in PPP. If I try it, I get the remark "Unrecognised chip on command line: <PIC16F631>" and there is also no possibility to chose this chip in PPP.

IΒ΄m using:

Flowcode: 3.2.1
PPP: 3.9.12.26

Hello,
I tried your solution. but it is not working for me.

I got an error-message:

error: unknown identifier 'clr_wdt'
error: failed to generate expression


Can you help me to reset the watchdog.

Wow I can reset the watchdog in flowcode, or how I can bring in the clrwdt-command into flowcode ?

Hi,
I have exactly the same problem, using a PIC16F716 with an AV1624 LCD in combination with a 4MHz or 2MHz quartz. If I adjust the frequency on the same value as the quartz has, no matter if it is a 4 MHz or a 2MHz, the LCD is not working. If I adjust it on a different value it works with both ...

How can I realise an analogue input in Flowcode 3.1.0.31 for the PIC16F716. I tried it with an ADC and two component macros ( 1. Sample ADC 2. ReadAsByte) and the simulation was running very well, but when I tried to compile it I got the error message:


D:\Eigene Dateien\Flow\An In\An In.c(77:9 ...