Nabble - PIC - [PIC]

Re: Audio recording in APR6008 chip With PIC16F877A.

2009-12-07T03:30:07Z

Victor,

The datasheet shows only 640 sectors, so your range is only 0x280, not
ox3ff. If you want to split that into three portions, they would have to
start at 0x000, 0x0d5, and 0x1ab.

You may want to look at the Current Device Status (CDS) Overflow and Illegal
Address flags to to help you see if either of those is a problem.

Good luck.

Richard

----- Original Message -----
From: "VICTOR PV" <juo.victor@...>
To: <piclist@...>
Sent: Sunday, December 06, 2009 11:34 PM
Subject: [PIC] Audio recording in APR6008 chip With PIC16F877A.

Hi all

I am developing an automatic bell system which records audio in
APR6008 and plays at predetermined time. The controller used in PIC16F877A.
I recorded audio in the APR6008 and played back. The problem is when
recording time increases early recorded area replaces with new data.

The datasheet of APR6008 shows that there is 10bits address for
the memory(out of total 15 bits, 5 bits reserved for future use.) So my plan
was to divide total 3FF range Divided into three portions. Since APR6008 can
store 8min audio, now each section will get 160 seconds. The starting
addresses for each section selected as 0x 000, 0x155, 0x2AA. I wrote code
with this addresses. Then address 0x2AA didn’t accepted by the device. Other
two portions recorded but over lapped. This problem is confusing me for some
days. If any body have idea please help. Thanks in advance.
Victor.
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Audio recording in APR6008 chip With PIC16F877A.

2009-12-06T20:34:05Z

Hi all

I am developing an automatic bell system which records audio in
APR6008 and plays at predetermined time. The controller used in PIC16F877A.
I recorded audio in the APR6008 and played back. The problem is when
recording time increases early recorded area replaces with new data.

The datasheet of APR6008 shows that there is 10bits address for
the memory(out of total 15 bits, 5 bits reserved for future use.) So my plan
was to divide total 3FF range Divided into three portions. Since APR6008 can
store 8min audio, now each section will get 160 seconds. The starting
addresses for each section selected as 0x 000, 0x155, 0x2AA. I wrote code
with this addresses. Then address 0x2AA didn’t accepted by the device. Other
two portions recorded but over lapped. This problem is confusing me for some
days. If any body have idea please help. Thanks in advance.
Victor.
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Any one has serial smart card programer interface schematic

2009-12-06T08:53:19Z

Any one has serial smart card programer interface schematic? I am doing a final project about read/write cryptogaphic smart card? I am a newbie so i want to know smart card schematic and principle of circuit. Please help me. So thanks thanks thanks!!!!!!!!!!!!!!!!!

Re: de facto standard for intel hex files produced by MPLAB?

2009-12-04T16:04:32Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 04 Dec 2009 11:00:29 -0300
Mauricio Giovagnini <maugiovagnini@...> wrote:

> Peter escribió:
> > Is the default setting for MPLAB hex output INHX32 ? which is
> > INHX8M with an opcode 04 record to select INHX32 ?
> >
> > thanks,
> >
> > Peter
>
>
> Peter, the default output of the LINKER (MPLINK) is INHX32,
> if you wish to use another one you have to specify it (via
> command line. ex using the parameter /aINHX8S or via the
> MPLAB IDE in your project settings, under the LINKER tabsheet).
>
> About the opcode 04, I don't undestand the question, can you
> repost it?
>

He means opcode 04 of the Intel HEX file format, not of the PIC
instruction set. Opcode 4 is the "extended linear address record" type
code, which is used to provide the upper 16 bits of a 32-bit address
and is used in I32HEX but not I16HEX.

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: GnuPT 2.7.2

iEYEARECAAYFAksZo4gACgkQXUF6hOTGP7flGwCdG9tkqhf8p+rRw/FypQ3yLFO2
d2EAoJOHQsuwe+ADLDBP+pGYvzoZaHqm
=4mqY
-----END PGP SIGNATURE-----
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

RE: increase pic program flash memory size ? possible ?

2009-12-04T09:41:53Z

> -----Original Message-----
> From: piclist-bounces@... [mailto:piclist-bounces@...] On
Behalf
> Of cllow2020
> Sent: 04 December 2009 15:32
> To: Microcontroller discussion list - Public.
> Subject: Re: [PIC] increase pic program flash memory size ? possible ?
>
> thanks jinx,

<snip>

> an0_value=(an0_value/10)*2441 / 1000 //: get back reading in mv
range

> an1_value=(an1_value/10)*2441 / 1000
> an2_value=(an2_value/10)*2441 / 1000
> an3_value=(an3_value/10)*2441 / 1000
>
> an4_value=(an4_value/10)*2441 / 1000 *16 //: get back reading in mv
> range
> and 16x
> an5_value=(an5_value/10)*2441 / 1000 *16
> an6_value=(an6_value/10)*2441 / 1000 *16
> an7_value=(an7_value/10)*2441 / 1000 *16
> --

You would probably save a useful amount of program memory if you can put
the ADC values into an array and iterate through them in a loop rather
than calculating each one explicitly.

Also assuming you are using integers in the calculations you could save
a little more memory and improve speed by scaling the constants to avoid
the two divide/multiply operations e.g.

an0_value=(an0_value/10)*2441 / 1000

can be reduced to

an0_value=(an0_value * 125) / 512

and
an4_value=(an4_value/10)*2441 / 1000 *16

can be reduced to
an4_value=(an4_value * 125) / 8192

If your compiler is smart enough the divisions will be reduced to shift
operations, or you could do them explicitly.

These are not exactly equivalent; the scaling factor is 0.2441 in the
original and 0.244140 in the optimised version, giving an error of
0.016% which is probably insignificant compared to component tolerances
(scaling resistors and voltage reference for ADC. This gives a maximum
error in the reported value of 1mv.

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-04T07:31:38Z

thanks jinx,
you lightup my mind, below my optimize sample coding after modified, looks
better now, and i like the idea of 'moving averages' but difficult to added
in.,

8 analog split in 2 groups,
Group_A : ext_vref=2.5v, 2.441mV/step, measure range 0~2.5v..
Group_B : ext_vref=2.5v, (2.441mV*16)/step, measure range up to 40v
@ 39.056mv / step , use devided resister 150k//10k..

for i=1 to 10
raw_value=adc_read(an0) //: sub call, multiplx and select
an0, read value put in raw_value
an0_value=an0_value+raw_value
raw_value=adc_read(an1)
an1_value=an1_value+raw_value
raw_value=adc_read(an2)
an2_value=an2_value+raw_value
raw_value=adc_read(an3)
an3_value=an3_value+raw_value

raw_value=adc_read(an4)
an4_value=an4_value+raw_value
raw_value=adc_read(an5)
an5_value=an5_value+raw_value
raw_value=adc_read(an6)
an6_value=an6_value+raw_value
raw_value=adc_read(an7)
an7_value=an7_value+raw_value
next i

an0_value=(an0_value/10)*2441 / 1000 //: get back reading in mv range
an1_value=(an1_value/10)*2441 / 1000
an2_value=(an2_value/10)*2441 / 1000
an3_value=(an3_value/10)*2441 / 1000

an4_value=(an4_value/10)*2441 / 1000 *16 //: get back reading in mv range
and 16x
an5_value=(an5_value/10)*2441 / 1000 *16
an6_value=(an6_value/10)*2441 / 1000 *16
an7_value=(an7_value/10)*2441 / 1000 *16
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: de facto standard for intel hex files produced by MPLAB?

2009-12-04T06:00:29Z

Peter escribió:
> Is the default setting for MPLAB hex output INHX32 ? which is INHX8M with an
> opcode 04 record to select INHX32 ?
>
> thanks,
>
> Peter

Peter, the default output of the LINKER (MPLINK) is INHX32,
if you wish to use another one you have to specify it (via
command line. ex using the parameter /aINHX8S or via the
MPLAB IDE in your project settings, under the LINKER tabsheet).

About the opcode 04, I don't undestand the question, can you
repost it?

--
------------------------------
Mauricio Giovagnini (Maunix)
www.maunix.com.ar
Cordoba, Arg.
LinkedIn Profile: http://www.linkedin.com/in/mgiovagnini

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-04T04:26:49Z

Tamas Rudnai wrote:

>> FORTH! The answer is always FORTH.
>
> How fast is Forth on PIC? Forth was designed onto a stack based
> machine, was not it? And PIC (mid-range) need to emulate a stack
> using indirect addressing, so I thought it might not be very fast but
> I might wrong? Or maybe not slower than any other interpreter?

I don't think that it's any slower than what a BASIC or Pascal p-code
(or any other) interpreter would do. They all have to have some
structured means of indirectly addressing variables and function
arguments; on a more "common" architecture, that's naturally the machine
stack, but on a PIC that would be something else -- but still the same
mechanism, whether you call it an emulated stack or something else.

Gerhard
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-04T00:35:09Z

> it seem like 10 times of avg reading loop of each analog input,
> taking up 30% total flash memory in 4Kword

That seems an awful lot of memory for what seems a simple function

> is there a way for optimize adc avg reading method ?

If by 'average' you mean arithmetic mean, then add the 10 samples
to a 16-bit accumulator and divide by 10. Or to simplify, take 8
and right-shift 3 times, or take 16 and right-shift 4 times. There are
also 'moving averages', where you'd re-calculate the mean after
discarding sample1 from the queue/array and adding the latest

Finding a mode might take a little more work, but you can narrow
the range to limit the number of each number and its frequency

Similarly, other methods exist when looking for other "expected"
values

http://en.wikipedia.org/wiki/Arithmetic_mean

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T23:59:43Z

facing flash memory shortage is PIC16F688, intend to increase some function
but i try not too many re-engineering on PCB hardware to suit for it, b'cos
there will be PCB cost. it seem like the only way is to optimize the
"codes".

i use 1 internal ADC at AN0, mutiplx-ed externally(using CD4051) get 8
analog inputs, it seem like 10 times of avg reading loop of each analog
input, taking up 30% total flash memory in 4Kword, is there a way for
optimize adc avg reading method ?
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T19:02:07Z

On Thu, Dec 3, 2009 at 11:23 PM, Marcel Birthelmer
<marcelb.lists@...> wrote:
> So... what to interpret? Tokenized Basic? Pascal p-code? Java?
>> ...
>
> FORTH! The answer is always FORTH.

How fast is Forth on PIC? Forth was designed onto a stack based
machine, was not it? And PIC (mid-range) need to emulate a stack using
indirect addressing, so I thought it might not be very fast but I
might wrong? Or maybe not slower than any other interpreter?

BTW: BasicStamp is doing this Basic interpreter thingy on , never
tried that though:
http://www.parallax.com/tabid/295/Default.aspx

And PICBASIC seems to be very similar to that but on the 'real' PIC:
http://www.comfile.co.kr/english2/study/pbmanualf.html

Tamas

> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
/* www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s="/*
www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s=%s%s%s,
q=%s%s%s%s,s,q,q,a=%s%s%s%s,q,q,q,a,a,q); }",
q="\"",s,q,q,a="\\",q,q,q,a,a,q); }

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T18:21:00Z

> So... what to interpret? Tokenized Basic? Pascal p-code? Java?
>> ...
>
> FORTH! The answer is always FORTH.

I was thinking that, but forgot to include it in the list! I used to have
an MC6800 STD bus card with FORTH on it. I even went to a one day class
put on by Forth Inc.

Harold

--
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T15:23:20Z

So... what to interpret? Tokenized Basic? Pascal p-code? Java?
> ...

FORTH! The answer is always FORTH.
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T15:20:33Z

>> Another option is to have the code inside the PIC as an interpreter,
>> and put the tokens that get interpreted in external EEPROM
>
> I believe that's how the PIC-AXE works, using internal EEPROM,
> so programs are/were quite short

I had not thought of the internal interpreter, external program idea, but
that's a good idea for large programs. If each instruction read in from
outside resulted in a lot of internal code being run, it could be pretty
fast too. So... what to interpret? Tokenized Basic? Pascal p-code? Java?
...

Harold

--
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T14:36:06Z

> Another option is to have the code inside the PIC as an interpreter,
> and put the tokens that get interpreted in external EEPROM

I believe that's how the PIC-AXE works, using internal EEPROM,
so programs are/were quite short
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Problem on LCD (SPLC780D controller) + 18F4525 PIC + MPLAB

2009-12-03T12:52:30Z

Hey do you have any sample code for the A/D converter?? Im new at this and I am having trouble with the understanding how to code the A/D converter. Thanks.

lionkid wrote:

Hi all!

Well, i'm new in PIC but i've already tested differents PIC functions as : the ADC, the LED blinking and so on...

So, i've got an LCD which is based on the SPLC780D controller (you can find the datasheet here : http://www.hebeiltd.com.cn/lcm.datasheet/SPLC780D_DS.pdf)
i've tried a lot of things in order to display caracters but nothing seems to be displayed...More over, i've spent approximately 2 weeks in order to make this stuff working, but no results... :(

So, what i have and what i've done is here...

1° I've got a Schaer+ programmer that i've done and which works very well, so the problem doesn't come from this one...

2° I send the program (the .hex file) into the PIC thanks to the Winpic software.

3° I use MPLAB (V 8.00.000) + C18 to compile the source files which are given in the src and the h folder for obtaining this "famous" .hex file..

4° I use a 18F4525 Microchip PIC with the following connexions :

The control bits :

=> RA0 : R/W pin.

=> RA1 : RS pin.

=> RA2 : E pin.

=> OSC1 & OSC2 : a 20Mhz crystal resonator with 2* 15pF capacitors ( as mentionned by the 18F4525 datasheet )

--

Data bits :

=> RB7 : D7

=> RB6 : D6

=> RB5 : D5

=> RB4 : D4

--

PIC alimentation :

Vdd = +5V (given by a 78M05)
Vss = 0V = GND.

--

All the previous tests with differents functions were OK (ADC and LED blinking), so may the problem come from my personal C code ?

Here is the main :

[code]

/********* USE OF THE MPLAB libraries ************/

#include "p18f4525.h"
#include "delays.h"
#include "xlcd.h"

/*************************************************/

/**************** Configuration bits *************/

#pragma config OSC = HS // 20Mhz.
#pragma config FCMEN = OFF // Fail Safe Clock Monitor : Disabled.
#pragma config IESO = OFF // Internal External Osc. Switch Over : Disabled.
#pragma config PWRT = OFF // Power Up Timer : Disabled.
#pragma config BOREN = OFF // Brown Out Reset : Disabled.
#pragma config WDT = OFF // Watch Dog Timer : Disabled.
#pragma config MCLRE = OFF // MCLRE : Disabled.
#pragma config PBADEN = OFF // Port B A/D Enable : Disabled. => sortie numérique sur RESET.
#pragma config STVREN = OFF // Stack oVerflow Reset : Disabled.
#pragma config LVP = OFF // Low voltage ICSP : Disabled.

/**************************************************/

/***************** MAIN FUNCTION ******************/

void main(void)
{

/****************** Config des broches reliées au LCD *******/

TRISB = 0x00; // All the port B is made as an output. (can put 0x0F but 0x00 should be OK)
TRIS_RW = 0; // Read/Write is made as an output.
TRIS_RS = 0; // Register Select is made as an output.
TRIS_E = 0; // Enable is made as an Output.

/************************************************************/

OpenXLCD(FOUR_BIT & LINES_5X7);
while(BusyXLCD());

putrsXLCD("Test");
while(1);
}

/************ END OF MAIN FUNCTION ********************/

/************** DELAYS NECESSARY USED BY THE MPLAB LIBRARIES ************/

void DelayXLCD(void) // Delay of 5ms
{
Delay1KTCYx(25);
}

void DelayPORXLCD(void) // Delay of 18ms
{
Delay1KTCYx(90);
}

void DelayFor18TCY(void) // Delay of 3.6µs
{
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
Nop();Nop();
}

/**************************************************************************/
[/code]

Here is the xlcd.h :

[code]

#ifndef __XLCD_H
#define __XLCD_H

/* PIC18 XLCD peripheral routines.
*
* Notes:
* - These libraries routines are written to support the
* Hitachi HD44780 LCD controller.
* - The user must define the following items:
* - The LCD interface type (4- or 8-bits)
* - If 4-bit mode
* - whether using the upper or lower nibble
* - The data port
* - The tris register for data port
* - The control signal ports and pins
* - The control signal port tris and pins
* - The user must provide three delay routines:
* - DelayFor18TCY() provides a 18 Tcy delay
* - DelayPORXLCD() provides at least 15ms delay
* - DelayXLCD() provides at least 5ms delay
*/

/* Interface type 8-bit or 4-bit
* For 8-bit operation uncomment the #define BIT8
*/
/* #define BIT8 */

/* When in 4-bit interface define if the data is in the upper
* or lower nibble. For lower nibble, comment the #define UPPER
*/
#define UPPER

/* DATA_PORT defines the port to which the LCD data lines are connected */
#define DATA_PORT PORTB
#define TRIS_DATA_PORT TRISB

/* CTRL_PORT defines the port where the control lines are connected.
* These are just samples, change to match your application.
*/
#define RW_PIN LATAbits.LATA0 /* PORT for RW */
#define TRIS_RW DDRAbits.RA0 /* TRIS for RW */

#define RS_PIN LATAbits.LATA1 /* PORT for RS */
#define TRIS_RS DDRAbits.RA1 /* TRIS for RS */

#define E_PIN LATAbits.LATA2 /* PORT for D */
#define TRIS_E DDRAbits.RA2 /* TRIS for E */

/* Display ON/OFF Control defines */
#define DON 0b00001111 /* Display on */
#define DOFF 0b00001011 /* Display off */
#define CURSOR_ON 0b00001111 /* Cursor on */
#define CURSOR_OFF 0b00001101 /* Cursor off */
#define BLINK_ON 0b00001111 /* Cursor Blink */
#define BLINK_OFF 0b00001110 /* Cursor No Blink */

/* Cursor or Display Shift defines */
#define SHIFT_CUR_LEFT 0b00010011 /* Cursor shifts to the left */
#define SHIFT_CUR_RIGHT 0b00010111 /* Cursor shifts to the right */
#define SHIFT_DISP_LEFT 0b00011011 /* Display shifts to the left */
#define SHIFT_DISP_RIGHT 0b00011111 /* Display shifts to the right */

/* Function Set defines */
#define FOUR_BIT 0b00101111 /* 4-bit Interface */
#define EIGHT_BIT 0b00111111 /* 8-bit Interface */
#define LINE_5X7 0b00110011 /* 5x7 characters, single line */
#define LINE_5X10 0b00110111 /* 5x10 characters */
#define LINES_5X7 0b00111011 /* 5x7 characters, multiple line */

#define PARAM_SCLASS auto
#define MEM_MODEL far /* Change this to near for small memory model */

/* OpenXLCD
* Configures I/O pins for external LCD
*/
void OpenXLCD(PARAM_SCLASS unsigned char);

/* SetCGRamAddr
* Sets the character generator address
*/
void SetCGRamAddr(PARAM_SCLASS unsigned char);

/* SetDDRamAddr
* Sets the display data address
*/
void SetDDRamAddr(PARAM_SCLASS unsigned char);

/* BusyXLCD
* Returns the busy status of the LCD
*/
unsigned char BusyXLCD(void);

/* ReadAddrXLCD
* Reads the current address
*/
unsigned char ReadAddrXLCD(void);

/* ReadDataXLCD
* Reads a byte of data
*/
char ReadDataXLCD(void);

/* WriteCmdXLCD
* Writes a command to the LCD
*/
void WriteCmdXLCD(PARAM_SCLASS unsigned char);

/* WriteDataXLCD
* Writes a data byte to the LCD
*/
void WriteDataXLCD(PARAM_SCLASS char);

/* putcXLCD
* A putc is a write
*/
#define putcXLCD WriteDataXLCD

/* putsXLCD
* Writes a string of characters to the LCD
*/
void putsXLCD(PARAM_SCLASS char *);

/* putrsXLCD
* Writes a string of characters in ROM to the LCD
*/
void putrsXLCD(PARAM_SCLASS const /*MEM_MODEL*/ rom char *);

/* User defines these routines according to the oscillator frequency */
extern void DelayFor18TCY(void);
extern void DelayPORXLCD(void);
extern void DelayXLCD(void);

#endif

[/code]

Here is the OpenXLCD.c code if necessary... :

[code]

#include <p18cxxx.h>
#include <xlcd.h>

/********************************************************************
* Function Name: OpenXLCD *
* Return Value: void *
* Parameters: lcdtype: sets the type of LCD (lines) *
* Description: This routine configures the LCD. Based on *
* the Hitachi HD44780 LCD controller. The *
* routine will configure the I/O pins of the *
* microcontroller, setup the LCD for 4- or *
* 8-bit mode and clear the display. The user *
* must provide three delay routines: *
* DelayFor18TCY() provides a 18 Tcy delay *
* DelayPORXLCD() provides at least 15ms delay *
* DelayXLCD() provides at least 5ms delay *
********************************************************************/
void OpenXLCD(unsigned char lcdtype)
{
// The data bits must be either a 8-bit port or the upper or
// lower 4-bits of a port. These pins are made into inputs
#ifdef BIT8 // 8-bit mode, use whole port
DATA_PORT = 0;
TRIS_DATA_PORT = 0xff;
#else // 4-bit mode
#ifdef UPPER // Upper 4-bits of the port
DATA_PORT &= 0x0f;
TRIS_DATA_PORT |= 0xf0;
#else // Lower 4-bits of the port
DATA_PORT &= 0xf0;
TRIS_DATA_PORT |= 0x0f;
#endif
#endif
TRIS_RW = 0; // All control signals made outputs
TRIS_RS = 0;
TRIS_E = 0;
RW_PIN = 0; // R/W pin made low
RS_PIN = 0; // Register select pin made low
E_PIN = 0; // Clock pin made low

// Delay for 15ms to allow for LCD Power on reset
DelayPORXLCD();

// Setup interface to LCD
#ifdef BIT8 // 8-bit mode interface
TRIS_DATA_PORT = 0; // Data port output
DATA_PORT = 0b00110000; // Function set cmd(8-bit interface)
#else // 4-bit mode interface
#ifdef UPPER // Upper nibble interface
TRIS_DATA_PORT &= 0x0f;
DATA_PORT &= 0x0f;
DATA_PORT |= 0b00100000; // Function set cmd(4-bit interface)
#else // Lower nibble interface
TRIS_DATA_PORT &= 0xf0;
DATA_PORT &= 0xf0;
DATA_PORT |= 0b00000010; // Function set cmd(4-bit interface)
#endif
#endif
E_PIN = 1; // Clock the cmd in
DelayFor18TCY();
E_PIN = 0;

// Delay for at least 4.1ms
DelayXLCD();

// Setup interface to LCD
#ifdef BIT8 // 8-bit interface
DATA_PORT = 0b00110000; // Function set cmd(8-bit interface)
#else // 4-bit interface
#ifdef UPPER // Upper nibble interface
DATA_PORT &= 0x0f; // Function set cmd(4-bit interface)
DATA_PORT |= 0b00100000;
#else // Lower nibble interface
DATA_PORT &= 0xf0; // Function set cmd(4-bit interface)
DATA_PORT |= 0b00000010;
#endif
#endif
E_PIN = 1; // Clock the cmd in
DelayFor18TCY();
E_PIN = 0;

// Delay for at least 100us
DelayXLCD();

// Setup interface to LCD
#ifdef BIT8 // 8-bit interface
DATA_PORT = 0b00110000; // Function set cmd(8-bit interface)
#else // 4-bit interface
#ifdef UPPER // Upper nibble interface
DATA_PORT &= 0x0f; // Function set cmd(4-bit interface)
DATA_PORT |= 0b00100000;
#else // Lower nibble interface
DATA_PORT &= 0xf0; // Function set cmd(4-bit interface)
DATA_PORT |= 0b00000010;
#endif
#endif
E_PIN = 1; // Clock cmd in
DelayFor18TCY();
E_PIN = 0;

#ifdef BIT8 // 8-bit interface
TRIS_DATA_PORT = 0xff; // Make data port input
#else // 4-bit interface
#ifdef UPPER // Upper nibble interface
TRIS_DATA_PORT |= 0xf0; // Make data nibble input
#else // Lower nibble interface
TRIS_DATA_PORT |= 0x0f; // Make data nibble input
#endif
#endif

// Set data interface width, # lines, font
while(BusyXLCD()); // Wait if LCD busy
WriteCmdXLCD(lcdtype); // Function set cmd

// Turn the display on then off
while(BusyXLCD()); // Wait if LCD busy
WriteCmdXLCD(DOFF&CURSOR_OFF&BLINK_OFF); // Display OFF/Blink OFF
while(BusyXLCD()); // Wait if LCD busy
WriteCmdXLCD(DON&CURSOR_ON&BLINK_ON); // Display ON/Blink ON

// Clear display
while(BusyXLCD()); // Wait if LCD busy
WriteCmdXLCD(0x01); // Clear display

// Set entry mode inc, no shift
while(BusyXLCD()); // Wait if LCD busy
WriteCmdXLCD(SHIFT_CUR_LEFT); // Entry Mode

// Set DD Ram address to 0
while(BusyXLCD()); // Wait if LCD busy
SetDDRamAddr(0); // Set Display data ram address to 0

return;
}

[/code]

I work on a project board for avoiding any soldering operation... @20Mhz (xtal resonator) does it induce any problem?

Thanks to all per advance!

PS : Sorry for my english... I'm french ;)

See ya!

Re: increase pic program flash memory size ? possible ?

2009-12-03T10:04:57Z

> does anyone know how to increase pic flash memory size by using external
> eeprom ? is this possible to have extended flash memory?

There is an 18 series PIC that can use external memory, but then all memory
is external.

Most people just go and choose the next memory size up chip.

As others have noted, you can put constant data in an external EEPROM, e.g.
strings for display on an LCD. Another option is to have the code inside the
PIC as an interpreter, and put the tokens that get interpreted in external
EEPROM.

You don't say just which chip you are using, or why you think you need more
memory.

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T09:59:59Z

> need help,
> does anyone know how to increase pic flash memory size by using external
> eeprom ? is this possible to have extended flash memory?
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

Generally, no. You cannot execute code from external memory. You can, of
course, add external RAM, EEPROM, or flash for data.

Harold

--
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: increase pic program flash memory size ? possible ?

2009-12-03T09:26:27Z

Not for running program from -- but you can use an external eeprom to
store static data (text or graphics for example), so you can free up
space from the flas which then can be used for storing code instead.

Tamas

On Thu, Dec 3, 2009 at 5:09 PM, cllow2020 <cllow2020@...> wrote:
> need help,
> does anyone know how to increase pic flash memory size by using external
> eeprom ? is this possible to have extended flash memory?
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
/* www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s="/*
www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s=%s%s%s,
q=%s%s%s%s,s,q,q,a=%s%s%s%s,q,q,q,a,a,q); }",
q="\"",s,q,q,a="\\",q,q,q,a,a,q); }

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

increase pic program flash memory size ? possible ?

2009-12-03T09:09:35Z

need help,
does anyone know how to increase pic flash memory size by using external
eeprom ? is this possible to have extended flash memory?
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: PIC 16F1936 -- is this for real?

2009-12-01T03:02:44Z

I'm running my PIC18F4420 and PIC18F4520 at 32Mhz...by 8Mhz*4 using PLL

Sean Breheny wrote:

Yes, although I was slightly wrong: at least for the chip I checked,
the max is 32MHz using the PLL plus the internal osc.

See the datasheet for the 18F8722 family, section 2.6.4

2.6.4 PLL IN INTOSC MODES
The 4x Phase Locked Loop (PLL) can be used with the
internal oscillator block to produce faster device clock
speeds than are normally possible with the internal
oscillator sources. When enabled, the PLL produces a
clock speed of 16 MHz or 32 MHz.
Unlike HSPLL mode, the PLL is controlled through
software. The control bit, PLLEN (OSCTUNE<6>), is
used to enable or disable its operation.

The PLL is available when the device is configured to
use the internal oscillator block as its primary clock
source (FOSC<3:0> = 1001 or 1000). Additionally, the
PLL will only function when the selected output fre-
quency is either 4 MHz or 8 MHz (OSCCON<6:4> = 111
or 110). If both of these conditions are not met, the PLL
is disabled and the PLLEN bit remains clear (writes are
ignored).

On Tue, Sep 8, 2009 at 8:10 PM, Funny NYPD<funnynypd@yahoo.com> wrote:
>>20 or even 40MHz.
>
> Any reference?
>
> Funny N.
> Au Group Electronics, http://www.AuElectronics.com
> http://www.AuElectronics.com/products
> http://augroups.blogspot.com/
>
>
>
>
> ________________________________
> From: Sean Breheny <shb7@cornell.edu>
> To: Microcontroller discussion list - Public. <piclist@mit.edu>
> Sent: Tuesday, September 8, 2009 6:27:40 PM
> Subject: Re: [PIC] PIC 16F1936 -- is this for real?
>
> This is a bit late, but I wanted to point out that some PICs (in the
> 18 series I think) allow you to run the internal PLL from the RC
> oscillator to multiply the frequency up to 20 or even 40MHz.
>
> Sean
>
>
> O
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>
>
>
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Experimental LCD/USB Solar Design

2009-11-30T08:28:25Z

Driving a simple numeric LCD display is easy from any microcontroller,
with very low power:

http://www.ubasics.com/driving_static_lcds

With a two digit display counting from 32 to 0 you need 12 output
lines, and they will need to change state about 30-60 times a second.
Put them on an interrupt, and put the processor to sleep, and it'll
consume less than 1mA for the LCD and timer.

The USB function of the microcontroller can be turned off until you
detect 5V on the USB V+ line.

So the only current you'll need beyond 1mA is the current required to
activate that external signal you mention.

The PIC18F24J50 might be agood candidate. It has more than enough
pins to drive the LCD and talk via USB, it's part of the extra low
power line of microchip's parts, built in real time clock/counter. It
has a high precision internal oscillator to the USB, and a low speed
internal oscillator which you can use for the timer/clock and for low
power LCD driving. And it's relatively inexpensive.

The MAX1555 IC is good for lithium-ion charging. It'll accept
charging from either a USB port or from a 3.7-7V input (solar cell,
for instance) and performs all the work required for safely charging
the cell. You can get it on a breakout board here:
http://www.sparkfun.com/commerce/product_info.php?products_id=726

That may help with hardware selection, but the hardware design and
more difficult software design still lie ahead. If the system is as
simple as you suggest, then using the USB libraries provided by
microchip and just adding your LCD/timer/external output code should
be relatively easy.

On Mon, Nov 30, 2009 at 9:36 AM, patrickdel1982 <patrick.del@...> wrote:

>
> • My objective is to create a battery-operated counter-controller which shuts
> down an external function “X” via an analog signal after one cycle of
> thirty-two (32) days (e.g. 2764800 seconds) unless the counter-controller is
> “unlocked” through a security code is entered through a USB port to renew
> the count.
> • The unit should be able to display the number of days left in the counting
> cycle on a small LCD, starting from thirty-two (32) days and counting down
> to zero (0).
> • The external function is run through a PIC16F785, which has an available
> analog input. There should be a string of five (5) security codes stored on
> the counter-controller memory which repeat every five (5) cycles.
> • The counter-controller should be as low-power, running as few watts as
> possible. The system should also work on a 3.0-4.0 volt range (single
> lithium-ion battery).
> • The default mode for if the battery has low power below 3.0V is, “locked,
> but not counting,” meaning that the external device cannot function but the
> counter-controller stops counting for the time being until the battery is
> charged above 3.0V.
> • Since the unit is solar powered, the entire counting and controlling
> regime must be super low-power. There is a switch which a human user will
> push periodically (perhaps 3-20 times per day) to activate and deactivate
> the external function “X,” so a count check, date display and control
> function can be hypothetically performed only at these times.
> • As a side note, the USB port used to unlock the system should use its
> external 5V power source to charge the battery while unlocking.
>
> My experience with microcontrollers, counters and IC’s is limited, having a
> fair working knowledge of 8-bit MCUs, perhaps able to debug codes written in
> C format, but not a true designer or troubleshooter. Overall I am a
> beginner level with microcontrollers, but have a good working knowledge of
> circuit design. I know how to “flash an LED.” In fact, I can make an LED
> run on PWM using 16F785. Can anyone give me a recommendation of where to
> start? I am interested in PIC microcontrollers, but not strictly limited if
> nothing fits the design parameters above.
> Here is a basic diagram of the functionality of the counter-controller:
>
>
>
>
>
>
>
>
>
>
>
> http://old.nabble.com/file/p26575712/simple_diagram.jpg
>
> http://imgur.com/g2eg1
>
>
> Can anyone offer any help with what PIC families and features I should look
> for? Is there any PIC which has both LCD and USB capability? How much
> memory will I need? How can I find a PIC or incorporate a design that will
> fulfill all of the above requirements? What approach should I use on this
> design? Any ideas or tips?
>
> --
> View this message in context: http://old.nabble.com/Experimental-LCD-USB-Solar-Design-tp26575712p26575712.html
> Sent from the PIC - [PIC] mailing list archive at Nabble.com.
>
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Experimental LCD/USB Solar Design

2009-11-30T06:36:34Z

• My objective is to create a battery-operated counter-controller which shuts down an external function “X” via an analog signal after one cycle of thirty-two (32) days (e.g. 2764800 seconds) unless the counter-controller is “unlocked” through a security code is entered through a USB port to renew the count.
• The unit should be able to display the number of days left in the counting cycle on a small LCD, starting from thirty-two (32) days and counting down to zero (0).
• The external function is run through a PIC16F785, which has an available analog input. There should be a string of five (5) security codes stored on the counter-controller memory which repeat every five (5) cycles.
• The counter-controller should be as low-power, running as few watts as possible. The system should also work on a 3.0-4.0 volt range (single lithium-ion battery).
• The default mode for if the battery has low power below 3.0V is, “locked, but not counting,” meaning that the external device cannot function but the counter-controller stops counting for the time being until the battery is charged above 3.0V.
• Since the unit is solar powered, the entire counting and controlling regime must be super low-power. There is a switch which a human user will push periodically (perhaps 3-20 times per day) to activate and deactivate the external function “X,” so a count check, date display and control function can be hypothetically performed only at these times.
• As a side note, the USB port used to unlock the system should use its external 5V power source to charge the battery while unlocking.

My experience with microcontrollers, counters and IC’s is limited, having a fair working knowledge of 8-bit MCUs, perhaps able to debug codes written in C format, but not a true designer or troubleshooter. Overall I am a beginner level with microcontrollers, but have a good working knowledge of circuit design. I know how to “flash an LED.” In fact, I can make an LED run on PWM using 16F785. Can anyone give me a recommendation of where to start? I am interested in PIC microcontrollers, but not strictly limited if nothing fits the design parameters above.
Here is a basic diagram of the functionality of the counter-controller:

http://imgur.com/g2eg1

Can anyone offer any help with what PIC families and features I should look for? Is there any PIC which has both LCD and USB capability? How much memory will I need? How can I find a PIC or incorporate a design that will fulfill all of the above requirements? What approach should I use on this design? Any ideas or tips?

Re: Macro usage

2009-11-29T10:48:03Z

On Sun, Nov 29, 2009 at 6:30 AM, Jan-Erik Soderholm
<jan-erik.soderholm@...> wrote:
> Since it is a macro (which always is expanded into real code)
> it will work. There will be one BSF instruction for each
> "call" (which isn't a real call, of course) of the macro.
> It would not have worked if the BSF was in e.g. a normal
> subroutine (that is CALL'ed).

Ok, perfect. I thought that was the case. I must admit I totally
forgot about checking the output listing.

Thanks everyone!

Josh
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
-Douglas Adams
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Experimental Solar Auto-Shutdown Controller

2009-11-29T07:53:33Z

• My objective is to create a battery-operated counter-controller which shuts down an external function “X” via an analog signal after one cycle of thirty-two (32) days (e.g. 2764800 seconds) unless the counter-controller is “unlocked” through a security code is entered through a USB port to renew the count.
• The unit should be able to display the number of days left in the counting cycle on a small LCD, starting from thirty-two (32) days and counting down to zero (0).
• The external function is run through a PIC16F785, which has an available analog input. There should be a string of five (5) security codes stored on the counter-controller memory which repeat every five (5) cycles.
• The counter-controller should be as low-power, running as few watts as possible. The system should also work on a 3.0-4.0 volt range (single lithium-ion battery).
• The default mode for if the battery has low power below 3.0V is, “locked, but not counting,” meaning that the external device cannot function but the counter-controller stops counting for the time being until the battery is charged above 3.0V.
• Since the unit is solar powered, the entire counting and controlling regime must be super low-power. There is a switch which a human user will push periodically (perhaps 3-20 times per day) to activate and deactivate the external function “X,” so a count check, date display and control function can be hypothetically performed only at these times.
• As a side note, the USB port used to unlock the system should use its external 5V power source to charge the battery while unlocking.

My experience with microcontrollers, counters and IC’s is limited, having a fair working knowledge of 8-bit MCUs, perhaps able to debug codes written in C format, but not a true designer or troubleshooter. Overall I am a beginner level with microcontrollers, but have a good working knowledge of circuit design. Can anyone give me a recommendation of where to start? I am interested in PIC microcontrollers, but not strictly limited if nothing fits the design parameters above.
Here is a basic diagram of the functionality of the counter-controller:

http://imgur.com/g2eg1

Can anyone offer any help with what PIC families and features I should look for? Are there any PICs which provide counting units? How much memory will I need? How can I find a PIC or incorporate a design that will fulfill all of the above requirements? What approach should I use on this design? Any ideas or tips?

Thank you for your time.

Re: Macro usage

2009-11-29T04:17:46Z

On Sun, Nov 29, 2009 at 4:26 AM, Josh Koffman <joshybear@...> wrote:
> mShiftOut macro _data, _port, _ClockPin, _DataPin, LatchPin
>
> If I did that, could I then use the following line within the macro?
>
> bsf _port,_ClockPin

Yes, you could. For the sake of simplicity you can look in that way:
Macro for the compiler is like a search-and-replace for your text
editor. Every time you mention you macro in your 'real' code the
compiler looks up your macro definition and replaces the code whatever
it finds there.

Tamas

>
> It seems to assemble, I just don't have my board ready to test it yet.
>
> Thanks!
>
> Josh
> --
> A common mistake that people make when trying to design something
> completely foolproof is to underestimate the ingenuity of complete
> fools.
> -Douglas Adams
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
/* www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s="/*
www.mcuhobby.com */ int main() { char *a,*s,*q; printf(s=%s%s%s,
q=%s%s%s%s,s,q,q,a=%s%s%s%s,q,q,q,a,a,q); }",
q="\"",s,q,q,a="\\",q,q,q,a,a,q); }

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Macro usage

2009-11-29T03:30:21Z

Josh Koffman wrote:

> Hi all.
>
> I'm a bit confused by exactly what MPLAB will let me do with a macro.
> I have a routine that I use for sending data to a shift register. Now
> I want to do two separate shift registers (not chained, different
> pins). So what I'd like to do is define a macro like this:
>
> mShiftOut macro _data, _port, _ClockPin, _DataPin, LatchPin
>
> If I did that, could I then use the following line within the macro?
>
> bsf _port,_ClockPin
>
> It seems to assemble, I just don't have my board ready to test it yet.
>
> Thanks!
>
> Josh

Since it is a macro (which always is expanded into real code)
it will work. There will be one BSF instruction for each
"call" (which isn't a real call, of course) of the macro.
It would not have worked if the BSF was in e.g. a normal
subroutine (that is CALL'ed).
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Macro usage

2009-11-29T00:39:18Z

2009/11/29 Ruben Jönsson <ruben@...>:
> Hi,
>
> Why can't you use the MPLAB simulator to test it?
>
> /Ruben
>

Or just look at the listing file to to verify that that's what's happening.

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Macro usage

2009-11-29T00:15:31Z

Hi,

Why can't you use the MPLAB simulator to test it?

/Ruben

==============================
Ruben Jönsson
AB Liros Electronic
Box 9124, 200 39 Malmö, Sweden
TEL INT +46 40142078
FAX INT +46 40947388
ruben@...
==============================

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Macro usage

2009-11-28T20:26:15Z

Hi all.

I'm a bit confused by exactly what MPLAB will let me do with a macro.
I have a routine that I use for sending data to a shift register. Now
I want to do two separate shift registers (not chained, different
pins). So what I'd like to do is define a macro like this:

mShiftOut macro _data, _port, _ClockPin, _DataPin, LatchPin

If I did that, could I then use the following line within the macro?

bsf _port,_ClockPin

It seems to assemble, I just don't have my board ready to test it yet.

Thanks!

Josh
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
-Douglas Adams
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Microchip new Tag-Connect for ICD2/3/REAL ICE

2009-11-26T08:32:38Z

> PICkit2 button could have been there too -- so then this
> press-to-program function works with the original pk2 software (no
> beeps though).

I think for a real hands-off-the-PC programming some feedback is
necessary. The pickit 2 has is LEDs.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Microchip new Tag-Connect for ICD2/3/REAL ICE

2009-11-26T07:49:55Z

On Thu, Nov 26, 2009 at 3:41 PM, Wouter van Ooijen <wouter@...> wrote:
>> Your programming pen's neat. But what's the function of the button?
>
> mid-volume production. get the PCB, connect, press the button wait for
> readly (beep? signal?), disconnect, repeat.

PICkit2 button could have been there too -- so then this
press-to-program function works with the original pk2 software (no
beeps though).

Tamas

>
> --
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: www.voti.nl/hvu
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

Re: Microchip new Tag-Connect for ICD2/3/REAL ICE

2009-11-26T07:41:16Z

> Your programming pen's neat. But what's the function of the button?

mid-volume production. get the PCB, connect, press the button wait for
readly (beep? signal?), disconnect, repeat.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Microchip new Tag-Connect for ICD2/3/REAL ICE

2009-11-26T07:14:28Z

2009/11/25 Funny NYPD wrote:

> A few URLs are listed below:
>
> ...

Thanks.

--
WH Tan
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

Re: Microchip new Tag-Connect for ICD2/3/REAL ICE

2009-11-26T07:13:52Z

2009/11/24 Vicent Colomar Prats <vicentecolomar@...>:
> CCS, Inc. was using it some time ago:
> http://www.ccsinfo.com/content.php?page=tagConnect
>

Hi Vicent,

Those cables look-alike! I wonder if Microchip bought it from CCS...

Thanks for the info.
Best regards,

--
WH Tan
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist