FemtoBasic for Hitt Consulting's PropDongle and other minimal Prop boards
Mike Green
Posts: 23,101
I've put together a version of FemtoBasic uploaded to the Object Exchange that's stripped down for Propeller boards without special I/O and uses the programming serial port for "console" I/O. It does keep the SD card support (on I/O pins 8-11). This is specifically intended for use with Hitt Consulting's PropDongle, but would work well with any minimal Propeller board like the
PropStick, PropStickUSB, or the SpinStamp. As will all FemtoBasic derivatives, there's direct access to the I/O pins, the counters, and any EEPROM attached to pins 28/29.
PropStick, PropStickUSB, or the SpinStamp. As will all FemtoBasic derivatives, there's direct access to the I/O pins, the counters, and any EEPROM attached to pins 28/29.
Comments
Nico Hattink
@Mike: Would you mind my posting Femtobasic_PropTerminal to the object exchange?
It appears to do the same thing yours does except it was geared toward Propterm,
and I couldn't resist adding a couple commands to play with the graphics and color
in that driver.
We may need an entire section on OBEX just to host all the flavors of Femto. <GRIN>
Oldbitcollector
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Buttons . . . check. Dials . . . check. Switches . . . check. Little colored lights . . . check.
— Calvin, of 'Calvin and Hobbes.
There were some bugs fixed in the last update to FemtoBasic. I think the "autorun" feature was added then as well.
I've used HyperTerminal under Windows and both ZTerm and MacWise under the Mac OS as terminal programs for the serial Basics. I think you could use the Stamp Editor's debug window. Certainly you could use PropTerminal. Anything that talks 9600 Baud 8-bit asynchronous serial without handshaking should work.
Oldbitcollector,
I don't have any objections to people posting variations / improvements / extensions to programs I've posted. There are some responsibility issues that people will have to address for themselves:
1) Is there enough functional difference between what's already there and what the person wants to post to warrant adding to the clutter? Clearly, one person's major functional improvement is another person's clutter. That's why it's a responsibility issue.
2) FemtoBasic is pretty stable at this point. The BoeBotBasic derivatives are a little different and borrow some of their I/O drivers and memory organization from the Propeller OS. A couple of bugs were introduced which have now been fixed and there will be a new BoeBotBasic version uploaded shortly. Are you (or anyone else considering posting a FemtoBasic derivative) willing to take responsibility for monitoring for updates to the original and updating their derivative program?