jedimatt42

Does a recipe for that exist? Or is that still to be designed? [email protected]

Nice! Thanks, I'm back in business [email protected]

In other news, I just got a couple usb host shields from DuinoFun.com that appear to be nearly identical to the [email protected] device I have used in my prototype. It is slightly modified, in that it doesn't have the solder pads there are traces you might cut for certain applications. But it is still clear where to cut to isolate the VBUS 5v supply to the USB device. Supply chain on this piece is much better. About 1 week for delivery, instead of 30days for the other. And I've got a couple Teensy 3.2 boards, which is for my purposes completely pin/software compatible with the Teensy 3.1 I used. So I believe supply of these breakout boards I'm using will be healthy. Just something I was worried about.

I've looked at OSHpark a bit. It looked promising. It's a bit of a leap to take But sometimes I think the instability I experience is the wiggly wires in the breadboard. Keyboardio looks very related to some 'build your own keyboard' link that was posted earlier. I still can't believe someone wants to hit the modifiers with their thumbs... But it is cool. I believe in personalized computers. I'm a lefty in a righty world, so I respect the totally custom layout. But I actually enjoy a variety of keyboards, from my Logitech K750, which I'm surprised I like, to my Happy Hacking Keyboard Lite. I use too many different computers between work and home, that I need to customize them back to what my fingers know. I haven't seen anything in the USB keyboard 'boot' protocol that inherently limits the number of simultaneous keys, but it is those missing diodes, and how the matrix is wired up to the microcontroller in the keyboard that encodes it out to USB that is the problem. The makers have to balance consumer desire for cheap against the desire for quality. I'm pretty sure I don't know what I'm doing with them, which is why I'm hoping to find something that can change me. I'd like to understand there role, and how to determine the correct size for an application. I don't really think the F18A did anything but mix up the power demands a little. It appeared as though the USB host control chip was continuously resetting, very rapidly. Normally, the guy who makes the USB Host shield, cheats on the 5v power to the usb device, and puts a capacitor (200uf) across the 3.3v/gnd supply from the teensy to the USB Host shield. But that was said to be to protect the shield causing undervoltage on the teensy and resetting it when the USB device is powered on. This is a 3.3v cheat that works with some usb devices. But I'm not powering the USB device off the 3.3v. I cut the connection between the VBUS and the 3.3v, and supply the 5v to VBUS like it is supposed to be for the USB standard. In the beginning, I had just the teensy and usb host shield. 5v wired to VBUS, 5v wired to teensy VCC, and the teensy's 3.3v out supplying the usb host shield's 3.3v in requirement. This worked fine for a cheap little wired USB keyboard. But then I ordered a wireless to test. And there was no joy. I read more, and experimented. The USB standard expects a host port to provide a certain amount of capacitance, but most host ports provide grossly more than the spec calls for. I think the spec wanted 150uf as a minimum. I worked my up to a 330uf capacitor at VBUS on the 5v line, and then the wireless unifying receiver from Logitech worked. This has been pretty stable for a while now, except I seem to have to wiggle the wiggly breadboard wires.. Ok, so enter the F18A. Like I said, I don't think it is anything bad with the F18A, it is just exposing that I get pretty far without hard knowledge So, in the 3.3v USB power cheat it was common to have a capacitor between the USB Host and the 3.3v supply from the teensy. So I put a 100uf cap there. That didn't seem to work.. I left it there, and then put another 100uf cap on the 5v line to the teensy, this happens to be in parallel with the supply to VBUS ( so there is also a 330uf cap downstream )... This works better, but when cold, still seems to need a few restarts to get it working. Then after it has been live for a while, I can take those two 100uf caps out, and power down, pause for a bit, and power back on and it all seems to work. So, I've got to learn something to figure out how to make this stable. I figured the 100uf wouldn't hurt as a greater value was not unheard of. Although I feel like the 330uf on the VBUS should be providing the undercurrent protection when the USB device powers up, so the 100uf shouldn't be necessary, or should be something smaller. And the last one I put in feels like it is just a stab in the dark. I'm searching the internet wrong, cause I'm not finding anything that describes how to choose to influence my circuit. I am assuming my application is about smoothing out the voltage. I just realized I haven't tried youtube... Anyway, if anyone has the correct words to google, or any detail that I'm headed in the completely wrong direction, that input is welcome. I think the tech industry is just trying to eliminate them with touch screens. I joke... I hope. [email protected]

So, a fresh batch of F18As went out recently. I managed to grab 2. I've upgraded my working console with one, and then this next weekend, I'm hoping the second will just fix what looks like bad VDP ram in my second console. The first thing that struck me, is that now all the emulators look more like real iron But my favorite new software feature is 80 column editor in fbForth. My next favorite new thing is how it makes this old TI look like college era Sega when you run the ALEX KIDD cartridge demo. What is your favorite app/feature/aspect that changes regular real iron usage of your TI?

I've noticed as you said, unexpected behavior when doing a lot of editing. Backspace is so naturally quick, but I have typing habits on a PC, such as pressing the next key before really releasing the backspace. And since the backspace maps to a modifier (fctn) and s, it acts like I'm holding down fctn,s, and the next key... It was also pretty stable, power wise, but then after I put in the F18A, it wouldn't work. I solved that with some capacitors. But I don't really know what I'm doing with capacitors. Does anyone know a good technique to figure out how much is needed and where? Or a dummies intro to this? Thanks, [email protected]

I took a stab at enabling hardware flow control and had no luck. More research needed. It looks like hardware flow control is sharing a pin with a boot mode control. I may need a switch to only connect that after power on. Or more... Wiring it the way I had also screws with the ftdi programming cable. So you don't want to lock it in with the serial port attached. But you can put the tx rx on the ftdi header instead. But it worked really well at 2400, so still cool. I'll keep at it. [email protected]

That's cool, then I'd leave the title be, since it is a lineage, and not a fork. [email protected]

Is this same binary going to be compatible with both the Geneve and the F18A? If not, it would be cool to be branded for the F18A, maybe where the screen shot currently says 9640 Or maybe you've covered that already... [email protected]

Looking forward to it! I just got my F18A about a week ago, installed it in my working TI same day. Loading Boot in the XB2.7 cart is awesome. This will be 2xAwesome! Can you access the built in cart programs from the menu? I tried in Boot using DSR style "DM2K." to do things like jump to DM2K, but that didn't work directly, so instead I throw a little helper xb program on the disk that Boot runs in XB and it then bounces back into the cart program I want. Is there, or will there be a more streamlined way to do that? It'll be 2xAwesome no matter what! And for the math detail oriented, I know, it will literally be 2.5 x Awesome. [email protected]

and by 'supposed to be' I just mean that is what the manual says... Is this where we got the space to include VLIST? Other blockfile words like MKBFL and USEBFL appear to work fine.

Is this why all the sprites go to warp speed on the way to the title screen?

Looking at the manual, that code didn't change in fbForth2.0:3 in the FBLOCKS file. And BFLNAM is supposed to be resident. I'll check my module and see if BFLNAM shows up.

I stopped going backwards, but not at Iwantgames level yet... 1340, is my best so far... So, this game, Cross Fire, says it is from Sierra On-Line. I was surprised, I only new them from their later PC publications. And then there is the sound effects... Which game did these originate in? The obvious answer would be Tombstone City as the source was shipped with Editor Assembler, but obvious isn't always correct... [email protected]

This game confirms that I'm bad at games On my first play I got 680, then my score went down by about half each time. Are there levels to this game? If you kill a monster do they come back randomly, or do you have to clear them all before they come back?

Yes, that was good stuff! I've been curious about that particular subject of comparison between these two Forths for a while. I enjoyed the discussion on floored division vs. 'symmetric' division. That could turn into a real astonishing difference. I was not previously aware of the significance of that. I found this paper on division: http://research.microsoft.com/pubs/151917/divmodnote-letter.pdf There was a brief story of porting between TurboForth and fbForth, with the suggestion that the right thing to do is redefine the words, instead of rewriting the app that is being ported. I think this was treated once in this thread already, but as language features go, that is a pretty powerful aspect of Forth. Compilation binds to the definitions available at that time, and they stick. So the system stays coherent, even if you redefine something as integral as EMIT or CR. It seems to me that variables are also in the same definition stack, so they can be overridden as well with the same protections... Is that correct? I'll have to go do some learning Definitely good stuff!

I have another gift for you Lee, Try loading the CPYBLK from the the 20151026 FBLOCKS file. I'm getting a compilation error at the word BFLNAM. The error location is 586 on block 4. [email protected]

The eraser did work quite well, just as you said! The fbForth cartridge you made for me is all upgraded now And my code still worked. I have taken out the workarounds, and all my issues were fixed. Thanks! [email protected]

A long time ago Microsoft compilers had options to produce p-code, but I believed that to be their own thing so single binaries would work on DEC Alpha or Intel x86.

It is also likely that I misinterpreted the links to posts as links to the original posts that posted the bins... When I came online, I poured through those original threads, which gave me an appreciation for how much effort goes into making these games and other applications work when loaded off of ROM, and the bank switching issues. Anyway, there are still tie ins to the community... I'd consider the websites indexing these files as the duplicate work and your efforts here the original work. I suspect new stuff will land here as well.

I wouldn't drop them so quick. There is a lot of good stuff there already, great stuff for new people to see the health of the hobby. For the last two, you might just update the top post to point at Opry99er's site once it surpasses the info currently available. In particular, it is nice that the .BIN repo thread points to the threads and messages that provide the context around what those Bins actually are. It is an index into so much more than just the files. [email protected]

I spent most of my childhood waiting for the computer to load something, format something, download something, or list something I figured I can be patient enough to erase something with a little light. Anyone use one of these?: http://www.ebay.com/itm/301718071627 I ordered it special for handling these fbForth updates... I've heard it referred to as 'scary', but I don't think it will get here in time for Halloween. Some reviewer called them scary asserting that it looked like it would burn your house down.

I believe it is that design... SP3232EE. Ridiculously difficult to read. And I was wrong, this wasn't the $3 item of DX.com, but a $10 item I got from Amazon: http://www.amazon.com/gp/product/B00OPTOKI0 I had purchased a similar item from DX.com but it was less convenient to integrate.

I had the impression the extra wires were mostly there to control write selection. So I was thinking since the board is socketed onto the card, replacing the card with an eprom might be just fine... But then I was noticing today that Fred Kaal's loader loads two different banks. I haven't looked at the schematics at all yet. But the stability seems worth it a little research.

If you never want to retire from fiddling with the language, an interesting future might be to have a facility to load blocks from more pages in the cart rom. With an auto load if present, situation. Something that would enable deployment of a forth app/game as a cart itself. Just a thought as it sounds like both forths would need some significant change if they got any bigger. Maybe that change could make them extensible as well as bigger. [email protected]