Hey, buzzard, are you cloth-eared? Come on, look at hotchas here http://u.to/ZOg3Dw
Tiny Lisp Computer
21–27 of 27 posts
Re: Tiny Lisp Computer
#22Another option for running a lisp (like language) on a small package is esp-lisp [1] running on ESP8622. The ESP8622 has a 32 bit processor running quite fast, and comes with 64K of RAM, so it's clearly not as challenging a platform to run lisp on as the Atmega used here. Its just a software project, though, and leaves the hardware part for others to design.
Re: Tiny Lisp Computer
#23Earlier quoted context omitted.
If you build a compiler without runtime eval, you can use all the AVR's memory for user data. Still tiny, but not as cramped as this interpreter: http://microscheme.org Then again, if it doesn't have runtime eval, is it really a lisp?
Good question. It's hard to say. As for microscheme, it looks cool. Although I am annoyed, because it implicitly claims to be Scheme (it's not), and it explicitly claims to be functional (scheme most definitely isn't). But those are just nitpicks.
Nope; it's absolutely clear right on the front page that it's a subset of Scheme.
Re: Tiny Lisp Computer
#24Huh. I thought about doing this, figured it would be impossible / pointless, and that (apparently wrong) assumption led me on a year-long journey: The core problem, I thought, would be that AVRs have very very little memory. 316 Lisp cells sounds about right. I figured, well that's pointless. How can I do better? I wasn't able to find a microcontroller that you can attach external memory to (without cheating and usin…
Some of the devices in the Mega AVR line support external memory. The ATmega640 is an example. Generally you'll only find it on higher pin-count devices which aren't available in DIP packages. If you need something that's a bit easier to work with, the Teensy 2.0++ is an option. As for your Z80 computer, another option would be to add some simple bank-switching hardware to allow you to boot from ROM. Probably more wo…
I'm fine working with surface-mount stuff, I can solder it by hand, it's not actually as hard as it looks. Bank switching seems like a pain to manage though.
I wish I had learned this stuff in school. I majored in CS, and we didn't go any lower level than C++.
Re: Tiny Lisp Computer
#25Earlier quoted context omitted.
Good question. It's hard to say. As for microscheme, it looks cool. Although I am annoyed, because it implicitly claims to be Scheme (it's not), and it explicitly claims to be functional (scheme most definitely isn't). But those are just nitpicks.
Nope; it's absolutely clear right on the front page that it's a subset of Scheme.
What I meant was the name, although it's up for debate. The micro- would imply a subset, so it's much better than the many languages that call themselves Scheme, and really, really aren't.
Re: Tiny Lisp Computer
#26uLisp is cool (code is a bit scary in places though), I'm working on a virtual game console which uses an AVR. I added some simple drawing functions. http://fingswotidun.com/cruft/lisptri.gif The emulator is at http://fingswotidun.com/avr/ but it's very alpha. If you have a small screen you can't even click on the run button because of an old debugging div is sitting on top of it.
I would like to read a blog post about your virtual game console if you have or ever write one.
I have one from the very early days.
http://blag.fingswotidun.com/2015/09/8-bit-machine.html
I've been planning on an update talking about Getting C programs running on it then building avr BASIC and Lisp for run time languages.
Probably far more likely to do updates given someone has actually shown interest in reading them. I kind of assumed My blog posts went into a void.
It's also on github https://github.com/Lerc/kwak-8
Re: Tiny Lisp Computer
#27The article links to http://www.technoblogy.com/list?1GLV calling it the full code listing for this Tiny Lisp Computer, however, that link leads to code for a ATtiny841 "I2C Display Module" which is from the "Make your own I2C peripherals" blog post at http://www.technoblogy.com/show?1G29 . Hope the author sees this so he can change the link to be the correct one.
I notified the author about it on the uLisp forums. He has now updated the link.