> a) Outlook Express is warning me that _your_ message has been altered,
> probably by the mail list server. So maybe you are not really who your
> digital signature is hoping to convince me you are... Looking at your
> certificate I see you have one of their Web of Trust certificates - I have
> one too!  For this to work our mail list server would need to know not to
> alter the digital message envelope of our signed messages - but how else
can
> they add their advertisers links and pay for the service - sigh!

Yes, I know... its the darn yahoo server... but you will notice that the
cert is still intact. The fact that it warned you that the message had been
tampered with shows that it is working. Frankly, I tend to think it
unethical for the list to tamper with the mail... but at teh same time Yahoo
is a business that's trying to make a buck with a server we're partaking in
of freely.
A lot of companies use the Yahoo lists for this exact type of group (the
JStamp list is another example) I'm starting to wonder if it would be worth
setting up a server for lists of this type specifically for companies to
host external to themselves... in fact, the list could issue certs. to
members, elminiating spam and address trolling by robots.

> b) Anyone can go get a free personal email certificate from Thawte that
only
> asserts that they are the owner of the email address - nothing else. So a
> spammer can got get a free email certificate for their spam haven email
> address and still spam the list!!! The certificate needs to assert their
> identiry not just their email address which takes more work.

This is true but they can have only *one* "id" (though many addresses), not
a million ids from a million systems. Not only that, but the folks who go
about spamming don't take much time to considder who they are senting
*to*... so why would they go to the trouble of getting a legit cert? Once
they had one, we would then be able to actually find the buggers and let
them really know how we feel. Or better yet, bill them for our time. Maybe
then they wouldn't be so causal about randomly sending irrelivent mail to
everyone in there ill-gotten database.

> Thawte had a big push on their Web of Trust program a year or two ago and
> got people to be notarizd in person. A number of us went along got
notarized
> so we could notarize others, but it has not taken off. This allowed you to
> get yorr actual name on the certificate and not just an email box that you
> have access to. See https://www.thawte.com/html/COMMUNITY/wot/index.html

Yah, that's how I got my name on mine... I was notarized by a few people in
my city, who had gone through that initial notarization process... I could
notarize people myself but I'd need a few more security points ;)

Another aspect is that I could encrypt my mail to the list, preventing any
robot from gathering my address. To do that, everyone on the list would have
to have a cert as well. and this list would have to have its own cert.

- Brill Pappin

All,

I have fair amount of PIC parts I bought for an SMD project that never saw
the light of day, and none of it was never used.  Since my new projects will
use the Atmel AVR, I'm offering the following for sale.  Everything listed
below is brand new and never used.

All prices are in US Dollars, buyer pays for shipping.  And I don't mind
shipping stuff to Oz.

MPLAB ICD KIT, Part # DV164002
---------------------------------------------------------
Kit contains the following:

- One PIC16LF876-04/SP (28-pin PDIP)
- One PIC16F877-04/P (40-pin PDIP)
- MPLAB ICD Module, Rev 1- MPLAB ICD User's Guide
- DB9 male to DB9 female serial cable
- PIC16F87X Rev B errata sheet
- PIC16F87X Rev B3 errata sheet
- PIC16F87X Rev B5 errata sheet
- MPASM User's Guide
- MPLAB IDE, Simulator, Editor User's Guide
- MPLAB IDE v5.20 CD-ROM
- Microchip 2000 Technical Library CD-ROM
- Setup Brochure
- Packing List
- Registration Card

Never Used, software, ICD module, cable, and CPUs still in shrink wrap

Paid $99.00 new, will sell for $75.00 or best offer


Parts
---------------------------------------------------------

- 25 PIC16F876-20/SO (Digi-Key Part# PIC16F876-20/SO-ND) 28-pin SOIC
     New, still in tube in sealed antistatic bag, never opened
     Paid $5.32 each new, will sell for $5.00 each or $115 for all 25

-  2 PIC16F877-20/L (Digi-Key Part# PIC16F877-20/L-ND) 44-pin PLCC
     New, in sealed antistatic bag, never opened

- 25 PIC16F876-20/SO (Digi-Key Part# PIC16F876-20/SO-ND) 28-pin SOIC
     New, still in tube inside sealed antistatic bag, never opened
     Paid $5.32 each new, will sell for $5.00 each or $115 for all 25

-  2 PIC16F877-20/L (Digi-Key Part# PIC16F877-20/L-ND) 44-pin PLCC
     New, in sealed antistatic bag, never opened
     Paid $10.63 each new, will sell for $8.00 each

- 20 20MHz Ceramic Resonators, with caps (Digi-Key Part# X909-ND)
     New, in sealed antistatic bags (10 to a bag), never opened
     Paid $0.68 each new, will sell for $0.50 each

-  2 44-pin PLCC sockets (Digi-Key Part# ED80024-ND)
     New, in sealed antistatic bags, never opened
     Paid $0.83 each new, will sell for $0.50 each

Will sell all the above parts and the MPLAB ICD Kit together for US$200
or best offer.  Buyer pays shipping.

Carl

I finally got my dt006 working. The problem was the parallel 
port bidirectional problem. For an ibm thinkpad you cannot 
set or check this with the bootup bios. You have to download 
the thinkpad config program from www.ibm.com.

Question on Bascom programming though. The first upload of a 
hex program produced by AvrStudio but uploaded via Bascom worked
and went fairly fast. I tried another test and after 15 minutes 
it was still writing and maybe 20% done (if you trust the little
monitor box). I finally ended up killing it. Do I have a 
problem?

Don

dshesnicky wrote:
> 
> I finally got my dt006 working. The problem was the parallel
> port bidirectional problem. For an ibm thinkpad you cannot
> set or check this with the bootup bios. You have to download
> the thinkpad config program from www.ibm.com.
> 
> Question on Bascom programming though. The first upload of a
> hex program produced by AvrStudio but uploaded via Bascom worked
> and went fairly fast. I tried another test and after 15 minutes
> it was still writing and maybe 20% done (if you trust the little
> monitor box). I finally ended up killing it. Do I have a
> problem?

yes you do Don.

a small program such as the ravar.bas that Mick did, should only take
about (I'm guessing) 20 seconds.
I doubt if you killed the chip. They are pretty hardy.

Check out power, cable, software settings. something has changed.
Cheers Don...


Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
              Home Page: http://www.dontronics.com

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

A DT106 board has been modified for use with the MPLab-ICD firmware and PIC
40 pin flash parts. The arrangement allows two alternatives for code
development : with the ICD cable attached, MPLab-ICD can be used, or the
DT106 can be used normally and, thru rs232 on the DT001, access third party
software such as MicroCode Studio Plus. A zif socket makes PIC removal easy.
Some ic's are omitted on the adapter, but if required can be accessed on a
second DT106 fitted to the bus.

The modification required fitting an RJ12 socket to the pcb. The remaining
components on the board were : a 40 pin zif socket, 40 pin header, two 90
deg headers and links, and the following DT106 parts - R1,R2,R6,
Xtal,C5,C6,C11,C14,C12, and on the solder side, C13 and R3.

The RJ12 is fitted to the upper left hand corner of the pcb, with the cable
entry horizontal. After the following pads have been isolated (on both sides
of the board), the RJ12 can be soldered to U7 pins 1,2 and 3, and U2 pins
3,4 and 5. Drill holes near the edge of the board for the locating plugs of
the socket. On the version I used, these holes partially broke out past the
edge so some careful filing was necessary. To add mechanical strength, at
completion of assembly the socket was glued to the pcb using plastic
modelers cement. The isolation of the pads cuts two connections which have
to be rewired - portB.0 to 40 pin header pin 16 and C.7 to header pin 30.
Solder connections between :
                                    RJ12 pin no.        1        2        3
4        5        6
                                    PIC pin no.           1        Vcc
Gnd    40    39    NC
Pins 39 and 40 (B.6 and B.7) either have to be isolated when using the ICD
or not used with any external circuit. I chose to isolate and for
convenience  brought the links to the top of the board, using the isolated
pads of J2 (for B.7) and JP4 (for B.6) to fit right angled headers. (The
tracks on the pcb make this tedious to describe but easy to accomplish).

Tip : check your assembly sequence before you start work.

Regards,

Graeme Jenkins
Precision Devices Pty. Ltd.

Graeme Jenkins wrote:
> 
> A DT106 board has been modified for use with the MPLab-ICD firmware
> and PIC
> 40 pin flash parts. The arrangement allows two alternatives for code
> development : with the ICD cable attached, MPLab-ICD can be used, or
> the

Nice  to see you have got it up and running Graeme.

I would like to add the details to my dt106 page so others can make use
of it.
Do you have any pictures we can add?

Cheers Don...


Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
              Home Page: http://www.dontronics.com

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

thanks Graeme, whenever you are ready,

Cheers Don...


> Graeme Jenkins wrote:
> 
> Don,
> 
> dt2002
> Unfortunately I do not have a photograph, but luckily I have one shot
> left on a roll of film and will get something to you in a few days.
> 
> Regards,
> 
> Graeme Jenkins
> -----Original Message-----
> From: Don McKenzie <support2003@d...>
> To: simmstick@yahoogroups.com <simmstick@yahoogroups.com>
> Date: Sunday, 13 October 2002 6:23
> Subject: Re: [simmstick] MPLab-ICD Adaptor
> 
> Graeme Jenkins wrote:
> >
> > A DT106 board has been modified for use with the MPLab-ICD firmware
> > and PIC
> > 40 pin flash parts. The arrangement allows two alternatives for code
> > development : with the ICD cable attached, MPLab-ICD can be used, or
> > the
> 
> Nice  to see you have got it up and running Graeme.
> 
> I would like to add the details to my dt106 page so others can make
> use
> of it.
> Do you have any pictures we can add?
> 
> Cheers Don...
> 
> Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
>               Home Page: http://www.dontronics.com
> 
> Add USB to your favorite Micro.
> http://www.dontronics.com/dlp.html
> The World's Largest Range of Atmel/AVR & PICmicro Hardware and
> Software
> 
>   Please place (or leave -->) "dt2002" in the subject or body of your
>   message to guarantee your message getting through our spam filters.
> 
> To Post a message, send it to:   simmstick@e...
> 
> To Unsubscribe, send a blank message to:
> simmstick-unsubscribe@e...
> 
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
> 
>                    Yahoo! Groups Sponsor
> 
>                  ADVERTISEMENT
> 
>            [Image]                 [Image]
> 
> 
> 
> To Post a message, send it to:   simmstick@e...
> 
> To Unsubscribe, send a blank message to:
> simmstick-unsubscribe@e...
> 
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

-- 
Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
              Home Page: http://www.dontronics.com

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

> a small program such as the ravar.bas that Mick did, should only 
take
> about (I'm guessing) 20 seconds.
> I doubt if you killed the chip. They are pretty hardy.

I can consistently program the chip now but I have to
erase it prior to programming. Is that expected? I wouldn't
have thought that step was necessary.

Each programming of the chip takes > 10 minutes. I am not
programming in basic but instead uploading intel hex via
bascom-avr. I create the hex in AVRStudio4, startup Bascom
and open the hex file. I then choose upload at which time
I get an error about no .bin and it brings up a hex upload 
window. I erase the chip and program it from from that 
interface. 

I wonder if the fact that it is hex code has something to 
do with it. Shouldn't but stranger things have been seen 
known to happen. I'll some basic and .bin programs and
see what happens. 

Don

> I can consistently program the chip now but I have to
> erase it prior to programming. Is that expected? I wouldn't
> have thought that step was necessary.

I believe that this is necessary as erasing sets all locations to 0xFF and
programming selectively resets them back to 0 for the required bit pattens.
Once a bit value is set to 0 it cannot be set back to 1. That is what an
erase does. That is my understanding which might be accurate :-)

> Each programming of the chip takes > 10 minutes.

You are using a 2313 right? What happens when you load up one of the
BASCOM/AVR demos for the 2313 and program is with the BASCOM IDE Programmer?
It shouls only take seconds, like 5-15 for a smallish bit of code.

What xtal are you using because I have noticed that this can make a
difference? I have found that the programming time for a Mega8 using the
internal 1 MHz clock is a lot slower than using the 8 MHz internal or
external xtal.

If don't want to use BASCOM/AVR as a programmer (I have done quite
successfully for a while) you can use PonyProg. It is very popular and is
fast. The only problem when using it with a DT006 is it does not release the
Reset line after programming. I recently modified some LPT port interface
library demo code to Reset the DT006 properly so you just run that after
PongProg and all is well. In my project I define a PonyProg script file
(*.e2s) that sets the chip type, does an erase, loads the HEX file and
programs it. Then I have a batch file that first executes the e2s file then
calls the ResetDT006 utility which resets the DT006 and away it goes.

PonyProg works a lot faster (maybe 2x) than BASCOM/AVR's programmer which is
also a bonus as I was seriously looking at getting Atmel's AVR ISP
programmer but will put that on hold now.

Have a look at the top of the page here:
http://www.dontronics.com/dt006_help.html

The code with a README.txt can be downloaded from here:
http://www.dontronics.com/zip/resetdt006.zip

I am using PongProg2000 version 2.05a which you can download from here:
http://www.lancos.com/ppwin95.html

Get the 2.05a BETA code. It seems to work well for me programming the DT006
using a 2313, 8535 and a Mega8

> programming in basic but instead uploading intel hex via
> bascom-avr. I create the hex in AVRStudio4, startup Bascom
> and open the hex file. I then choose upload at which time
> I get an error about no .bin and it brings up a hex upload
> window. I erase the chip and program it from from that
> interface.
>
> I wonder if the fact that it is hex code has something to
> do with it. Shouldn't but stranger things have been seen
> known to happen. I'll some basic and .bin programs and
> see what happens.

I would be surprised. I expect something hardware releted is happening here.
Can you try your DT006 and HEX file on another PC to ensure all it well with
your cables and the DT006. Maybe it is some wierdo thing with your laptop.
After all they sometimes do some tricky things to make then small - not
always with the desired outcome...

Good luck!!!

Alex

dshesnicky wrote:
> 
> > a small program such as the ravar.bas that Mick did, should only
> take
> > about (I'm guessing) 20 seconds.
> > I doubt if you killed the chip. They are pretty hardy.
> 
> I can consistently program the chip now but I have to
> erase it prior to programming. Is that expected? I wouldn't
> have thought that step was necessary.
> 
> Each programming of the chip takes > 10 minutes. I am not
> programming in basic but instead uploading intel hex via
> bascom-avr. I create the hex in AVRStudio4, startup Bascom
> and open the hex file. I then choose upload at which time
> I get an error about no .bin and it brings up a hex upload
> window. I erase the chip and program it from from that
> interface.
> 
> I wonder if the fact that it is hex code has something to
> do with it. Shouldn't but stranger things have been seen
> known to happen. I'll some basic and .bin programs and
> see what happens.
> 
> Don

No, something really strange Don,
can you test it on another computer easily?
Also you should try ravar.bas, basically to say it's not the hex code.
This will clear your mind about a hex code or hex code format playing
up.

Cheers Don...

Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
              Home Page: http://www.dontronics.com

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

Thanks for the replies guys. As soon as I read them over I
started thinking there is probably a parallel port problem.
It wouldn't suprise me as alot of laptop items can be a bit
unusual. Unfortunately I may not be able to test this out
this week as I am preparing for a trip next week. It's cramping
my style :)  anyway I will get back to this group when I 
return.

Don

While poking around the web thinking about peripherals
I read about the I2C protocol. Is this still fairly 
common or have people stopped using it? If I'm going
to come up on something it might as well be something
with a future.

Don

I am currently developing production I2C enabled devices at a mad rate...
first to be released shortly... don't abandon it yet ;) All our products
will be I2C enabled where practical.

Check out the SRF08 and CMPS03 from Devantech. You will also notice its the
*newer* AVRs (the mega series) have I2C support in hardware.

Sorry Don, about the almost spam, but I didn't want him/her to get the idea
I2C was dead... but rather a new era of devices are on the way ;)

- Brill Pappin

----- Original Message -----
From: "dshesnicky" <dshesnicky@y...>
To: <simmstick@yahoogroups.com>
Sent: Tuesday, October 15, 2002 10:58 AM
Subject: [simmstick] I2C still used


>
> While poking around the web thinking about peripherals
> I read about the I2C protocol. Is this still fairly
> common or have people stopped using it? If I'm going
> to come up on something it might as well be something
> with a future.
>
> Don
>
>
>
> To Post a message, send it to:   simmstick@e...
>
> To Unsubscribe, send a blank message to: simmstick-unsubscribe@e...
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>

Brill Pappin wrote:
> 
> I am currently developing production I2C enabled devices at a mad
> rate...
> first to be released shortly... don't abandon it yet ;) All our
> products
> will be I2C enabled where practical.
> 
> Check out the SRF08 and CMPS03 from Devantech. You will also notice
> its the
> *newer* AVRs (the mega series) have I2C support in hardware.
> 
> Sorry Don, about the almost spam, but I didn't want him/her to get the
> idea
> I2C was dead... but rather a new era of devices are on the way ;)

No worries Brill.
I welcome "on topic" almost spam as you call it. :-)

Don McKenzie  E-mail:    http://www.dontronics.com/e-mail.html
              Home Page: http://www.dontronics.com

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

> Sorry Don, about the almost spam, but I didn't want him/her to get
the idea
> I2C was dead... but rather a new era of devices are on the way ;)

I agree with the other Don, it's not spam at all. I've been
searching around on I2C and there does seem to be a number
of devices out there. I've printed the I2C spec and datasheets
on an eeprom device as well as the LM75 temp sensor to read over.

Thanks for the reply.

Don

I can see how to program it and that's not my question.
How is the flash typically used on avrs? Are subroutines
stored there for access by main memory or does the flash
storage have to be copied into the main memory for usage?

Excuse any ignorance over and above my usual level in the
above questions.

Don

Hi Don,

AVR's use Harvard architecture, which means that the program is stored  
in a different portion of the chip to main RAM.  So the program lives  
in Flash, while the transient data that the program might use is stored  
in either registers or main RAM.  There is also another area of AVR's  
-- the EEPROM, which is useful for storing data that you don't want to  
disappear when the power turns off.

No instructions are 'copied across to main RAM' the way that  
conventional processors work, for example the AT90S1200 doesn't have  
any RAM at all!  I think that single instructions are copied from Flash  
to some part of the processor before that instruction executes, but you  
don't need to worry about that as it is all deeply hidden from the user.

Any questions, please feel free to ask.

Cheers,
Ben


On Wednesday, October 16, 2002, at 11:55  PM, dshesnicky wrote:

>
> I can see how to program it and that's not my question.
> How is the flash typically used on avrs? Are subroutines
> stored there for access by main memory or does the flash
> storage have to be copied into the main memory for usage?
>
> Excuse any ignorance over and above my usual level in the
> above questions.
>
> Don
>
>
> ------------------------ Yahoo! Groups Sponsor  
> ---------------------~-->
> 4 DVDs Free +s&p Join Now
> http://us.click.yahoo.com/pt6YBB/NXiEAA/jd3IAA/CFFolB/TM
> --------------------------------------------------------------------- 
> ~->
>
> To Post a message, send it to:   simmstick@e...
>
> To Unsubscribe, send a blank message to:  
> simmstick-unsubscribe@e...
>
> Your use of Yahoo! Groups is subject to  
> http://docs.yahoo.com/info/terms/
>
>

If your new to I2C, I'd suggest something like a PCF8574 for your first
try... very simple to use... the eeprom gets tricky at some points, or at
least its harder to see what's going on with it.

- Brill Pappin
  Rogue Robotics
  www.roguerobotics.com


----- Original Message -----
From: "dshesnicky" <dshesnicky@y...>
To: <simmstick@yahoogroups.com>
Sent: Wednesday, October 16, 2002 9:51 AM
Subject: [simmstick] Re: I2C still used


>
> > Sorry Don, about the almost spam, but I didn't want him/her to get
> the idea
> > I2C was dead... but rather a new era of devices are on the way ;)
>
> I agree with the other Don, it's not spam at all. I've been
> searching around on I2C and there does seem to be a number
> of devices out there. I've printed the I2C spec and datasheets
> on an eeprom device as well as the LM75 temp sensor to read over.
>
> Thanks for the reply.
>
> Don
>
>
>
> To Post a message, send it to:   simmstick@e...
>
> To Unsubscribe, send a blank message to: simmstick-unsubscribe@e...
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>

> If your new to I2C, I'd suggest something like a PCF8574 
> for your first try... very simple to use... the eeprom gets 
> tricky at some points, or at least its harder to see what's 
> going on with it.

Thanks Brill. I've printed off various I2C stuff from Philips
and elsewhere to read over. Your right that the I/O expander
is probably the easiest thing to come up to speed on.

Don

> If your new to I2C, I'd suggest something like a PCF8574 
> for your first try... very simple to use... the eeprom 
gets 
> tricky at some points, or at least its harder to see 
what's 
> going on with it.

Thanks Brill. I've printed off various I2C stuff from 
Philips
and elsewhere to read over. Your right that the I/O expander
is probably the easiest thing to come up to speed on.

--------

Don,

Dontronics has a SimmStick that uses the PCF8574. It uses 
3, but only one need be populated.  
http://www.dontronics.com/dt209.html 

-Rob

I seem to be having trouble getting my mind around the
memory model. I'm going to read the datasheet over again
tonight and let the grey matter work on it a bit more.

I guess my problem is/was with the idea of two types of
program storage - eeprom and flash. The 128 bytes of
ram and 128 bytes of eeprom threw me off. The only
real ram are the registers. End of story. 

So basically you load your program into flash (up to 2k)
and you use eeprom for data you don't want to loose should
the board reboot ie. operating parameters, state info or
whatever - sound OK?

Don


--- In simmstick@y..., Ben Hitchcock <ben@w...> wrote:
> Hi Don,
> 
> AVR's use Harvard architecture, which means that the program is
stored  
> in a different portion of the chip to main RAM.  So the program
lives  
> in Flash, while the transient data that the program might use is
stored  
> in either registers or main RAM.  There is also another area of
AVR's  
> -- the EEPROM, which is useful for storing data that you don't want
to  
> disappear when the power turns off.
> 
> No instructions are 'copied across to main RAM' the way that  
> conventional processors work, for example the AT90S1200 doesn't
have  
> any RAM at all!  I think that single instructions are copied from
Flash  
> to some part of the processor before that instruction executes, but
you  
> don't need to worry about that as it is all deeply hidden from the
user.
> 
> Any questions, please feel free to ask.
> 
> Cheers,
> Ben
> 
> 
> On Wednesday, October 16, 2002, at 11:55  PM, dshesnicky wrote:
> 
> >
> > I can see how to program it and that's not my question.
> > How is the flash typically used on avrs? Are subroutines
> > stored there for access by main memory or does the flash
> > storage have to be copied into the main memory for usage?
> >
> > Excuse any ignorance over and above my usual level in the
> > above questions.
> >
> > Don
> >
> >
> > ------------------------ Yahoo! Groups Sponsor  
> > ---------------------~-->
> > 4 DVDs Free +s&p Join Now
> > http://us.click.yahoo.com/pt6YBB/NXiEAA/jd3IAA/CFFolB/TM
> >
--------------------------------------------------------------------- 
> > ~->
> >
> > To Post a message, send it to:   simmstick@e...
> >
> > To Unsubscribe, send a blank message to:  
> > simmstick-unsubscribe@e...
> >
> > Your use of Yahoo! Groups is subject to  
> > http://docs.yahoo.com/info/terms/
> >
> >

> I guess my problem is/was with the idea of two types of
> program storage - eeprom and flash. The 128 bytes of
> ram and 128 bytes of eeprom threw me off.

The FLASH is primarily program storage. Some languages allow you to also
place static or permanent data there also and access it at runtime. With the
classic AVRs FLASH cannot be self-modified however the Mega AVRs now have a
LPM instruction that will allow FLASH to be self-modified which is what the
boot loaders do

The EEPROM is semi-permanent DATA storage in that the data will survide a
power cycle but it can be changed by the program at runtime.

The RAM is volatile storage which will not survive a power cycle. RAM is
much faster to READ/WRITE compared to EEPROM and is used for general
variable storage

> The only real ram are the registers. End of story.

No not true. I think the Registers and RAM occupy the same memory space but
the Registers are first and have special functions and then the RAM comes
after that (except for a ATS901200 and others) with no special functions.

Cheers

Alex

I don't know how I got all screwed up on this topic but it
must have been a combination of age and too much fermented
turkey. Somehow I was picturing the eeprom as the location
for the uploaded programs and the combination of 128 bytes
of sram and 128 bytes of eeprom had me picturing it 
incorrectly. 

Anyway thanks to everyone for setting me straight.

Don

Sharon Burke wrote:
> 
> -------- Original Message --------
> Subject: Sales - via contact page
> Date: Fri, 25 Oct 2002 00:16:23 +1000
> From: steve vukosic <steve.vukosic@s...>
> To: Sales2003@d...
> 
> We are looking for someone to program 1K-10K pieces of 5 different
> programs, totaling about 100K/year.  Typically programming for the 8-pin
> Microchip devices.  Would you be interested?  Or are you only small
> quantities?  An suggestions who I can contact for higher volumes?

Hi Steve,
It is not the sort of work I am in a position to do, however I am
sending this message to my list of dealers, and my SimmStick group in
the hope that one of them will be able to assist.

I get a lot of these types of messages, and attempt to steer people in
the right direction, but it dawned on me, that I have a small group of
people involved in micros that could well be looking for this type of
work, or be able to advise you further.

Also I have a list of willing people at:
http://www.dontronics.com/meeting.html

good luck,
Cheers Don... 

Add USB to your favorite Micro.      http://www.dontronics.com/dlp.html
The World's Largest Range of Atmel/AVR & PICmicro Hardware and Software

  Please place (or leave -->) "dt2002" in the subject or body of your 
  message to guarantee your message getting through our spam filters.

Hi,

Many years ago I remember seeing an I2C evaluation bopard from Philips that
had one big PCB that could be cut up into smaller, single I2C function
units. Each unit was linked via a I2C cable with power and maybe a hardware
interrupt line.

However I cannot find any details on it or the cable pinout that is used.

Do any of you I2C guys know of any common I2C cable pinout specs or have any
comments about I2C cable lengths etc.

Cheers

Alex Shepherd

Alex Shepherd wrote:

> Hi,
>
> Many years ago I remember seeing an I2C evaluation bopard from Philips that
> had one big PCB that could be cut up into smaller, single I2C function
> units. Each unit was linked via a I2C cable with power and maybe a hardware
> interrupt line.
>
> However I cannot find any details on it or the cable pinout that is used.
>
> Do any of you I2C guys know of any common I2C cable pinout specs or have any
> comments about I2C cable lengths etc.
>
> Cheers
>
> Alex Shepherd

Hi,
I think I2C is intended for devices on a PCB or fairly close to it.
I have seen one system where they used I2C to 8Bit port for monitornig up to 128
digital i/p's
The micro was on a card in a "Eurocard" rack, the I/P cards were screwed to the
back and connected by ribbon cable with an IDC socket crunched on at intervals
and mated with header pins on each I/O board, using Vcc, Gnd, SDA and SCL
I have never seen specs giving cable length they often quote max capacitance!
There is a "bus extender" that is more tolerant of cable type so allows greater
distance, but again I know not "how far"
Hope this helps
Cheers

>
>
>
> To Post a message, send it to:   simmstick@e...
>
> To Unsubscribe, send a blank message to: simmstick-unsubscribe@e...
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

--
Leon Blakeley
CFA Communications
Ph (03) 92628400
Fax  (03) 92628383

PO Box 701
Mt. Waverley
3149

CAUTION - This message is intended for the use of the individual or
entity named above and may contain information that is confidential or
privileged.  If you are not the intended recipient of this message you
are hereby notified that any use, dissemination, distribution or
reproduction of this message is prohibited and that you must not take
any action in reliance on it.  If you have received this communication
in error, please notify CFA immediately and destroy the original
message.

In practical experience, I've used I2C on the end of a cable up to a meter
long... could likely get longer, but the main issue is the capacitance of
the cable (much has a 400pF maximum). you can make this work better with
"active" termination or put in repeaters or a hub.

As for pinout, it'll depend on the uC your using... most do it in software
anyway so it doesn't matter much.

The cabling is very simple... two lines, SCL (Clock) and SDA (Data) both
must be pulled-up, and is generally pulled-up by the uC instead of the
device (prevents creating voltage dividers as you add devices to the bus)
Pull-up resistors of 4.7k should work well, though its not critical (I've
used 1k often enough).

- Brill Pappin
  Rogue Robotics
  www.roguerobotics.com


----- Original Message -----
From: "Alex Shepherd" <ashepherd@w...>
To: <simmstick@yahoogroups.com>
Sent: Thursday, October 24, 2002 6:44 PM
Subject: [simmstick] I2C Cable Spec


> Hi,
>
> Many years ago I remember seeing an I2C evaluation bopard from Philips
that
> had one big PCB that could be cut up into smaller, single I2C function
> units. Each unit was linked via a I2C cable with power and maybe a
hardware
> interrupt line.
>
> However I cannot find any details on it or the cable pinout that is used.
>
> Do any of you I2C guys know of any common I2C cable pinout specs or have
any
> comments about I2C cable lengths etc.
>
> Cheers
>
> Alex Shepherd
>
>
>
> To Post a message, send it to:   simmstick@e...
>
> To Unsubscribe, send a blank message to: simmstick-unsubscribe@e...
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

Does anyone here happen to use the DT001 Simmstick programming board from
DonTronics along with Wiz-C and programs the PIC with WinPicProg. I have one
HEX file someone sent me as a test that I can program correctly into a
PIC16F877 (on the DT106 board). However, every program I compile from Wiz-C
does not program for some reason. I am guessing it has something to do with
the fuses however I am not sure. I have tried every possible fuse setting I
can think of. Right now I am using $393A. I have ruled out it has to do with
the hardware. If anyone has any luck with this combination please reply back
to me (either on or off the list).

Chris