Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is the BX24 main processor) with the BasicX system on it. We will call it the BX35 Then you can have your way with all the pins. I will expand serial out any of the I/O pins and allow access to the other pins of the device like the analog comparitor and the additional interrupt. You will have access to all the ADC's and the BX24's features. The BX35 will be serially downloadable. Of course it will be up to you to get a EEprom and crystal just like the BX1 now. Same parts kit as we have now for the BX1. We are making a new single development system that will support all three chips: The BX1, BX24 and the BX35. The development system wont be ready to sell until at least February (dont hold me to it!), the chip sooner for any one who wants to make their own download cable. Jack -----Original Message----- From: Mike Fellinger <> To: ' <> Date: Saturday, December 11, 1999 10:39 AM Subject: RE: [BasicX] Assembly Language Only Version of BX24 >From: Mike Fellinger <> > >On the subject of wish lists, I'd love to see a "BX28" with sclk, mosi, >miso, and output capture on real pins that can fit a real socket. For new >projects that would be much more >convenient that the existing chip. > >mwf > > -----Original Message----- > From: Jack Schoof [SMTP:] > Sent: Friday, December 10, 1999 10:32 PM > To: > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > From: "Jack Schoof" <> > > We have a physical routing issue. We just cant get there from here. >If you > look at the BX24 it is a marvel in hand routing that 2 layer board. > > You can always add a tiny wire :) > > Jack > > -----Original Message----- > From: Nick Taylor <> > To: <> > Date: Friday, December 10, 1999 10:11 PM > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > >From: Nick Taylor <> > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > >on board for data storage. I'd also like to see the 8535's Int0 > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > >external interrupts would be very nice to have. > > - Nick - > > > > wrote: > >> > >> Seems like it would be easier on you guys to provide the BX24 >without OS > as > >> is -- let users make use of the EE. Since the AL24 volume is >like to be > >> less than the BX24, the cost of a potentially unused EE would >probably be > >> offset by the savings in manufacturing costs. Basically, aren't >all > BX24's > >> AL24's until you put the OS in? > >> > >> -- Jon Williams > > > > > > --------------------------- ONElist Sponsor >---------------------------- > > Buy your holiday gifts at cost this season at eCOST.com - > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a >------------------------------------------------------------------------

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

This sounds cool. I love the BX-24 features but am finding myself making trade offs on what I am physically able to connect to it. Not a short coming in the chip, just too many inputs and outputs to connect to it. Kent M. Gibbs --- Jack Schoof <> wrote: > From: "Jack Schoof" <> > > We will be releasing a version of the Atmel 8535 in a 40 Pin DIP > (which is > the BX24 main processor) with the BasicX system on it. We will call > it the > BX35 Then you can have your way with all the pins. I will expand > serial out > any of the I/O pins and allow access to the other pins of the device > like > the analog comparitor and the additional interrupt. You will have > access to > all the ADC's and the BX24's features. The BX35 will be serially > downloadable. > > Of course it will be up to you to get a EEprom and crystal just like > the BX1 > now. Same parts kit as we have now for the BX1. > > We are making a new single development system that will support all > three > chips: The BX1, BX24 and the BX35. The development system wont be > ready to > sell until at least February (dont hold me to it!), the chip sooner > for any > one who wants to make their own download cable. > > Jack > > -----Original Message----- > From: Mike Fellinger <> > To: ' <> > Date: Saturday, December 11, 1999 10:39 AM > Subject: RE: [BasicX] Assembly Language Only Version of BX24 > >From: Mike Fellinger <> > > > >On the subject of wish lists, I'd love to see a "BX28" with sclk, > mosi, > >miso, and output capture on real pins that can fit a real socket. > For new > >projects that would be much more > >convenient that the existing chip. > > > >mwf > > > > -----Original Message----- > > From: Jack Schoof [SMTP:] > > Sent: Friday, December 10, 1999 10:32 PM > > To: > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > From: "Jack Schoof" <> > > > > We have a physical routing issue. We just cant get there from > here. > >If you > > look at the BX24 it is a marvel in hand routing that 2 layer board. > > > > You can always add a tiny wire :) > > > > Jack > > > > -----Original Message----- > > From: Nick Taylor <> > > To: <> > > Date: Friday, December 10, 1999 10:11 PM > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > > > >From: Nick Taylor <> > > > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > > >on board for data storage. I'd also like to see the 8535's Int0 > > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > > >external interrupts would be very nice to have. > > > - Nick - > > > > > > wrote: > > >> > > >> Seems like it would be easier on you guys to provide the BX24 > >without OS > > as > > >> is -- let users make use of the EE. Since the AL24 volume is > >like to be > > >> less than the BX24, the cost of a potentially unused EE would > >probably be > > >> offset by the savings in manufacturing costs. Basically, aren't > >all > > BX24's > > >> AL24's until you put the OS in? > > >> > > >> -- Jon Williams > > > > > > > > > > --------------------------- ONElist Sponsor > >---------------------------- > > > > Buy your holiday gifts at cost this season at eCOST.com - > > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a> > > > > > >------------------------------------------------------------------------ > > > > > > --------------------------- ONElist Sponsor > ---------------------------- > > Independent contractors: Find your next project gig through JobSwarm! > You can even make $$$ by referring friends. > <a href=" http://clickme.onelist.com/ad/jobswarm2 ">Click Here</a ------------------------------------------------------------------------ __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Jack, The BX35 sounds like what I've been hoping for! I'll want two of them sight unseen! Now if you'll just get that DATA statement going I'll be a happy camper. - Nick - Jack Schoof wrote: > > We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is > the BX24 main processor) with the BasicX system on it. We will call it the > BX35 Then you can have your way with all the pins. I will expand serial out > any of the I/O pins and allow access to the other pins of the device like > the analog comparitor and the additional interrupt. You will have access to > all the ADC's and the BX24's features. The BX35 will be serially > downloadable. > > Of course it will be up to you to get a EEprom and crystal just like the BX1 > now. Same parts kit as we have now for the BX1. > > We are making a new single development system that will support all three > chips: The BX1, BX24 and the BX35. The development system wont be ready to > sell until at least February (dont hold me to it!), the chip sooner for any > one who wants to make their own download cable. > > Jack > > -----Original Message----- > From: Mike Fellinger <> > To: ' <> > Date: Saturday, December 11, 1999 10:39 AM > Subject: RE: [BasicX] Assembly Language Only Version of BX24 > > >From: Mike Fellinger <> > > > >On the subject of wish lists, I'd love to see a "BX28" with sclk, mosi, > >miso, and output capture on real pins that can fit a real socket. For new > >projects that would be much more > >convenient that the existing chip. > > > >mwf > > > > -----Original Message----- > > From: Jack Schoof [SMTP:] > > Sent: Friday, December 10, 1999 10:32 PM > > To: > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > From: "Jack Schoof" <> > > > > We have a physical routing issue. We just cant get there from here. > >If you > > look at the BX24 it is a marvel in hand routing that 2 layer board. > > > > You can always add a tiny wire :) > > > > Jack > > > > -----Original Message----- > > From: Nick Taylor <> > > To: <> > > Date: Friday, December 10, 1999 10:11 PM > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > > > >From: Nick Taylor <> > > > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > > >on board for data storage. I'd also like to see the 8535's Int0 > > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > > >external interrupts would be very nice to have. > > > - Nick - > > > > > > wrote: > > >> > > >> Seems like it would be easier on you guys to provide the BX24 > >without OS > > as > > >> is -- let users make use of the EE. Since the AL24 volume is > >like to be > > >> less than the BX24, the cost of a potentially unused EE would > >probably be > > >> offset by the savings in manufacturing costs. Basically, aren't > >all > > BX24's > > >> AL24's until you put the OS in? > > >> > > >> -- Jon Williams > > > > > > > > > > --------------------------- ONElist Sponsor > >---------------------------- > > > > Buy your holiday gifts at cost this season at eCOST.com - > > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a> > > > > > >------------------------------------------------------------------------ > > > > > > --------------------------------------------------------------- > [Image] > Click Here

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Jack ... I've got my fingers crossed that the BX-35 will be pin compatible with the BX-01. - Nick - Jack Schoof wrote: > > We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is > the BX24 main processor) with the BasicX system on it. We will call it the > BX35 Then you can have your way with all the pins. I will expand serial out > any of the I/O pins and allow access to the other pins of the device like > the analog comparitor and the additional interrupt. You will have access to > all the ADC's and the BX24's features. The BX35 will be serially > downloadable. > > Of course it will be up to you to get a EEprom and crystal just like the BX1 > now. Same parts kit as we have now for the BX1. > > We are making a new single development system that will support all three > chips: The BX1, BX24 and the BX35. The development system wont be ready to > sell until at least February (dont hold me to it!), the chip sooner for any > one who wants to make their own download cable. > > Jack > > -----Original Message----- > From: Mike Fellinger <> > To: ' <> > Date: Saturday, December 11, 1999 10:39 AM > Subject: RE: [BasicX] Assembly Language Only Version of BX24 > > >From: Mike Fellinger <> > > > >On the subject of wish lists, I'd love to see a "BX28" with sclk, mosi, > >miso, and output capture on real pins that can fit a real socket. For new > >projects that would be much more > >convenient that the existing chip. > > > >mwf > > > > -----Original Message----- > > From: Jack Schoof [SMTP:] > > Sent: Friday, December 10, 1999 10:32 PM > > To: > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > From: "Jack Schoof" <> > > > > We have a physical routing issue. We just cant get there from here. > >If you > > look at the BX24 it is a marvel in hand routing that 2 layer board. > > > > You can always add a tiny wire :) > > > > Jack > > > > -----Original Message----- > > From: Nick Taylor <> > > To: <> > > Date: Friday, December 10, 1999 10:11 PM > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > > > >From: Nick Taylor <> > > > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > > >on board for data storage. I'd also like to see the 8535's Int0 > > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > > >external interrupts would be very nice to have. > > > - Nick - > > > > > > wrote: > > >> > > >> Seems like it would be easier on you guys to provide the BX24 > >without OS > > as > > >> is -- let users make use of the EE. Since the AL24 volume is > >like to be > > >> less than the BX24, the cost of a potentially unused EE would > >probably be > > >> offset by the savings in manufacturing costs. Basically, aren't > >all > > BX24's > > >> AL24's until you put the OS in? > > >> > > >> -- Jon Williams > > > > > > > > > > --------------------------- ONElist Sponsor > >---------------------------- > > > > Buy your holiday gifts at cost this season at eCOST.com - > > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a> > > > > > >------------------------------------------------------------------------ > > > > > > --------------------------------------------------------------- > [Image] > Click Here

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Unfortunately in the wisdom of Atmel, they did not make it pin compatible with the BX1 which is why we need another development system. See the Atmel site for the pinout of the 8535. I mainly think it was due to the ADC requiring a quiet Vcc. Jack -----Original Message----- From: Nick Taylor <> To: <> Date: Saturday, December 11, 1999 5:25 PM Subject: Re: [BasicX] Sneak Peek at the BX35 >From: Nick Taylor <> > >Jack ... I've got my fingers crossed that the BX-35 will be pin >compatible with the BX-01. > - Nick - > >Jack Schoof wrote: >> >> We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is >> the BX24 main processor) with the BasicX system on it. We will call it the >> BX35 Then you can have your way with all the pins. I will expand serial out >> any of the I/O pins and allow access to the other pins of the device like >> the analog comparitor and the additional interrupt. You will have access to >> all the ADC's and the BX24's features. The BX35 will be serially >> downloadable. >> >> Of course it will be up to you to get a EEprom and crystal just like the BX1 >> now. Same parts kit as we have now for the BX1. >> >> We are making a new single development system that will support all three >> chips: The BX1, BX24 and the BX35. The development system wont be ready to >> sell until at least February (dont hold me to it!), the chip sooner for any >> one who wants to make their own download cable. >> >> Jack

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Aha ... the light bulb over my head comes on! I was picturing a 40 pin pcb module with a TQFP 8535 on it, similar to the BX-24 ... and I should have been thinking of a DIP 8535 with the Basicx OS on it. In re-reading your original post, that seems to be exactly what you said. - Nick - At 14:00 Jack Schoof wrote: [snip] > Unfortunately in the wisdom of Atmel, they did not make it pin compatible > with the BX1 which is why we need another development system. See the Atmel > site for the pinout of the 8535. > > Jack At 18:34 Jack Schoof wrote: [snip] >> We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is >> the BX24 main processor) with the BasicX system on it. We will call it the >> BX35 Then you can have your way with all the pins. I will expand serial out >> any of the I/O pins and allow access to the other pins of the device like >> the analog comparitor and the additional interrupt. You will have access to >> all the ADC's and the BX24's features. The BX35 will be serially >> downloadable. >> >> Jack

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Jack: I am wondering if the following will be incorporated into the BX25. 1) Will a "DATA" statement be available for both numeric data ( bytes, integer, longs, reals) and for string constsants? 2) Will the serial download make the ATN signal the chip reset so i don't loose a other wise useful pin? (It connects to an interrupt input on the BX24) 3) Will the BX24 commands "CountTransistion", "FreqOut", "PlaySound", "DefineCom3", "Get1Wire", "Put1Wire" be in the BX35? 4) Will a primitive shift command be added to the BX35 firmware and corresponding library calls added. That is the commands could be ShiftLeft(var-name,#bits) and ShiftRight(var- name,#bits). Then add machine code to the chip firmware to implement the shift. 5) Will bit primitve commands be added to the BX35 firmware for individual bit set, clear, and testing? Cheers... Rich > ---------- > From: Jack Schoof[SMTP:] > Reply To: > Sent: Saturday, December 11, 1999 1:00 PM > To: > Subject: [BasicX] Sneak Peek at the BX35 > > From: "Jack Schoof" <> > > We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is > the BX24 main processor) with the BasicX system on it. We will call it the > BX35 Then you can have your way with all the pins. I will expand serial out > any of the I/O pins and allow access to the other pins of the device like > the analog comparitor and the additional interrupt. You will have access to > all the ADC's and the BX24's features. The BX35 will be serially > downloadable. > > Of course it will be up to you to get a EEprom and crystal just like the BX1 > now. Same parts kit as we have now for the BX1. > > We are making a new single development system that will support all three > chips: The BX1, BX24 and the BX35. The development system wont be ready to > sell until at least February (dont hold me to it!), the chip sooner for any > one who wants to make their own download cable. > > Jack > > -----Original Message----- > From: Mike Fellinger <> > To: ' <> > Date: Saturday, December 11, 1999 10:39 AM > Subject: RE: [BasicX] Assembly Language Only Version of BX24 > >From: Mike Fellinger <> > > > >On the subject of wish lists, I'd love to see a "BX28" with sclk, mosi, > >miso, and output capture on real pins that can fit a real socket. For new > >projects that would be much more > >convenient that the existing chip. > > > >mwf > > > > -----Original Message----- > > From: Jack Schoof [SMTP:] > > Sent: Friday, December 10, 1999 10:32 PM > > To: > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > From: "Jack Schoof" <> > > > > We have a physical routing issue. We just cant get there from here. > >If you > > look at the BX24 it is a marvel in hand routing that 2 layer board. > > > > You can always add a tiny wire :) > > > > Jack > > > > -----Original Message----- > > From: Nick Taylor <> > > To: <> > > Date: Friday, December 10, 1999 10:11 PM > > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > > > > > >From: Nick Taylor <> > > > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > > >on board for data storage. I'd also like to see the 8535's Int0 > > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > > >external interrupts would be very nice to have. > > > - Nick - > > > > > > wrote: > > >> > > >> Seems like it would be easier on you guys to provide the BX24 > >without OS > > as > > >> is -- let users make use of the EE. Since the AL24 volume is > >like to be > > >> less than the BX24, the cost of a potentially unused EE would> > >probably be > > >> offset by the savings in manufacturing costs. Basically, aren't > >all > > BX24's > > >> AL24's until you put the OS in? > > >> > > >> -- Jon Williams > > > > > > > > > > --------------------------- ONElist Sponsor > >---------------------------- > > > > Buy your holiday gifts at cost this season at eCOST.com - > > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a> > > > > > >------------------------------------------------------------------------ > > > > > >

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I'd still rather have a single part with all the goodies on it. That makes the BX24 more attractive than the BX01 for my purposes, even with the awkward spi. mwf -----Original Message----- From: Jack Schoof [SMTP:] Sent: Saturday, December 11, 1999 2:01 PM To: Subject: [BasicX] Sneak Peek at the BX35 From: "Jack Schoof" <> We will be releasing a version of the Atmel 8535 in a 40 Pin DIP (which is the BX24 main processor) with the BasicX system on it. We will call it the BX35 Then you can have your way with all the pins. I will expand serial out any of the I/O pins and allow access to the other pins of the device like the analog comparitor and the additional interrupt. You will have access to all the ADC's and the BX24's features. The BX35 will be serially downloadable. Of course it will be up to you to get a EEprom and crystal just like the BX1 now. Same parts kit as we have now for the BX1. We are making a new single development system that will support all three chips: The BX1, BX24 and the BX35. The development system wont be ready to sell until at least February (dont hold me to it!), the chip sooner for any one who wants to make their own download cable. Jack -----Original Message----- From: Mike Fellinger <> To: ' <> Date: Saturday, December 11, 1999 10:39 AM Subject: RE: [BasicX] Assembly Language Only Version of BX24 >From: Mike Fellinger <> > >On the subject of wish lists, I'd love to see a "BX28" with sclk, mosi, >miso, and output capture on real pins that can fit a real socket. For new >projects that would be much more >convenient that the existing chip. > >mwf > > -----Original Message----- > From: Jack Schoof [SMTP:] > Sent: Friday, December 10, 1999 10:32 PM > To: > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > > From: "Jack Schoof" <> > > We have a physical routing issue. We just cant get there from here. >If you > look at the BX24 it is a marvel in hand routing that 2 layer board. > > You can always add a tiny wire :) > > Jack > > -----Original Message----- > From: Nick Taylor <> > To: <> > Date: Friday, December 10, 1999 10:11 PM > Subject: Re: [BasicX] Assembly Language Only Version of BX24 > >From: Nick Taylor <> > > > >Jack ... Jon's idea sounds good to me since I'd like the 25256 > >on board for data storage. I'd also like to see the 8535's Int0 > >brought out to a pin ... maybe pin-27 instead of PD4 ... two > >external interrupts would be very nice to have. > > - Nick - > > > > wrote: > >> > >> Seems like it would be easier on you guys to provide the BX24 >without OS > as > >> is -- let users make use of the EE. Since the AL24 volume is >like to be > >> less than the BX24, the cost of a potentially unused EE would >probably be > >> offset by the savings in manufacturing costs. Basically, aren't >all > BX24's > >> AL24's until you put the OS in? > >> > >> -- Jon Williams > > > > > > --------------------------- ONElist Sponsor >---------------------------- > > Buy your holiday gifts at cost this season at eCOST.com - > <a href=" http://clickme.onelist.com/ad/ecost1 ">Click Here</a >------------------------------------------------------------------------ --------------------------- ONElist Sponsor ---------------------------- Independent contractors: Find your next project gig through JobSwarm! You can even make $$$ by referring friends. <a href=" http://clickme.onelist.com/ad/jobswarm2 ">Click Here</a ------------------------------------------------------------------------

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

-----Original Message----- From: Johnson, Richard A <> To: 'BasicX List Server' <> Date: Monday, December 13, 1999 7:38 AM Subject: RE: [BasicX] Sneak Peek at the BX35 >From: "Johnson, Richard A" <> > >Jack: >I am wondering if the following will be incorporated into the BX25. > >1) Will a "DATA" statement be available for both numeric data ( bytes, integer, longs, reals) > and for string constsants? We are working on this in the compiler for all products. It does not require the chip to know about it. >2) Will the serial download make the ATN signal the chip reset so i don't loose a other wise > useful pin? (It connects to an interrupt input on the BX24) On the BX24 it goes into PortB, Bit 1. We do not believe that the chip reset is the place to go for this purpose. Any wayward modem or com port can reset the Basic Stamp. In our device it cannot. We are going to use the ATN line to communicate with Visual Basic in a PC, for a direct connect between the PC and the BX24 and BX35. Imagine moving a slider in Visual Basic and the corresponding data location changes in the BX24!!! >3) Will the BX24 commands "CountTransistion", "FreqOut", "PlaySound", "DefineCom3", > "Get1Wire", "Put1Wire" be in the BX35? Yes it will be a duplicate of the BX24 as far as system calls go. You will just have more I/O pins. (Of course the pins will be renumbered to match the 40 pin DIP). >4) Will a primitive shift command be added to the BX35 firmware and corresponding library > calls added. That is the commands could be ShiftLeft(var-name,#bits) and ShiftRight(var- > name,#bits). Then add machine code to the chip firmware to implement the shift. As you know shifting can be done with multiply and divide, (or add if it is a shift by one). Function ShiftLeftOne(byval foo as byte) as byte ShiftLeftOne = foo + foo end function Function ShiftLeft(byval foo as byte, byval numbits as byte) as byte dim i as byte for i = 1 to numbits foo = foo + foo next ShiftLeft = foo end function Function ShiftRight(byval foo as byte, byval numbits as byte) as byte dim i as byte for i = 1 to numbits foo = foo \ 2 next ShiftRight = foo end function >5) Will bit primitve commands be added to the BX35 firmware for individual bit set, clear, and > testing? We will be implementing PutBit and GetBit which will allow you to place bits within a 256 bit world. For example: Dim foo(0 to 3) as byte Dim bar as integer ... call PutBit(foo,10,0) 'this would change bit number 2 in foo(1) to a zero call PutBit(bar,15,1) 'this would change bit number 15 in bar = 1 ' equivalent to bar = bar or &H8000 bar = GetBit(foo,10) 'this would get the bit number 2 in foo(1) So to make flags, and be self documenting: Const Test_Flag as byte = 3 Const Another_Flag as byte = 6 Dim Flags as byte ... Call PutBit(Flags,Test_Flag,1) 'turn on test flag ... If GetBit(Flags,Test_Flag) = 1 then ... end if >Cheers... >Rich Hope you like it! Jack <snip

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Thank you for the quick response. It sounds good. However using shifting loops that have division are very slow compared to an assembly primitve. But then you must evaluate if the user community needs faster shifting more than another feature. I understand product development is a trade-off. Also if the serial download is on COM1, which can generate a hardware interrupt, then maybe the ATN pin is not necessary. Invent a protocol that allows interruption of the BasicX at the link level of the protocol. Just an idea. Cheers... Rich > ---------- > From: Jack Schoof[SMTP:] > Reply To: > Sent: Monday, December 13, 1999 9:04 AM > To: > Subject: Re: [BasicX] Sneak Peek at the BX35 > > From: "Jack Schoof" < > -----Original Message----- > From: Johnson, Richard A <> > To: 'BasicX List Server' <> > Date: Monday, December 13, 1999 7:38 AM > Subject: RE: [BasicX] Sneak Peek at the BX35 > >From: "Johnson, Richard A" <> > > > >Jack: > >I am wondering if the following will be incorporated into the BX25. > > > >1) Will a "DATA" statement be available for both numeric data ( bytes, > integer, longs, reals) > > and for string constsants? > > We are working on this in the compiler for all products. It does not > require the chip to know about it. > > >2) Will the serial download make the ATN signal the chip reset so i don't > loose a other wise > > useful pin? (It connects to an interrupt input on the BX24) > > On the BX24 it goes into PortB, Bit 1. We do not believe that the chip > reset is the place to go for this purpose. Any wayward modem or com port > can reset the Basic Stamp. In our device it cannot. We are going to use > the ATN line to communicate with Visual Basic in a PC, for a direct connect > between the PC and the BX24 and BX35. Imagine moving a slider in Visual > Basic and the corresponding data location changes in the BX24!!! > > >3) Will the BX24 commands "CountTransistion", "FreqOut", "PlaySound", > "DefineCom3", > > "Get1Wire", "Put1Wire" be in the BX35? > > Yes it will be a duplicate of the BX24 as far as system calls go. You will > just have more I/O pins. (Of course the pins will be renumbered to match > the 40 pin DIP). > > >4) Will a primitive shift command be added to the BX35 firmware and > corresponding library > > calls added. That is the commands could be ShiftLeft(var-name,#bits) > and ShiftRight(var- > > name,#bits). Then add machine code to the chip firmware to implement > the shift. > > As you know shifting can be done with multiply and divide, (or add if it is > a shift by one). > > Function ShiftLeftOne(byval foo as byte) as byte > ShiftLeftOne = foo + foo > end function > > Function ShiftLeft(byval foo as byte, byval numbits as byte) as byte > dim i as byte > for i = 1 to numbits > foo = foo + foo > next > ShiftLeft = foo > end function > > Function ShiftRight(byval foo as byte, byval numbits as byte) as byte > dim i as byte > for i = 1 to numbits > foo = foo \ 2 > next > ShiftRight = foo > end function > >5) Will bit primitve commands be added to the BX35 firmware for individual > bit set, clear, and > > testing? > > We will be implementing PutBit and GetBit which will allow you to place bits > within a 256 bit world. For example: > > Dim foo(0 to 3) as byte > Dim bar as integer > ... > call PutBit(foo,10,0) 'this would change bit number 2 in foo(1) to a zero > call PutBit(bar,15,1) 'this would change bit number 15 in bar = 1 > ' equivalent to bar = bar or &H8000 > bar = GetBit(foo,10) 'this would get the bit number 2 in foo(1) > > So to make flags, and be self documenting: > > Const Test_Flag as byte = 3 > Const Another_Flag as byte = 6 > > Dim Flags as byte > > ... > Call PutBit(Flags,Test_Flag,1) 'turn on test flag> > ... > If GetBit(Flags,Test_Flag) = 1 then > ... > end if > > > > >Cheers... > >Rich > Hope you like it! > > Jack > > <snip> > >

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I would like to see an option on the chip page of the compiler to automatically set the BX-???'s RTC to the computers system time and date on download. The downloader could query the computer and load those values into the RTC registers on the BX-???. This option could be saved along with the project options just like the pin definitions. --- Jack Schoof <> wrote: > From: "Jack Schoof" < > -----Original Message----- > From: Johnson, Richard A <> > To: 'BasicX List Server' <> > Date: Monday, December 13, 1999 7:38 AM > Subject: RE: [BasicX] Sneak Peek at the BX35 > >From: "Johnson, Richard A" <> > > > >Jack: > >I am wondering if the following will be incorporated into the BX25. > > > >1) Will a "DATA" statement be available for both numeric data ( > bytes, > integer, longs, reals) > > and for string constsants? > > We are working on this in the compiler for all products. It does not > require the chip to know about it. > > >2) Will the serial download make the ATN signal the chip reset so i > don't > loose a other wise > > useful pin? (It connects to an interrupt input on the BX24) > > On the BX24 it goes into PortB, Bit 1. We do not believe that the > chip > reset is the place to go for this purpose. Any wayward modem or com > port > can reset the Basic Stamp. In our device it cannot. We are going to > use > the ATN line to communicate with Visual Basic in a PC, for a direct > connect > between the PC and the BX24 and BX35. Imagine moving a slider in > Visual > Basic and the corresponding data location changes in the BX24!!! > > >3) Will the BX24 commands "CountTransistion", "FreqOut", > "PlaySound", > "DefineCom3", > > "Get1Wire", "Put1Wire" be in the BX35? > > Yes it will be a duplicate of the BX24 as far as system calls go. > You will > just have more I/O pins. (Of course the pins will be renumbered to > match > the 40 pin DIP). > > >4) Will a primitive shift command be added to the BX35 firmware and > corresponding library > > calls added. That is the commands could be > ShiftLeft(var-name,#bits) > and ShiftRight(var- > > name,#bits). Then add machine code to the chip firmware to > implement > the shift. > > As you know shifting can be done with multiply and divide, (or add if > it is > a shift by one). > > Function ShiftLeftOne(byval foo as byte) as byte > ShiftLeftOne = foo + foo > end function > > Function ShiftLeft(byval foo as byte, byval numbits as byte) as byte > dim i as byte > for i = 1 to numbits > foo = foo + foo > next > ShiftLeft = foo > end function > > Function ShiftRight(byval foo as byte, byval numbits as byte) as byte > dim i as byte > for i = 1 to numbits > foo = foo \ 2 > next > ShiftRight = foo > end function > >5) Will bit primitve commands be added to the BX35 firmware for > individual > bit set, clear, and > > testing? > > We will be implementing PutBit and GetBit which will allow you to > place bits > within a 256 bit world. For example: > > Dim foo(0 to 3) as byte > Dim bar as integer > ... > call PutBit(foo,10,0) 'this would change bit number 2 in foo(1) to a > zero > call PutBit(bar,15,1) 'this would change bit number 15 in bar = 1 > ' equivalent to bar = bar or &H8000 > bar = GetBit(foo,10) 'this would get the bit number 2 in foo(1) > > So to make flags, and be self documenting: > > Const Test_Flag as byte = 3 > Const Another_Flag as byte = 6 > > Dim Flags as byte > > ... > Call PutBit(Flags,Test_Flag,1) 'turn on test flag > ... > If GetBit(Flags,Test_Flag) = 1 then > ... > end if > > > > >Cheers... > >Rich > Hope you like it! > > Jack > > <snip> > > --------------------------- ONElist Sponsor > ---------------------------- > > Hey Freelancers: Find your next project through JobSwarm! > You can even make $$$ in your sleep by referring friends. > <a href=" http://clickme.onelist.com/ad/jobswarm1 ">Click Here</a ------------------------------------------------------------------------ __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I cant guarantee that I wont mess up your COM1 code. Modems use a pause followed by a +++, but I want faster access than that. The ATN line lets me connect in a few milliseconds. Jack -----Original Message----- From: Johnson, Richard A <> To: 'BasicX List Server' <> Date: Monday, December 13, 1999 10:40 AM Subject: RE: [BasicX] Sneak Peek at the BX35 >From: "Johnson, Richard A" <> > >Thank you for the quick response. >It sounds good. >However using shifting loops that have division are very slow compared to an assembly primitve. But then you must evaluate if the user community needs faster shifting more than another feature. I understand product development is a trade-off. > >Also if the serial download is on COM1, which can generate a hardware interrupt, then maybe the ATN pin is not necessary. Invent a protocol that allows interruption of the BasicX at the link level of the protocol. Just an idea. > >Cheers... >Rich > >> ---------- >> From: Jack Schoof[SMTP:] >> Reply To: >> Sent: Monday, December 13, 1999 9:04 AM >> To: >> Subject: Re: [BasicX] Sneak Peek at the BX35 >> >> From: "Jack Schoof" <> >> >> >> -----Original Message----- >> From: Johnson, Richard A <> >> To: 'BasicX List Server' <> >> Date: Monday, December 13, 1999 7:38 AM >> Subject: RE: [BasicX] Sneak Peek at the BX35 >> >> >> >From: "Johnson, Richard A" <> >> > >> >Jack: >> >I am wondering if the following will be incorporated into the BX25. >> > >> >1) Will a "DATA" statement be available for both numeric data ( bytes, >> integer, longs, reals) >> > and for string constsants? >> >> We are working on this in the compiler for all products. It does not >> require the chip to know about it. >> >> >2) Will the serial download make the ATN signal the chip reset so i don't >> loose a other wise >> > useful pin? (It connects to an interrupt input on the BX24) >> >> On the BX24 it goes into PortB, Bit 1. We do not believe that the chip >> reset is the place to go for this purpose. Any wayward modem or com port >> can reset the Basic Stamp. In our device it cannot. We are going to use >> the ATN line to communicate with Visual Basic in a PC, for a direct connect >> between the PC and the BX24 and BX35. Imagine moving a slider in Visual >> Basic and the corresponding data location changes in the BX24!!! >> >> >3) Will the BX24 commands "CountTransistion", "FreqOut", "PlaySound", >> "DefineCom3", >> > "Get1Wire", "Put1Wire" be in the BX35? >> >> Yes it will be a duplicate of the BX24 as far as system calls go. You will >> just have more I/O pins. (Of course the pins will be renumbered to match >> the 40 pin DIP). >> >> >4) Will a primitive shift command be added to the BX35 firmware and >> corresponding library >> > calls added. That is the commands could be ShiftLeft(var-name,#bits) >> and ShiftRight(var- >> > name,#bits). Then add machine code to the chip firmware to implement >> the shift. >> >> As you know shifting can be done with multiply and divide, (or add if it is >> a shift by one). >> >> Function ShiftLeftOne(byval foo as byte) as byte >> ShiftLeftOne = foo + foo >> end function >> >> Function ShiftLeft(byval foo as byte, byval numbits as byte) as byte >> dim i as byte >> for i = 1 to numbits >> foo = foo + foo >> next >> ShiftLeft = foo >> end function >> >> Function ShiftRight(byval foo as byte, byval numbits as byte) as byte >> dim i as byte >> for i = 1 to numbits >> foo = foo \ 2 >> next >> ShiftRight = foo >> end function >> >> >> >5) Will bit primitve commands be added to the BX35 firmware for individual >> bit set, clear, and >> > testing? >> >> We will be implementing PutBit and GetBit which will allow you to place bits >> within a 256 bit world. For example: >> >> Dim foo(0 to 3) as byte >> Dim bar as integer >> ... >> call PutBit(foo,10,0) 'this would change bit number 2 in foo(1) to a zero >> call PutBit(bar,15,1) 'this would change bit number 15 in bar = 1 >> ' equivalent to bar = bar or &H8000 >> bar = GetBit(foo,10) 'this would get the bit number 2 in foo(1) >> >> So to make flags, and be self documenting: >> >> Const Test_Flag as byte = 3 >> Const Another_Flag as byte = 6 >> >> Dim Flags as byte >> >> ... >> Call PutBit(Flags,Test_Flag,1) 'turn on test flag> >> ... >> If GetBit(Flags,Test_Flag) = 1 then >> ... >> end if >> >> > >> >Cheers... >> >Rich >> >> >> Hope you like it! >> >> Jack >> >> <snip> >> >>

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )