BasicX V2.1 IDE Released

Started by Frank Manning August 19, 2003
The new BasicX V2.1 IDE has been released and is available here:

http://www.basicx.com/transfer/bx_updates.htm

Summary of changes:

http://www.basicx.com/downloads/Rev_History.txt

I'd like to thank everybody for their critiques and comments.

From: twesthoff <>
Sent: Friday, November 01, 2002 5:55 AM

> That BX emulation program would be nice to have. Will it be
> available to the rest of us sometime?

Ask and you shall receive.

With V2.1 you can create a VB6 project from an existing BasicX
project, and you can run a BasicX emulator on a PC. A bit over
half of the BasicX system library is either emulated or inherently
built into VB.

From: Dave Houston <>
Sent: Monday, June 03, 2002 2:42 PM

> How about...
>
> 1. Adding a timeout parameter to GetQueue
>
> 2. A way to exit InputCapture when a pulse (or space)
> width exceeds a limit value. This would allow it to be
> used for pulse trains of arbitrary length.

The new system library includes GetQueue with optional timeout
parameters.

We've also included an application note that explains how to
impose a timeout limit on InputCapture.

From: John Piccirillo <>
Sent: Tuesday, November 19, 2002 10:03 PM

> 1. Can the jumping jack flash "feature" be eliminated
> please? I refer to the code in the editor window
> jumping up or down a screen when the cursor is
> repositioned in the code.

OK, this has been fixed.

From: Tom Igoe <>
Sent: Sunday, June 08, 2003 8:02 AM

> No doubt HTML is much better for online docs (which is why
> all my class docs are in html), but the fact is, quite
> often I prefer PDF's because I am offline.

Most of the documentation is now in PDF instead of Word format.

-- Frank Manning
-- NetMedia, Inc.



Frank,

How about changing the documentation to the CHM format so
that it will simply work with Windows help?

I have yet to play with the emulator but it seems like a nice tool
to have.

Dan Thompson ----- Original Message -----
From: "Frank Manning" <>
To: <>
Sent: Tuesday, August 19, 2003 2:14 PM
Subject: [BasicX] BasicX V2.1 IDE Released > The new BasicX V2.1 IDE has been released and is available here:
>
> http://www.basicx.com/transfer/bx_updates.htm
>
> Summary of changes:
>
> http://www.basicx.com/downloads/Rev_History.txt
>
> I'd like to thank everybody for their critiques and comments.
>
> From: twesthoff <>
> Sent: Friday, November 01, 2002 5:55 AM
>
> > That BX emulation program would be nice to have. Will it be
> > available to the rest of us sometime?
>
> Ask and you shall receive.
>
> With V2.1 you can create a VB6 project from an existing BasicX
> project, and you can run a BasicX emulator on a PC. A bit over
> half of the BasicX system library is either emulated or inherently
> built into VB.
>
> From: Dave Houston <>
> Sent: Monday, June 03, 2002 2:42 PM
>
> > How about...
> >
> > 1. Adding a timeout parameter to GetQueue
> >
> > 2. A way to exit InputCapture when a pulse (or space)
> > width exceeds a limit value. This would allow it to be
> > used for pulse trains of arbitrary length.
>
> The new system library includes GetQueue with optional timeout
> parameters.
>
> We've also included an application note that explains how to
> impose a timeout limit on InputCapture.
>
> From: John Piccirillo <>
> Sent: Tuesday, November 19, 2002 10:03 PM
>
> > 1. Can the jumping jack flash "feature" be eliminated
> > please? I refer to the code in the editor window
> > jumping up or down a screen when the cursor is
> > repositioned in the code.
>
> OK, this has been fixed.
>
> From: Tom Igoe <>
> Sent: Sunday, June 08, 2003 8:02 AM
>
> > No doubt HTML is much better for online docs (which is why
> > all my class docs are in html), but the fact is, quite
> > often I prefer PDF's because I am offline.
>
> Most of the documentation is now in PDF instead of Word format.
>
> -- Frank Manning
> -- NetMedia, Inc. > ">http://docs.yahoo.com/info/terms/




Does the support for 64KB EEPROMs mean you will be offering a BX-24
with a larger EEPROM? If I replace the 32KB EEPROM on a BX-24, can I
create larger programs?

On 19 Aug 2003 at 11:14, Frank Manning wrote:

> Summary of changes:
>
> http://www.basicx.com/downloads/Rev_History.txt
---
http://www.laser.com/dhouston/


From: Dave Houston <>

> Does the support for 64KB EEPROMs mean you will be
> offering a BX-24 with a larger EEPROM?

We're considering doing that in the future.

> If I replace the 32KB EEPROM on a BX-24, can I
> create larger programs?

Yes. You should be able to replace the 32 KB EEPROM with a 64 KB
Atmel AT25HP512 or compatible chip.

-- Frank Manning
-- NetMedia, Inc.



On 19 Aug 2003 at 12:38, Frank Manning wrote:

> From: Dave Houston <>
>
> > Does the support for 64KB EEPROMs mean you will be
> > offering a BX-24 with a larger EEPROM?
>
> We're considering doing that in the future.

How soon? I'm old and in ill health so my future ain't what it used
to be. ;)

I have a few hundred users of an application that now uses 26,908
bytes of EEPROM for the program. I use the area from 27,000 up for
user data. If I can increase program space and still use any area
above the program for user data, I can add more features. The 92
bytes free now doesn't allow much leeway.

Can we write our own routines to put user data into EEPROM above 32K?

> > If I replace the 32KB EEPROM on a BX-24, can I
> > create larger programs?
>
> Yes. You should be able to replace the 32 KB EEPROM with a 64 KB
> Atmel AT25HP512 or compatible chip.

I doubt that many end users will want to risk ruining a $50 module
but I might consider doing it if I can make use of the area above 32K
for user data.

If not, I suppose I can add a daughterboard with the 25256 that I
desolder and put user data there.
---
http://www.laser.com/dhouston/


From: Dave Houston <>

> On 19 Aug 2003 at 12:38, Frank Manning wrote:
>
> > From: Dave Houston <>
> >
> > > Does the support for 64KB EEPROMs mean you will be
> > > offering a BX-24 with a larger EEPROM?
> >
> > We're considering doing that in the future.
>
> How soon? I'm old and in ill health so my future
> ain't what it used to be. ;)
>
> I have a few hundred users of an application that
> now uses 26,908 bytes of EEPROM for the program. I
> use the area from 27,000 up for user data. If I can
> increase program space and still use any area above
> the program for user data, I can add more features.
> The 92 bytes free now doesn't allow much leeway.
>
> Can we write our own routines to put user data into
> EEPROM above 32K? [...]

Yes, as long as you don't use PutEEPROM. Probably a block data
class is the easiest way to load read-only user data into the 64
KB chip.

If you also need read/write access, you'd need an alternative,
such as a second EEPROM attached to the SPI bus, but at least you
can write programs larger than 32 KB.

We don't have a specific date yet for supplying 64 KB BX-24 chips.
Probably the easiest upgrades would be for BX-01 or BX-35 users
with PDIP EEPROM chips in sockets.

-- Frank Manning
-- NetMedia, Inc.



On 19 Aug 2003 at 14:01, Frank Manning wrote:

> If you also need read/write access, you'd need an alternative,
> such as a second EEPROM attached to the SPI bus, but at least you can
> write programs larger than 32 KB.

I need read/write so I guess I'll have a use for the 25256 that I'll
have to remove.

> We don't have a specific date yet for supplying 64 KB BX-24 chips.
> Probably the easiest upgrades would be for BX-01 or BX-35 users with
> PDIP EEPROM chips in sockets.

I've already decided that going straight to Atmel mega chips is
better for me than using the BX-35 so that's not an attractive
alternative.

If I can add 32K of program space and then use the surplus 25256 for
user data, it gives my current users an upgrade path.---
http://www.laser.com/dhouston/


Just a minor note, on the revision history it mentions "V2.01" at the top,
shouldn't it be "V2.10"?

Regards, and many thanks!

Mike ----- Original Message -----
From: "Frank Manning" <>
To: <>
Sent: Tuesday, August 19, 2003 8:14 PM
Subject: [BasicX] BasicX V2.1 IDE Released > The new BasicX V2.1 IDE has been released and is available here:
>
> http://www.basicx.com/transfer/bx_updates.htm
>
> Summary of changes:
>
> http://www.basicx.com/downloads/Rev_History.txt
>
> I'd like to thank everybody for their critiques and comments.
>
> From: twesthoff <>
> Sent: Friday, November 01, 2002 5:55 AM
>
> > That BX emulation program would be nice to have. Will it be
> > available to the rest of us sometime?
>
> Ask and you shall receive.
>
> With V2.1 you can create a VB6 project from an existing BasicX
> project, and you can run a BasicX emulator on a PC. A bit over
> half of the BasicX system library is either emulated or inherently
> built into VB.
>
> From: Dave Houston <>
> Sent: Monday, June 03, 2002 2:42 PM
>
> > How about...
> >
> > 1. Adding a timeout parameter to GetQueue
> >
> > 2. A way to exit InputCapture when a pulse (or space)
> > width exceeds a limit value. This would allow it to be
> > used for pulse trains of arbitrary length.
>
> The new system library includes GetQueue with optional timeout
> parameters.
>
> We've also included an application note that explains how to
> impose a timeout limit on InputCapture.
>
> From: John Piccirillo <>
> Sent: Tuesday, November 19, 2002 10:03 PM
>
> > 1. Can the jumping jack flash "feature" be eliminated
> > please? I refer to the code in the editor window
> > jumping up or down a screen when the cursor is
> > repositioned in the code.
>
> OK, this has been fixed.
>
> From: Tom Igoe <>
> Sent: Sunday, June 08, 2003 8:02 AM
>
> > No doubt HTML is much better for online docs (which is why
> > all my class docs are in html), but the fact is, quite
> > often I prefer PDF's because I am offline.
>
> Most of the documentation is now in PDF instead of Word format.
>
> -- Frank Manning
> -- NetMedia, Inc. > ">http://docs.yahoo.com/info/terms/




As I think we've mentioned before, V2.1 adds support for 64 KB
EEPROM, which doubles the space available for programs. But
procedure PutEEPROM is not supported for the larger chips (Atmel
AT25HP512).

In case anybody's curious, the reason for the limitation is that
PutEEPROM writes a single byte at a time, but the 64 KB chip
restricts you to a 128 byte minimum.

In other words, to write any data at all to the chip, you need to
write at least a 128 byte page. Unlike the current 32 KB chip, the
larger chip does not have a 1 byte write mode.

By contrast, both chips allow you to read 1 byte at a time, which
means GetEEPROM works for both chips.

-- Frank Manning
-- NetMedia, Inc.



Frank

Can you clarify the 64KB EEPROM support in V2.1 a bit more?

If I change the EEPROM on my Bx24 to to a 64KB (AT25HP512) device.
Then I recompile a program that I know will take more space than the
current 32KB limit will the code 'grow' into that 64KB space?

Or is the program limit still 32KB and the 'upper' 32KB memory space only
useable by GetEEPROM ?

thanks Frank Manning <> wrote:
As I think we've mentioned before, V2.1 adds support for 64 KB
EEPROM, which doubles the space available for programs. But
procedure PutEEPROM is not supported for the larger chips (Atmel
AT25HP512).

In case anybody's curious, the reason for the limitation is that
PutEEPROM writes a single byte at a time, but the 64 KB chip
restricts you to a 128 byte minimum.

In other words, to write any data at all to the chip, you need to
write at least a 128 byte page. Unlike the current 32 KB chip, the
larger chip does not have a 1 byte write mode.

By contrast, both chips allow you to read 1 byte at a time, which
means GetEEPROM works for both chips.

-- Frank Manning
-- NetMedia, Inc. ">http://docs.yahoo.com/info/terms/
---------------------------------