XCSB Version 0.1.0 (ALPHA) is now available for download from:
        http://www.xcprod.com/titan/XCSB

XCSB LITE is free of charge for non-commercial use.

This is late ALPHA code so the documentation isn't great. Please don't be
shy, let me know of any problems you encounter so that we can fix them for
you.

Regards
Sergio Masci

------------------------------

Feature List

 * structured BASIC language

 * mixed mode 8, 16 and 32 bit optimising compiler (32 bit
    integer and floating point component not available with LITE
    version)

 * generates native 14 bit PIC core executable binary (suitable
    for direct execution on 16F84 and 16F628 - does not produce
    slow interpreted byte code)

 * directly accesses all page 0 control registers and RAM and
    indirectly accesses all page 0 and page 1 control registers
    and RAM

 * C style address of operator and pointer dereferencing (no need
    for peeks and pokes, resulting generated code is better
    optimised)

 * C style early out logical AND and OR operators

 * data (RAM) and code space arrays

 * 8 bit array indexing for efficient fast indexing

 * 16 bit array indexing allowing code space arrays greater than
    256 bytes

 * supports high level user defined functions in preference to
    'gosub' and 'call' statements

 * optimised generation of actual parameters used in function
    invokation based on user defined formal parameter list (known
    as function prototype in C language). Some compilers insist on
    generating a 'standard' parameter for every parameter which is
    not as efficient.

 * statically allocated function context for fast execution

 * function call analysis for efficient RAM reuse

 * function local variables and arrays

 * no limit on variable or function name length

 * supports labels in preference to line numbers

 * uses XCASM meta assembler for machine code generation
    (potential to retarget executable to alternate processor
    including user designed custom FPGA implemented processor)

 * source level debugging when used in combination with XCSIM
    simulator

 * part of the XC product line which includes ZMech, XEBOT and
    IPAD-Pro

At 12:17 PM 14/09/02, you wrote:
 >XCSB Version 0.1.0 (ALPHA) is now available for download from:
 >        http://www.xcprod.com/titan/XCSB

Probably would be a good idea to mention that the ONLY platform currently 
supported appears to be Linux.

pseakins@a... wrote:
> At 12:17 PM 14/09/02, you wrote:
>  >XCSB Version 0.1.0 (ALPHA) is now available for download from:
>  >        http://www.xcprod.com/titan/XCSB
> 
> Probably would be a good idea to mention that the ONLY platform currently 
> supported appears to be Linux.

Appearences can be deceptive

Supported platforms:
  Linux 2.2.x and higher (Intel x86 only)
  Solaris 8 (Intel & SPARC)
  MS Windows 9x
  MS Windows 3.1
  MS DOS 3 and higher
  OS/2 3 and higher
  HPUX 11 (PA-RISC not yet but soon)

The Linux version is currently the only version that has been uploaded but Linux is not the only platform currently supported. I had intended to upload the other versions within 24 hours of the Linux version but something else came up which needed my attention.

Regards
Sergio Masci

I am attempting to build an RS485 board using the DT107 Simmstick but 
am having difficulty finding an RJ45 socket to fit. Has anyone found 
a part that works?

Ok, Win9x and OS/2 versions have now been uploaded

Regards
Sergio Masci

Hi Group

I've been using my dt006 with standard 90s2313 chip for a year or two.
Everything's working fine. A few days ago I've solder the 8-pin 
socket in trying to program a 90s2323. But Bascom cant identify it. 
Pulling the 8-pin micro out and putting the old 90s2313 back again 
everything's working again, meaning cables and board are ok.

Does anyone have any clue what's wrong. ????

Sincerly

Steen Thunberg
Denmark

----- Original Message -----
From: "thunbergs" <steen@t...>
To: <simmstick@yahoogroups.com>
Sent: Tuesday, September 17, 2002 8:29 AM
Subject: [simmstick] Can't identify a 90s2323 on a DT006


> Hi Group
>
> I've been using my dt006 with standard 90s2313 chip for a year or two.
> Everything's working fine. A few days ago I've solder the 8-pin
> socket in trying to program a 90s2323. But Bascom cant identify it.
> Pulling the 8-pin micro out and putting the old 90s2313 back again
> everything's working again, meaning cables and board are ok.

Atmel might have changed the ID code. They did this a couple of years ago
with the 1200. I got round the problem by a minor hack of the SP12 source
code.

Leon
--
Leon Heller, G1HSM
leon_heller@h...
http://www.geocities.com/leon_heller

Gday Thunbergs,

thunbergs wrote:

> Hi Group
> 
> I've been using my dt006 with standard 90s2313 chip for a year or two.
> Everything's working fine. A few days ago I've solder the 8-pin 
> socket in trying to program a 90s2323. But Bascom cant identify it. 
> Pulling the 8-pin micro out and putting the old 90s2313 back again 
> everything's working again, meaning cables and board are ok.
> 
> Does anyone have any clue what's wrong. ????
> 
> Sincerly
> 
> Steen Thunberg
> Denmark

I think you will find that it is to do with the links ( J11 & J12 ).... 
see dons instructions here:

http://dontronics.com/dt006_assembly.html

It has been a long time since I playe with a dt006 so my memory may be 
rusty.

regards Mick

Hi Leon

How can I find out if they changed the id-code, and how do I solve 
it ?
"a minor hack in the sp12"..what does it means ?

sincerly

steen



--- In simmstick@y..., "Leon Heller" <leon_heller@h...> wrote:
> 
> ----- Original Message -----
> From: "thunbergs" <steen@t...>
> To: <simmstick@y...>
> Sent: Tuesday, September 17, 2002 8:29 AM
> Subject: [simmstick] Can't identify a 90s2323 on a DT006
> 
> 
> > Hi Group
> >
> > I've been using my dt006 with standard 90s2313 chip for a year or 
two.
> > Everything's working fine. A few days ago I've solder the 8-pin
> > socket in trying to program a 90s2323. But Bascom cant identify 
it.
> > Pulling the 8-pin micro out and putting the old 90s2313 back again
> > everything's working again, meaning cables and board are ok.
> 
> Atmel might have changed the ID code. They did this a couple of 
years ago
> with the 1200. I got round the problem by a minor hack of the SP12 
source
> code.
> 
> Leon
> --
> Leon Heller, G1HSM
> leon_heller@h...
> http://www.geocities.com/leon_heller

Hi All,
There is a new mailing list for the PIC edition of XCSB (optimising
structured BASIC compiler). You can get to it via
http://www.xcprod.com/titan/XCSB

Regards
Sergio Masci

I have a dt001 doard and using nigel goodwin win pic prog software.  
When I load a pic program ( c or wl84.hex) onto win pic prog I am 
getting an error message - fuses not set in loaded file.

the program dissasembles ok but when I download onto pic I am getting 
error - program verify failed at program address 0x000, programming 
aborted.


The test programs and dt001 work on my friends computer.  any ideas??

Hi.

I code in C, but don't know how to code PIC-specific C code (I don't 
know how to manage inputs and outputs). What I need is really simple:
I'm gonna use 2 inputs and one output and they must behave like this:
If input 1 is low, any pulse coming from input 2 should be redirected 
to the output.
If input 1 is high, any pulse coming from input 2 should be stored in 
memory and sent when input 1 goes low. The C program should look like 
this:

void main()
{
  int input1, input2, output, stored=0;

  if(!input1 && input2)
    output=input2;

  if(input1 && input2)
    stored++;

  if(!input1 && stored)
  {
    output=stored;
    stored--;
    delay(1000);
  }
}

I just don't know how to interface the inputs and outputs from that C 
code, i.e. don't know where to point them.
Do I need a clock? Or an RC clock should be fine?
Any help would be really appreciated, thanks in advance.
Cheers,
Marton.

Hi All

I've been developing code for the AT90S8535 and have run out of code space
with still a lot to do. I'll need to upgrade to one of the AT-MEGA series
that have 16k FLASH.

Does anybody know offhand which of the MEGA series is the closest in terms
of registers etc - I'm looking for the easiest upgrade path in order to
minimise code re-writes. 40-pin DIP compatibilty would also be nice. I know
I can spend a day downloading and reading data sheets but I thought somebody
may have already been here before :)

Many TIA

Steve



E-Book publishing and marketing resources
www.e-bookmarket.com

Hi

http://www.mozzarella.jp/hardware/c8051f30x/
there is HEX file and Windows EXE (Also sources)

when flashed into S2313 a SimmStick becomes a programmer
for Cygnal micros with C2 interface (F30x, F31x?)

http://www.cygnal.com/products/C8051F300.htm

the device is pretty cool too and comes in a 11 Pin Package!
I was once joking about 9 Pin AVRs - they are not yet here,
but 11 Pin 8051s are :)

just for info that SimmStick platform can be used as programmer
(instead of bying the Cygnal 99 USD programmer).

The programmer has be checked, did build it, made a C8051F300
SimmStick out of proto and it worked right first attempt!

Antti

Hi, can any of you guys help me here? Basically I wish to use a 
SIMM100 and Mega16, with a STK200 to my computers parallel port. I 
wish to do all programming in Linux, using AVR-GCC, and PonyProg as 
the programmer.

The questions I have may be somewhat basic, but I'm having a hard 
time finding the answers...

i) Is what I'm trying to do is feasible? and will it be ok?
ii) Where can I purchase the Mega16 in Oz, Don doesn't seem to sell 
them.
iii) Where can I get a STK200 adapter from? I'd prefer not to make my 
own, but have seen the schematics of simple solutions.
iv) What PC program is best used to build a schematic, and hence PCB 
layout?

Thats all for my newbie questions, I even tried looking in the 
archives, but I didn't go back too far, sorry if this has been 
repeated before.

Thanks in advance, Davin.

Hi Marton,

I'm afraid I don't code in C, however I should be able to solve your problem 
quickly enough in either PIC-BASIC or assembler. Part 1 is easy enough, but 
with part 2 did you require the length of the pulse to be stored for 
re-transmission when input 1 goes high again? If so what is the likely 
maximum/minimum length of the pulse to be stored and would you need to store 
multiple pulses and the gaps between them?

Regards
Tim


Hi.

I code in C, but don't know how to code PIC-specific C code (I don't
know how to manage inputs and outputs). What I need is really simple:
I'm gonna use 2 inputs and one output and they must behave like this:
If input 1 is low, any pulse coming from input 2 should be redirected
to the output.
If input 1 is high, any pulse coming from input 2 should be stored in
memory and sent when input 1 goes low. The C program should look like
this:

void main()
{
  int input1, input2, output, stored=0;

  if(!input1 && input2)
    output=input2;

  if(input1 && input2)
    stored++;

  if(!input1 && stored)
  {
    output=stored;
    stored--;
    delay(1000);
  }
}

I just don't know how to interface the inputs and outputs from that C
code, i.e. don't know where to point them.
Do I need a clock? Or an RC clock should be fine?
Any help would be really appreciated, thanks in advance.
Cheers,
Marton.






_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Hi Tim,

Thanks for your reply, I really appreciate it.
Answering your questions:
It doesn't need to know the lenght of the pulse, it can be fixed at, 
say 250~500ms. It needs to count the pulses for sending them when 
input 1 goes low, but not the gaps. It isn't really hard but having 
no experience with pics or asm for pics I'm stuck for starting.
Also, for part 1 it can send the fixed pulse, too. It doesn't need to 
be exact in timings.
An example of operation for part 2:
Input 1 is high, I send three pulses to input 2, it counts and stores 
them.
Then at some moment I drop input 1, so it starts sending the pulses 
one-at-a-time (say with a delay of 1 sec) thru the output.
When I'm flushing the pulses, some more can come thru input 2 and 
part 1 must take care of it, but input 1 will not be a problem at 
that time because it will not go high for enough time to flush 
everything.
For a side note, input 2 and the output are active low.
Thanks for any help you can give me.

Best regards,
Marton.

--- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> Hi Marton,
> 
> I'm afraid I don't code in C, however I should be able to solve 
your problem 
> quickly enough in either PIC-BASIC or assembler. Part 1 is easy 
enough, but 
> with part 2 did you require the length of the pulse to be stored 
for 
> re-transmission when input 1 goes high again? If so what is the 
likely 
> maximum/minimum length of the pulse to be stored and would you need 
to store 
> multiple pulses and the gaps between them?
> 
> Regards
> Tim
> 
> 
> Hi.
> 
> I code in C, but don't know how to code PIC-specific C code (I don't
> know how to manage inputs and outputs). What I need is really 
simple:
> I'm gonna use 2 inputs and one output and they must behave like 
this:
> If input 1 is low, any pulse coming from input 2 should be 
redirected
> to the output.
> If input 1 is high, any pulse coming from input 2 should be stored 
in
> memory and sent when input 1 goes low. The C program should look 
like
> this:
> 
> void main()
> {
>   int input1, input2, output, stored=0;
> 
>   if(!input1 && input2)
>     output=input2;
> 
>   if(input1 && input2)
>     stored++;
> 
>   if(!input1 && stored)
>   {
>     output=stored;
>     stored--;
>     delay(1000);
>   }
> }
> 
> I just don't know how to interface the inputs and outputs from that 
C
> code, i.e. don't know where to point them.
> Do I need a clock? Or an RC clock should be fine?
> Any help would be really appreciated, thanks in advance.
> Cheers,
> Marton.
> 
> 
> 
> 
> 
> 
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx

Anyone tried to use the ATMega163 with the SIMM100 yet?

I've been taking a look and it seems as if all the important pins will match
up (xtal etc.) they didn't bother to look at other devices, so the I2C pins
are in the wrong place, but other than that, mostly looks ok.

Thought I'd ask before trying it.

- Brill Pappin
  Rogue Robotics
  www.roguerobotics.com


----- Original Message -----
From: "karura79" <karura79@y...>
To: <simmstick@yahoogroups.com>
Sent: Tuesday, September 24, 2002 6:12 AM
Subject: [simmstick] Re: Newbie needs help with 16F84


> Hi Tim,
>
> Thanks for your reply, I really appreciate it.
> Answering your questions:
> It doesn't need to know the lenght of the pulse, it can be fixed at,
> say 250~500ms. It needs to count the pulses for sending them when
> input 1 goes low, but not the gaps. It isn't really hard but having
> no experience with pics or asm for pics I'm stuck for starting.
> Also, for part 1 it can send the fixed pulse, too. It doesn't need to
> be exact in timings.
> An example of operation for part 2:
> Input 1 is high, I send three pulses to input 2, it counts and stores
> them.
> Then at some moment I drop input 1, so it starts sending the pulses
> one-at-a-time (say with a delay of 1 sec) thru the output.
> When I'm flushing the pulses, some more can come thru input 2 and
> part 1 must take care of it, but input 1 will not be a problem at
> that time because it will not go high for enough time to flush
> everything.
> For a side note, input 2 and the output are active low.
> Thanks for any help you can give me.
>
> Best regards,
> Marton.
>
> --- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> > Hi Marton,
> >
> > I'm afraid I don't code in C, however I should be able to solve
> your problem
> > quickly enough in either PIC-BASIC or assembler. Part 1 is easy
> enough, but
> > with part 2 did you require the length of the pulse to be stored
> for
> > re-transmission when input 1 goes high again? If so what is the
> likely
> > maximum/minimum length of the pulse to be stored and would you need
> to store
> > multiple pulses and the gaps between them?
> >
> > Regards
> > Tim
> >
> >
> > Hi.
> >
> > I code in C, but don't know how to code PIC-specific C code (I don't
> > know how to manage inputs and outputs). What I need is really
> simple:
> > I'm gonna use 2 inputs and one output and they must behave like
> this:
> > If input 1 is low, any pulse coming from input 2 should be
> redirected
> > to the output.
> > If input 1 is high, any pulse coming from input 2 should be stored
> in
> > memory and sent when input 1 goes low. The C program should look
> like
> > this:
> >
> > void main()
> > {
> >   int input1, input2, output, stored=0;
> >
> >   if(!input1 && input2)
> >     output=input2;
> >
> >   if(input1 && input2)
> >     stored++;
> >
> >   if(!input1 && stored)
> >   {
> >     output=stored;
> >     stored--;
> >     delay(1000);
> >   }
> > }
> >
> > I just don't know how to interface the inputs and outputs from that
> C
> > code, i.e. don't know where to point them.
> > Do I need a clock? Or an RC clock should be fine?
> > Any help would be really appreciated, thanks in advance.
> > Cheers,
> > Marton.
> >
> >
> >
> >
> >
> >
> > _________________________________________________________________
> > MSN Photos is the easiest way to share and print your photos:
> > http://photos.msn.com/support/worldwide.aspx
>
>
>
> 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/
>
>
>

Hi there

I'm sure the ATMega163 will be fine, but read up on the Mega163 first, it 
has a few bugs!    The Mega163 is now flagged a "not to be used in new 
designs" Atmel part and so I would not spent too much time on it.  Look 
towards the ATMega16, it is faster, bug free and cheaper ( 35 um from 50 
um)!   (The ATMega16 has a slower EEPROM write cycle, but is more reliable).

Regards


Bob W

At 12:59 AM 9/25/2002 -0400, you wrote:
>Anyone tried to use the ATMega163 with the SIMM100 yet?
>
>I've been taking a look and it seems as if all the important pins will match
>up (xtal etc.) they didn't bother to look at other devices, so the I2C pins
>are in the wrong place, but other than that, mostly looks ok.
>
>Thought I'd ask before trying it.
>
>- Brill Pappin
>   Rogue Robotics
>   www.roguerobotics.com
>
>
>----- Original Message -----
>From: "karura79" <karura79@y...>
>To: <simmstick@yahoogroups.com>
>Sent: Tuesday, September 24, 2002 6:12 AM
>Subject: [simmstick] Re: Newbie needs help with 16F84
>
>
> > Hi Tim,
> >
> > Thanks for your reply, I really appreciate it.
> > Answering your questions:
> > It doesn't need to know the lenght of the pulse, it can be fixed at,
> > say 250~500ms. It needs to count the pulses for sending them when
> > input 1 goes low, but not the gaps. It isn't really hard but having
> > no experience with pics or asm for pics I'm stuck for starting.
> > Also, for part 1 it can send the fixed pulse, too. It doesn't need to
> > be exact in timings.
> > An example of operation for part 2:
> > Input 1 is high, I send three pulses to input 2, it counts and stores
> > them.
> > Then at some moment I drop input 1, so it starts sending the pulses
> > one-at-a-time (say with a delay of 1 sec) thru the output.
> > When I'm flushing the pulses, some more can come thru input 2 and
> > part 1 must take care of it, but input 1 will not be a problem at
> > that time because it will not go high for enough time to flush
> > everything.
> > For a side note, input 2 and the output are active low.
> > Thanks for any help you can give me.
> >
> > Best regards,
> > Marton.
> >
> > --- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> > > Hi Marton,
> > >
> > > I'm afraid I don't code in C, however I should be able to solve
> > your problem
> > > quickly enough in either PIC-BASIC or assembler. Part 1 is easy
> > enough, but
> > > with part 2 did you require the length of the pulse to be stored
> > for
> > > re-transmission when input 1 goes high again? If so what is the
> > likely
> > > maximum/minimum length of the pulse to be stored and would you need
> > to store
> > > multiple pulses and the gaps between them?
> > >
> > > Regards
> > > Tim
> > >
> > >
> > > Hi.
> > >
> > > I code in C, but don't know how to code PIC-specific C code (I don't
> > > know how to manage inputs and outputs). What I need is really
> > simple:
> > > I'm gonna use 2 inputs and one output and they must behave like
> > this:
> > > If input 1 is low, any pulse coming from input 2 should be
> > redirected
> > > to the output.
> > > If input 1 is high, any pulse coming from input 2 should be stored
> > in
> > > memory and sent when input 1 goes low. The C program should look
> > like
> > > this:
> > >
> > > void main()
> > > {
> > >   int input1, input2, output, stored=0;
> > >
> > >   if(!input1 && input2)
> > >     output=input2;
> > >
> > >   if(input1 && input2)
> > >     stored++;
> > >
> > >   if(!input1 && stored)
> > >   {
> > >     output=stored;
> > >     stored--;
> > >     delay(1000);
> > >   }
> > > }
> > >
> > > I just don't know how to interface the inputs and outputs from that
> > C
> > > code, i.e. don't know where to point them.
> > > Do I need a clock? Or an RC clock should be fine?
> > > Any help would be really appreciated, thanks in advance.
> > > Cheers,
> > > Marton.
> > >
> > >
> > >
> > >
> > >
> > >
> > > _________________________________________________________________
> > > MSN Photos is the easiest way to share and print your photos:
> > > http://photos.msn.com/support/worldwide.aspx
> >
> >
> >
> > 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/
> >
> >
> >
>
>
>
>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/

<chuckle>
No wonder they sent me a large quantity of 163's when I only asked for a few
samples!
My samples came, with about 5 extra 163's I guess they had stock they needed
to dump.

- Brill Pappin
  Rogue Robotics
  www.roguerobotics.com


----- Original Message -----
From: "Bob Woodhead" <bob@w...>
To: <simmstick@yahoogroups.com>
Sent: Wednesday, September 25, 2002 6:15 AM
Subject: Re: [simmstick] ATMega163 with the SIMM100


> Hi there
>
> I'm sure the ATMega163 will be fine, but read up on the Mega163 first, it
> has a few bugs!    The Mega163 is now flagged a "not to be used in new
> designs" Atmel part and so I would not spent too much time on it.  Look
> towards the ATMega16, it is faster, bug free and cheaper ( 35 um from 50
> um)!   (The ATMega16 has a slower EEPROM write cycle, but is more
reliable).
>
> Regards
>
>
> Bob W
>
> At 12:59 AM 9/25/2002 -0400, you wrote:
> >Anyone tried to use the ATMega163 with the SIMM100 yet?
> >
> >I've been taking a look and it seems as if all the important pins will
match
> >up (xtal etc.) they didn't bother to look at other devices, so the I2C
pins
> >are in the wrong place, but other than that, mostly looks ok.
> >
> >Thought I'd ask before trying it.
> >
> >- Brill Pappin
> >   Rogue Robotics
> >   www.roguerobotics.com
> >
> >
> >----- Original Message -----
> >From: "karura79" <karura79@y...>
> >To: <simmstick@yahoogroups.com>
> >Sent: Tuesday, September 24, 2002 6:12 AM
> >Subject: [simmstick] Re: Newbie needs help with 16F84
> >
> >
> > > Hi Tim,
> > >
> > > Thanks for your reply, I really appreciate it.
> > > Answering your questions:
> > > It doesn't need to know the lenght of the pulse, it can be fixed at,
> > > say 250~500ms. It needs to count the pulses for sending them when
> > > input 1 goes low, but not the gaps. It isn't really hard but having
> > > no experience with pics or asm for pics I'm stuck for starting.
> > > Also, for part 1 it can send the fixed pulse, too. It doesn't need to
> > > be exact in timings.
> > > An example of operation for part 2:
> > > Input 1 is high, I send three pulses to input 2, it counts and stores
> > > them.
> > > Then at some moment I drop input 1, so it starts sending the pulses
> > > one-at-a-time (say with a delay of 1 sec) thru the output.
> > > When I'm flushing the pulses, some more can come thru input 2 and
> > > part 1 must take care of it, but input 1 will not be a problem at
> > > that time because it will not go high for enough time to flush
> > > everything.
> > > For a side note, input 2 and the output are active low.
> > > Thanks for any help you can give me.
> > >
> > > Best regards,
> > > Marton.
> > >
> > > --- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> > > > Hi Marton,
> > > >
> > > > I'm afraid I don't code in C, however I should be able to solve
> > > your problem
> > > > quickly enough in either PIC-BASIC or assembler. Part 1 is easy
> > > enough, but
> > > > with part 2 did you require the length of the pulse to be stored
> > > for
> > > > re-transmission when input 1 goes high again? If so what is the
> > > likely
> > > > maximum/minimum length of the pulse to be stored and would you need
> > > to store
> > > > multiple pulses and the gaps between them?
> > > >
> > > > Regards
> > > > Tim
> > > >
> > > >
> > > > Hi.
> > > >
> > > > I code in C, but don't know how to code PIC-specific C code (I don't
> > > > know how to manage inputs and outputs). What I need is really
> > > simple:
> > > > I'm gonna use 2 inputs and one output and they must behave like
> > > this:
> > > > If input 1 is low, any pulse coming from input 2 should be
> > > redirected
> > > > to the output.
> > > > If input 1 is high, any pulse coming from input 2 should be stored
> > > in
> > > > memory and sent when input 1 goes low. The C program should look
> > > like
> > > > this:
> > > >
> > > > void main()
> > > > {
> > > >   int input1, input2, output, stored=0;
> > > >
> > > >   if(!input1 && input2)
> > > >     output=input2;
> > > >
> > > >   if(input1 && input2)
> > > >     stored++;
> > > >
> > > >   if(!input1 && stored)
> > > >   {
> > > >     output=stored;
> > > >     stored--;
> > > >     delay(1000);
> > > >   }
> > > > }
> > > >
> > > > I just don't know how to interface the inputs and outputs from that
> > > C
> > > > code, i.e. don't know where to point them.
> > > > Do I need a clock? Or an RC clock should be fine?
> > > > Any help would be really appreciated, thanks in advance.
> > > > Cheers,
> > > > Marton.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _________________________________________________________________
> > > > MSN Photos is the easiest way to share and print your photos:
> > > > http://photos.msn.com/support/worldwide.aspx
> > >
> > >
> > >
> > > 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/
> > >
> > >
> > >
> >
> >
> >
> >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/
>
>
>
> 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/
>
>

BTW - Any docs on what the bugs are?

I'm thinking it might be a cheaper chip  for a new design, if I don't need
to do anything that causes the bugs to activate.

- Brill Pappin
  Rogue Robotics
  www.roguerobotics.com


----- Original Message -----
From: "Bob Woodhead" <bob@w...>
To: <simmstick@yahoogroups.com>
Sent: Wednesday, September 25, 2002 6:15 AM
Subject: Re: [simmstick] ATMega163 with the SIMM100


> Hi there
>
> I'm sure the ATMega163 will be fine, but read up on the Mega163 first, it
> has a few bugs!    The Mega163 is now flagged a "not to be used in new
> designs" Atmel part and so I would not spent too much time on it.  Look
> towards the ATMega16, it is faster, bug free and cheaper ( 35 um from 50
> um)!   (The ATMega16 has a slower EEPROM write cycle, but is more
reliable).
>
> Regards
>
>
> Bob W
>
> At 12:59 AM 9/25/2002 -0400, you wrote:
> >Anyone tried to use the ATMega163 with the SIMM100 yet?
> >
> >I've been taking a look and it seems as if all the important pins will
match
> >up (xtal etc.) they didn't bother to look at other devices, so the I2C
pins
> >are in the wrong place, but other than that, mostly looks ok.
> >
> >Thought I'd ask before trying it.
> >
> >- Brill Pappin
> >   Rogue Robotics
> >   www.roguerobotics.com
> >
> >
> >----- Original Message -----
> >From: "karura79" <karura79@y...>
> >To: <simmstick@yahoogroups.com>
> >Sent: Tuesday, September 24, 2002 6:12 AM
> >Subject: [simmstick] Re: Newbie needs help with 16F84
> >
> >
> > > Hi Tim,
> > >
> > > Thanks for your reply, I really appreciate it.
> > > Answering your questions:
> > > It doesn't need to know the lenght of the pulse, it can be fixed at,
> > > say 250~500ms. It needs to count the pulses for sending them when
> > > input 1 goes low, but not the gaps. It isn't really hard but having
> > > no experience with pics or asm for pics I'm stuck for starting.
> > > Also, for part 1 it can send the fixed pulse, too. It doesn't need to

> > > be exact in timings.
> > > An example of operation for part 2:
> > > Input 1 is high, I send three pulses to input 2, it counts and stores
> > > them.
> > > Then at some moment I drop input 1, so it starts sending the pulses
> > > one-at-a-time (say with a delay of 1 sec) thru the output.
> > > When I'm flushing the pulses, some more can come thru input 2 and
> > > part 1 must take care of it, but input 1 will not be a problem at
> > > that time because it will not go high for enough time to flush
> > > everything.
> > > For a side note, input 2 and the output are active low.
> > > Thanks for any help you can give me.
> > >
> > > Best regards,
> > > Marton.
> > >
> > > --- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> > > > Hi Marton,
> > > >
> > > > I'm afraid I don't code in C, however I should be able to solve
> > > your problem
> > > > quickly enough in either PIC-BASIC or assembler. Part 1 is easy
> > > enough, but
> > > > with part 2 did you require the length of the pulse to be stored
> > > for
> > > > re-transmission when input 1 goes high again? If so what is the
> > > likely
> > > > maximum/minimum length of the pulse to be stored and would you need
> > > to store
> > > > multiple pulses and the gaps between them?
> > > >
> > > > Regards
> > > > Tim
> > > >
> > > >
> > > > Hi.
> > > >
> > > > I code in C, but don't know how to code PIC-specific C code (I don't
> > > > know how to manage inputs and outputs). What I need is really
> > > simple:
> > > > I'm gonna use 2 inputs and one output and they must behave like
> > > this:
> > > > If input 1 is low, any pulse coming from input 2 should be
> > > redirected
> > > > to the output.
> > > > If input 1 is high, any pulse coming from input 2 should be stored
> > > in
> > > > memory and sent when input 1 goes low. The C program should look
> > > like
> > > > this:
> > > >
> > > > void main()
> > > > {
> > > >   int input1, input2, output, stored=0;
> > > >
> > > >   if(!input1 && input2)
> > > >     output=input2;
> > > >
> > > >   if(input1 && input2)
> > > >     stored++;
> > > >
> > > >   if(!input1 && stored)
> > > >   {
> > > >     output=stored;
> > > >     stored--;
> > > >     delay(1000);
> > > >   }
> > > > }
> > > >
> > > > I just don't know how to interface the inputs and outputs from that
> > > C
> > > > code, i.e. don't know where to point them.
> > > > Do I need a clock? Or an RC clock should be fine?
> > > > Any help would be really appreciated, thanks in advance.
> > > > Cheers,
> > > > Marton.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _________________________________________________________________
> > > > MSN Photos is the easiest way to share and print your photos:
> > > > http://photos.msn.com/support/worldwide.aspx
> > >
> > >
> > >
> > > 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/
> > >
> > >
> > >
> >
> >
> >
> >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/
>
>
>
> 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/
>
>

Hi,

> BTW - Any docs on what the bugs are?

Surf over to www.avrfreaks.net and download the errata sheet
for it. There are not that many bugs and I have many applications
using it, so I had no problem.

Regading SIMM100, it works fine with 8535, Mega163, Mega323, Mega16 &
Mega32.

I2C bus is on wrong place, but of course I didn't know about the Mega's
when I made the SIMM100 board, since it was before their time.

/Lars

> I'm thinking it might be a cheaper chip  for a new design, if I don't need
> to do anything that causes the bugs to activate.
>
> - Brill Pappin
>   Rogue Robotics
>   www.roguerobotics.com
>
>
> ----- Original Message -----
> From: "Bob Woodhead" <bob@w...>
> To: <simmstick@yahoogroups.com>
> Sent: Wednesday, September 25, 2002 6:15 AM
> Subject: Re: [simmstick] ATMega163 with the SIMM100
>
>
> > Hi there
> >
> > I'm sure the ATMega163 will be fine, but read up on the Mega163 first,
it
> > has a few bugs!    The Mega163 is now flagged a "not to be used in new
> > designs" Atmel part and so I would not spent too much time on it.  Look
> > towards the ATMega16, it is faster, bug free and cheaper ( 35 um from 50
> > um)!   (The ATMega16 has a slower EEPROM write cycle, but is more
> reliable).
> >
> > Regards
> >
> >
> > Bob W
> >
> > At 12:59 AM 9/25/2002 -0400, you wrote:
> > >Anyone tried to use the ATMega163 with the SIMM100 yet?
> > >
> > >I've been taking a look and it seems as if all the important pins will
> match
> > >up (xtal etc.) they didn't bother to look at other devices, so the I2C
> pins
> > >are in the wrong place, but other than that, mostly looks ok.
> > >
> > >Thought I'd ask before trying it.
> > >
> > >- Brill Pappin
> > >   Rogue Robotics
> > >   www.roguerobotics.com
> > >
> > >
> > >----- Original Message -----
> > >From: "karura79" <karura79@y...>
> > >To: <simmstick@yahoogroups.com>
> > >Sent: Tuesday, September 24, 2002 6:12 AM
> > >Subject: [simmstick] Re: Newbie needs help with 16F84
> > >
> > >
> > > > Hi Tim,
> > > >
> > > > Thanks for your reply, I really appreciate it.
> > > > Answering your questions:
> > > > It doesn't need to know the lenght of the pulse, it can be fixed at,
> > > > say 250~500ms. It needs to count the pulses for sending them when
> > > > input 1 goes low, but not the gaps. It isn't really hard but having
> > > > no experience with pics or asm for pics I'm stuck for starting.
> > > > Also, for part 1 it can send the fixed pulse, too. It doesn't need
to
>
> > > > be exact in timings.
> > > > An example of operation for part 2:
> > > > Input 1 is high, I send three pulses to input 2, it counts and
stores
> > > > them.
> > > > Then at some moment I drop input 1, so it starts sending the pulses
> > > > one-at-a-time (say with a delay of 1 sec) thru the output.
> > > > When I'm flushing the pulses, some more can come thru input 2 and
> > > > part 1 must take care of it, but input 1 will not be a problem at
> > > > that time because it will not go high for enough time to flush
> > > > everything.
> > > > For a side note, input 2 and the output are active low.
> > > > Thanks for any help you can give me.
> > > >
> > > > Best regards,
> > > > Marton.
> > > >
> > > > --- In simmstick@y..., "Big Tim" <big_tim88@h...> wrote:
> > > > > Hi Marton,
> > > > >
> > > > > I'm afraid I don't code in C, however I should be able to solve
> > > > your problem
> > > > > quickly enough in either PIC-BASIC or assembler. Part 1 is easy
> > > > enough, but
> > > > > with part 2 did you require the length of the pulse to be stored
> > > > for
> > > > > re-transmission when input 1 goes high again? If so what is the
> > > > likely
> > > > > maximum/minimum length of the pulse to be stored and would you
need
> > > > to store
> > > > > multiple pulses and the gaps between them?
> > > > >
> > > > > Regards
> > > > > Tim
> > > > >
> > > > >
> > > > > Hi.
> > > > >
> > > > > I code in C, but don't know how to code PIC-specific C code (I
don't
> > > > > know how to manage inputs and outputs). What I need is really
> > > > simple:
> > > > > I'm gonna use 2 inputs and one output and they must behave like
> > > > this:
> > > > > If input 1 is low, any pulse coming from input 2 should be
> > > > redirected
> > > > > to the output.
> > > > > If input 1 is high, any pulse coming from input 2 should be stored
> > > > in
> > > > > memory and sent when input 1 goes low. The C program should look
> > > > like
> > > > > this:
> > > > >
> > > > > void main()
> > > > > {
> > > > >   int input1, input2, output, stored=0;
> > > > >
> > > > >   if(!input1 && input2)
> > > > >     output=input2;
> > > > >
> > > > >   if(input1 && input2)
> > > > >     stored++;
> > > > >
> > > > >   if(!input1 && stored)
> > > > >   {
> > > > >     output=stored;
> > > > >     stored--;
> > > > >     delay(1000);
> > > > >   }
> > > > > }
> > > > >
> > > > > I just don't know how to interface the inputs and outputs from
that
> > > > C
> > > > > code, i.e. don't know where to point them.
> > > > > Do I need a clock? Or an RC clock should be fine?
> > > > > Any help would be really appreciated, thanks in advance.
> > > > > Cheers,
> > > > > Marton.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > MSN Photos is the easiest way to share and print your photos:
> > > > > http://photos.msn.com/support/worldwide.aspx
> > > >
> > > >
> > > >
> > > > 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/
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >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/
> >
> >
> >
> > 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/
> >
> >
>
>
>
> 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/
>
>
>

> I2C bus is on wrong place, but of course I didn't know about the Mega's
> when I made the SIMM100 board, since it was before their time.

Ahh... that would explain it :) seems like a very small change that would
make the product even better (for cross compatibility etc.). Anyway, maybe
in your next run.

- Brill Pappin

I keep getting emails from people telling me that STV5730A is back, 
anyone know of any official notice from ST on this?
Incidently, one person who emailed from the UK said that one of his 
local suppliers has 140,000 in stock, believe that if you will.

Dave :)

I am planning to remotely control my digital Olympus camera using an AVR and serial comm 
(Max232) in a RC model heli. 
It may be a good idea to have a more universal system that could handle the newer cameras 
as well, which all seems to be using USB.
Would it be possible to use one of the USBMOD1 modules to do this?
I noticed that it draws its power from the USB bus, but would a digicam be able to 
deliver this? Is that module only for connecting to a PCs USB port?

-- Bjorn Kare Nilssen http://bjornkn.home.online.no/ old 3D stuff
   Kristiansand, Norway

Hi,

Do not use the "old" USBMOD1, use instead the new DLP-USB232M instead,
see www.ftdichip.com for more information.

The way you want to do it, no, it can't be done!
The reason is simple, all cameras are Slave USB, so is the above tools.
You need a Master implementation to talk to USB slaves and that isn't
easy since it is only PC's etc. who has this functionallity.

/Lars

> I am planning to remotely control my digital Olympus camera using an AVR
and serial comm
> (Max232) in a RC model heli.
> It may be a good idea to have a more universal system that could handle
the newer cameras
> as well, which all seems to be using USB.
> Would it be possible to use one of the USBMOD1 modules to do this?
> I noticed that it draws its power from the USB bus, but would a digicam be
able to
> deliver this? Is that module only for connecting to a PCs USB port?
>
> -- Bjorn Kare Nilssen http://bjornkn.home.online.no/ old 3D stuff
>    Kristiansand, Norway
>
>
>
> 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/
>
>
>

My DT006 from Dontronics arrived. I found a straight through
parallel cable and a 12V power brick. I've hooked everything
up and the leds are blinking with the test program. I've got
AVRStudio4 loaded but I don't know how to program the board.

I want to program in assembler. Questions 1 and 2 follow.

1. How do I actually download a program into the DT006 board?
I've tried some options in AVRStudio4 but nothings working.
The cable is meant to be on the parallel port right? I'm
using an older IBM laptop.

2. I went out and brought a 12V power brick rated at 300 mA.
I guess that rating means 12V when actually drawing 300. 
With no load it's reading 15V+ and while powering the the
board it's just over 14V. Reason to worry?

Don

dshesnicky wrote:
> 
> My DT006 from Dontronics arrived. I found a straight through
> parallel cable and a 12V power brick. I've hooked everything
> up and the leds are blinking with the test program. I've got
> AVRStudio4 loaded but I don't know how to program the board.
> 
> I want to program in assembler. Questions 1 and 2 follow.
> 
> 1. How do I actually download a program into the DT006 board?
> I've tried some options in AVRStudio4 but nothings working.
> The cable is meant to be on the parallel port right? I'm
> using an older IBM laptop.

The dt006 board can be programmed with bascom-avr, codevision, or
imagecraft compilers.
it means you build your hex file from AVRStudio4, then download it with
say the demo version of bascom-avr

> 2. I went out and brought a 12V power brick rated at 300 mA.
> I guess that rating means 12V when actually drawing 300.
> With no load it's reading 15V+ and while powering the the
> board it's just over 14V. Reason to worry?

No, although I would have got something with a bit more amperage, this
will suit the dt006 
Cheers Don... 

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

Add USB to your Product in 10 min.  http://www.dontronics.com/giga.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.

> > I want to program in assembler. Questions 1 and 2 follow.
> >
> > 1. How do I actually download a program into the DT006 board?
> > I've tried some options in AVRStudio4 but nothings working.
> > The cable is meant to be on the parallel port right? I'm
> > using an older IBM laptop.
>
> The dt006 board can be programmed with bascom-avr, codevision, or
> imagecraft compilers.
> it means you build your hex file from AVRStudio4, then download it with
> say the demo version of bascom-avr

This is exactly what I do - its a little slumsy but it works!!!

Just start up bascom-avr and then go into the "Run Programmer" window. Then
click the "Load file into buffer" button, change the "Files of Type" option
to "Intel Hex" and navigate to your code directory, load your hex file and
click "Auto Program".

The other option is to use the PonyProg2000 program from:
http://www.lancos.com/prog.html. I have used the 2.05a beta version which
works well except that it does not release the RESET line after programming
so you have to unplug the cable to run - which is a bit of a pain. I have
reported this to the author, but it has not been resolved yet. This is a bit
of a shame as the program works real well except for the problem with RESET
and can be scripted from the command line. I had a play with another
parallel port program that allowed me to manually set the port lines etc and
I found that once I toggled the RESET line the DT006 would run fine again so
maybe its worth just making a very small ap to do just this after pongprog
is used.

Don, how about doing a small parallel port board like:
http://www.mcselec.com/an_200.htm that has the tri-statable buffer chip on
it and a 10 way connector that would allow a direct connection to the
programming port on your simmsticks.

Alex

Alex Shepherd wrote:

> The other option is to use the PonyProg2000 program from:
> http://www.lancos.com/prog.html. I have used the 2.05a beta version
> which
> works well except that it does not release the RESET line after
> programming
> so you have to unplug the cable to run - which is a bit of a pain. I
> have
> reported this to the author, but it has not been resolved yet. This is
> a bit
> of a shame as the program works real well except for the problem with
> RESET
> and can be scripted from the command line. I had a play with another
> parallel port program that allowed me to manually set the port lines
> etc and
> I found that once I toggled the RESET line the DT006 would run fine
> again so
> maybe its worth just making a very small ap to do just this after
> pongprog
> is used.

Yes I remember you talking about this in a previous message Alex.
 
> Don, how about doing a small parallel port board like:
> http://www.mcselec.com/an_200.htm that has the tri-statable buffer
> chip on
> it and a 10 way connector that would allow a direct connection to the
> programming port on your simmsticks.
> 
> Alex

what would be the main advantage?

Cheers Don...

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

Add USB to your Product in 10 min.  http://www.dontronics.com/giga.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.