Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
127 views4 pages

Historycal Flowcode

This release note summarizes updates made to the PPPv3 programming software over multiple releases from versions 3.1 to 3.4. Key points include: 1) Added support for numerous new microcontroller devices with each release. 2) Addressed some known issues like incorrect voltage readings and autodetection problems. 3) Version 3.4 added support for new firmware and much improved programming times. 4) Other updates removed registration requirements and implemented changes for compatibility with Flowcode software.

Uploaded by

Jo Di
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
127 views4 pages

Historycal Flowcode

This release note summarizes updates made to the PPPv3 programming software over multiple releases from versions 3.1 to 3.4. Key points include: 1) Added support for numerous new microcontroller devices with each release. 2) Addressed some known issues like incorrect voltage readings and autodetection problems. 3) Version 3.4 added support for new firmware and much improved programming times. 4) Other updates removed registration requirements and implemented changes for compatibility with Flowcode software.

Uploaded by

Jo Di
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 4

PPPv3.

1 Release Notes ===================== Known issues -----------* (v3 dev board & v3 Multiprogrammer E-Block only) Changing the PSU/USB jumper setting "on the fly" sometimes puts the USB connection into a "stuck" state and PPPv3 will seem to hang. To rectify this problem, disconnect and reconnect the USB cable to reset the USB connection. * (v3 dev board & v3 Multiprogrammer E-Block only) A very specific set of circumstances could cause auto-id, erase or programming failures when using a 16F87 or 16F88 device. The set of circumstances are: (a) The board is in XT mode (b) The 16F88 cfg word has previously been set to use an internal MCLR (c) The 16F88 is currently running a program that sets RB6 or RB7 as high o/p's The error message could be one of a number of different messages (e.g. "Could not ID the device", "Device has not been erased", "Please select device from the following ID: 0x00FF"). The simplest solution is to: (1) Set the board to RC mode (2) Attempt to reprogram the device (3) Reset the board to XTAL mode * The program-entry method for chips 12F615, 12F609, 16F616 and 16F610 may not be autodetected the first time. Either program for a second time, or select "R aise Vdd after Vpp" from the options screen. v3.11.15.30 ----------Date: 28/10/2009 * Support for many more chips added v3.10.14.28 ----------Date: 21/05/2009 * Support for many more chips added * Removed support for V1 and V2 development boards * It is now ok to continue downloading to the device when the cable was initial ly unplugged

v3.9.12.26 ---------Date: 12/06/2006

* Added support for these chips: - 12F609, 12F615 - 16F610, 16F616, 16F639, 16F677, 16F685, 16F687, 16F689, 16F690 - 16F785 - 16F883, 16F884, 16F886, 16F887 - 16F913, 16F914, 16F916, 16F917, 16F946 - 18F1230, 18F1231, 18F1330, 18F1331 - 18F2221, 18F2321, 18F2423, 18F2450, 18F2480, 18F2523, 18F2580, 18F2682, 18 F2685 - 18F4221, 18F4321, 18F4423, 18F4450, 18F4480, 18F4523, 18F4580, 18F4682, 18 F4685 - 18F6527, 18F6622, 18F6627, 18F6722 - 18F8527, 18F8622, 18F8627, 18F8722 * Made shorter strings in cfg file and lengthened config screen * NTPORT now gets called only when LPT board is selected * Simple config screen defaults to Watchdog=off v3.8.11.24 ---------Date: 06/06/2006 * Removed registration nag screen * Features reserved for registered users are now available as standard v3.7.10.23 ---------Date: 04/04/2006 * Various changes for FlowCode v3: - implemented a "nogui" mode - config data passed between FC and PPP using common registry location (if " fromFlowCode" is set) - messages now also written to stdout v3.6.9.22 --------Date: 15/03/2006 * Fixed erroneous low-voltage reading when using latest Matrix hardware * Fixed minor exception when changing between XTAL and RC oscillator modes v3.5.8.21 --------Date: 11/10/2005 * Added support for version 7+ firmware (v2.2) * New 'v5' multiprogrammer board supported (with higher potential divider resis tances)

* Tidied up a few errors regarding USB cable unplugs and low voltage readings

v3.4.7.19 --------Date: 08/09/2005 * Added support for version 6+ firmware (v2.1) [i.e. new 'C' firmware] * Option to upgrade firmware for on-the-fly updates * Much improved programming times (using new firmware) * Removed support for legacy 'C' OTP devices * Unresolved issue: 18F devices still take a while to program - this should be fixed in the next release.

v3.3.6.16 --------Date: 01/03/2005 * Added support for the following devices: - PIC18F2410, PIC18F2420, PIC18F2455, - PIC18F2510, PIC18F2520, PIC18F2550 - PIC18F4410, PIC18F4420, PIC18F4455, PIC18F4510 - PIC18F6310, PIC18F6390, PIC18F6625, PIC18F6721 - PIC18F8310, PIC18F8390, PIC18F8625, PIC18F8721 * Support for firmware Vdd switching (>= v4) on new USB boards - including option to specify Vdd raise timing - also added LVP scripts for Vdd switching * Implemented "simple" mode configuration screen for popular chips * Warning when programming MCLR internal to avoid problems on older hardware * Removed "obj" file reference from open dialog * Added support for V3 Dev Board v3.2.5.13 --------* Added support for the following devices: - PIC12F683 - PIC12F635 - PIC16F636 * New "Erase with Vdd Msg" button in the debug screen to allow chips with "internal MCLR / RB6" issue to be erased. v3.1.4.12 --------* Major revision of PPP - it is now compatible with most PIC18F devices

You might also like