Page 1 of 1
16F913
Posted: Sun Apr 01, 2007 8:43 am
by peter_w
When i can use 16F913 in flowcode?
Posted: Sun Apr 01, 2007 2:51 pm
by Camusensei
1) speak english
2) what do you mean?
3) you can always use this pic in flowcode if you have got the right version of flowcode
Posted: Sun Apr 01, 2007 4:19 pm
by peter_w
sorry, my english not so good. I 'm new in flowcode. now i'm using flowcode V3(pro license), but i don't see this device in device list. How can i do if i want to develop program for 16F913 with this software? please suggest me.
Posted: Sun Apr 01, 2007 4:35 pm
by saschech@gmx.de
Camusensei wrote:1) speak english
2) what do you mean?
3) you can always use this pic in flowcode if you have got the right version of flowcode
hahaha.........
Posted: Sun Apr 01, 2007 4:48 pm
by Camusensei
sorry but the only pics supported by flowcode are these ones in the 16FXXX serie :
PIC16F627A, PIC16F627, PIC16F628A, PIC16F628,
PIC16F630, PIC16F648A, PIC16F676, PIC16F684,
PIC16F688, PIC16F636, PIC16F716, PIC16F72,
PIC16F737, PIC16F73, PIC16F747, PIC16F74,
PIC16F767, PIC16F76, PIC16F777, PIC16F77,
PIC16F818, PIC16F819, PIC16F83, PIC16F84A,
PIC16F84, PIC16F870, PIC16F871, PIC16F872,
PIC16F873A, PIC16F873, PIC16F874A, PIC16F874,
PIC16F876A, PIC16F876, PIC16F877A, PIC16F877,
PIC16F87, PIC16F88
sorry
Posted: Mon Apr 02, 2007 9:03 am
by Steve
The next update of Flowcode will support this chip. We should release an update in the next few weeks, which will contain some bug fixes and the following new features:
Support for these chips:
- 12F609, 12F615, 16F610
- 16F913, 16F914, 16F916, 16F917
- 18F2423, 18F2523, 18F2682
- 18F4423, 18F4523, 18F4682
New components:
- PWM
- LIN Master and Slave
- I2C
New languages:
- Romanian
- Danish (hopefully)
The current release of Flowcode also supports the 16F88x family and a few others that are not listed in Camusensei's post.
I2C
Posted: Mon Apr 02, 2007 11:26 pm
by MarcB
Why is I2C written in a other color? is it 100% sure that it's in the next update? can we choose the pins for SDA and SCL ourself or is it in the program?
Posted: Tue Apr 03, 2007 8:33 am
by Steve
My current plan is to release the next update once the I2C component has been completed.
I'm not sure whether it will be a hardware or software implementation of I2C, so it's too early to say if you'll be able to define your own pins. Would you prefer to have a software implementation that allowed you to choose the pins?
I2C
Posted: Tue Apr 03, 2007 8:36 am
by MarcB
Mostly the pins are set to port C, but when you need 3 x 8 ports, there is a problem.... so its happy when we can take our own pins....
Posted: Tue Apr 03, 2007 10:07 am
by Mark
Hi Steve,
One consideration is the I2C bus speed. Historically with 400kHz or even 100kHz bus I2C software has plenty of time, however with the 1MHz devices (which will increasingly become the norm) then a 20MHz crystal giving a 20/4 instruction cycle time or even a 4MHz crystal giving a 4/4 = 1 us cycle time starts to make the coding time limiting. Add to this that an application may include an ADC acquistion and store then the opportunity to do any work with even audio signal waveforms starts to look difficult.
regards,
Mark
(ps there is a bug in the I2C write macro where I used FCV_SEND for sending the byte to write, when it should have been FCL_DATA for properly transportable code using the parameter brought in by the Macro)