Re: [M100] compact embedded ML coding

2018-05-31 Thread Willard Goosey
On Thu, 31 May 2018 12:22:43 -0700 "John R. Hogerhuis" wrote: > Here is the classic 8085 relative jump for those interested. > > It requires some code at a fixed location :-) Classic cleverness! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find

Re: [M100] compact embedded ML coding

2018-05-31 Thread Willard Goosey
On Thu, 31 May 2018 14:15:19 -0500 John Gardner wrote: > Your code can figure out it's execution address with something like: > > call @Boo > Boo pop B > pop A > > Boo's address is now in register pair A,B... > Umm, on a point of order... I see what you're

Re: [M100] compact embedded ML coding

2018-05-31 Thread Willard Goosey
On Wed, 30 May 2018 14:48:11 -0400 Stephen Adolph wrote: > I often want to embed ML into basic programs. There are 2 ways that > I use 1) make a string of binary and assign it to a basic string > variable. (use VARPTR) > 2) include data statements that contain the ML binary, with some >

[M100] NEC CMT port speed

2018-05-31 Thread Kurt McCullum
I've been reading through the technical manual for the 8201. I noticed that on page 1-2 it lists the baud rate of the cassette port at 600 or 1200 and that it is software selectable. But I don't see any reference as to where this is set. Does anyone know how to bump it from the default of 600 to

[M100] QRCode to load CloudT

2018-05-31 Thread John R. Hogerhuis
Funny, I had no idea the iPhone camera feature would activate QRCode links! In the past you had to rely on a barcode scanner app being installed and launched. So if you have the QRCode below on a card or sticker or something, you just Open Camera Point it at the QRCode Your iPhone or iPad will

Re: [M100] M200 Differences

2018-05-31 Thread John R. Hogerhuis
On Thu, May 31, 2018 at 2:02 PM, Ken Pettit wrote: > On 5/31/18 1:48 PM, John R. Hogerhuis wrote: > >> >> -clip- Who spends time writing code whose only purpose is to prevent >> software from working? >> > > Hmm, let's see ... Cadence, Synopsys, Autodesk, Oracle, Mathworks, ... > > Sometimes

Re: [M100] M200 Differences

2018-05-31 Thread Ken Pettit
On 5/31/18 1:48 PM, John R. Hogerhuis wrote: -clip- Who spends time writing code whose only purpose is to prevent software from working? Hmm, let's see ... Cadence, Synopsys, Autodesk, Oracle, Mathworks, ... Sometimes they call it a License Manager. ;) Ken

Re: [M100] M200 Differences

2018-05-31 Thread John R. Hogerhuis
On Thu, May 31, 2018 at 1:41 PM, Eric Nelson wrote: > I did try and toggle the control flow using the STAT line to no avail, but > I did not tinker with the settings on the Wifi232. I will give that a shot > and report back. Thanks for the help! > > DTR/DSR is enforced here and there by the ROM

Re: [M100] M200 Differences

2018-05-31 Thread Eric Nelson
I did try and toggle the control flow using the STAT line to no avail, but I did not tinker with the settings on the Wifi232. I will give that a shot and report back. Thanks for the help! >it has a solder jumper to assert dsr/dtr >On Thu, May 31, 2018 at 10:18 AM, John R. Hogerhuis wrote: > >

Re: [M100] compact embedded ML coding

2018-05-31 Thread Ken Pettit
Oh, And speaking of hidey holes, there is a 52-byte hidey hole that exists while BASIC is running that I don't believe anyone has ever realized exists or has used before. On the M100 this address starts at F6EBH. It is a table of 26 2-byte addresses which is used only in TEXT mode. TEXT

Re: [M100] compact embedded ML coding

2018-05-31 Thread Ken Pettit
Yeah, that's just 4 bytes of code. That could go in a hidey hole (Suzuki, Hayashi, etc.). Ken On 5/31/18 12:45 PM, John Gardner wrote: ...Reljmp.pdf... Nice. Thanks. On 5/31/18, John Gardner wrote: Hi John - I'm thinking about Ken's idea of having code embedded in BASIC jumping to

[M100] Fwd: Reporting Breakthrough for "Run In Place" Operation -- Was Re: Remem : relocatable ML codes.

2018-05-31 Thread John R. Hogerhuis
Self-locating code. Ron Wiesen did some research a long time ago to figure out code in the ROM that could tell you where you are calling from. This is a critical part of code that can efficiently relocate itself to run-in-place or at a specific location. -- John. -- Forwarded message

Re: [M100] compact embedded ML coding

2018-05-31 Thread John Gardner
...Reljmp.pdf... Nice. Thanks. On 5/31/18, John Gardner wrote: > Hi John - > > I'm thinking about Ken's idea of having code embedded in BASIC > > jumping to code embedded in a DO file - Sounds workable, even > > reasonable with a big routine, or a number of smaller routines. > > On 5/31/18,

Re: [M100] compact embedded ML coding

2018-05-31 Thread John Gardner
Hi John - I'm thinking about Ken's idea of having code embedded in BASIC jumping to code embedded in a DO file - Sounds workable, even reasonable with a big routine, or a number of smaller routines. On 5/31/18, John R. Hogerhuis wrote: > On Thu, May 31, 2018 at 12:15 PM, John Gardner

Re: [M100] compact embedded ML coding

2018-05-31 Thread John R. Hogerhuis
Here is the classic 8085 relative jump for those interested. It requires some code at a fixed location :-) RelJMP.pdf Description: Adobe PDF document

Re: [M100] compact embedded ML coding

2018-05-31 Thread John R. Hogerhuis
On Thu, May 31, 2018 at 12:15 PM, John Gardner wrote: > Your code can figure out it's execution address with something like: > > call @Boo > Boo pop B > pop A > > Boo's address is now in register pair A,B... > But you kind of already know since that code would

Re: [M100] compact embedded ML coding

2018-05-31 Thread John Gardner
Your code can figure out it's execution address with something like: call @Boo Boo pop B pop A Boo's address is now in register pair A,B... ...

Re: [M100] compact embedded ML coding

2018-05-31 Thread John R. Hogerhuis
On Thu, May 31, 2018 at 11:51 AM, Stephen Adolph wrote: > Ken, > so you are suggesting the .BA file calls into the .DO file? interesting. > > When I embed programs as strings, I write the program to avoid codes <32 > d. > ex. > mvi a,00 > is bad > xra a > is good. > > Maybe the best of both

Re: [M100] compact embedded ML coding

2018-05-31 Thread Ken Pettit
Hey Steve, Yes, then you aren't as restricted on the opcodes plus you don't need any encoding. You just need to ensure 1Ah doesn't appear anywhere. I suppose if your ML code snippets don't need to perform any jumps to address that require a byte <32, it works out. Also, I guess if you need

Re: [M100] compact embedded ML coding

2018-05-31 Thread Stephen Adolph
Ken, so you are suggesting the .BA file calls into the .DO file? interesting. When I embed programs as strings, I write the program to avoid codes <32 d. ex. mvi a,00 is bad xra a is good. On Thu, May 31, 2018 at 2:34 PM, Ken Pettit wrote: > Hey guys, > > Looking at this a bit, it seems

Re: [M100] compact embedded ML coding

2018-05-31 Thread John R. Hogerhuis
The relative branch technique I’ve seen requires a few bytes of code at a fixed location. — John.

Re: [M100] compact embedded ML coding

2018-05-31 Thread Ken Pettit
Hey guys, Looking at this a bit, it seems because of the restrictions imposed by BASIC with regard to binary values less than 32 decimal, the only real viable way to do execute in-place ML code would be to imbed it in a .DO file. Then the only restriction is that you can't have 26 decimal

Re: [M100] M200 differences

2018-05-31 Thread Gregory McGill
it has a solder jumper to assert dsr/dtr On Thu, May 31, 2018 at 10:18 AM, John R. Hogerhuis wrote: > > On Thu, May 31, 2018 at 10:10 AM Kurt McCullum wrote: > >> My 200 was picky about the DSR/DTR lines. I seem to recall that without a >> loopback of those it wasn't happy. >> >> > If the

Re: [M100] M200 differences

2018-05-31 Thread John R. Hogerhuis
On Thu, May 31, 2018 at 10:10 AM Kurt McCullum wrote: > My 200 was picky about the DSR/DTR lines. I seem to recall that without a > loopback of those it wasn't happy. > > If the wifi232 is not asserting the t200’s DSR it ought to be! Maybe it’s configurable. — John.

Re: [M100] M200 differences

2018-05-31 Thread Kurt McCullum
My 200 was picky about the DSR/DTR lines. I seem to recall that without a loopback of those it wasn't happy. On Thu, May 31, 2018, at 7:50 AM, Gregory McGill wrote: > I had this problem with a wimodem sending xon/xoff to my term program > on a commodore and I ended up having to disable xon/off in

Re: [M100] compact embedded ML coding

2018-05-31 Thread John Gardner
Hi Steve - My original scheme (for TI-74) was to make the 1st pgm line the DATA statement, in the form: 100 DATA ### ... ### The "#" character are simply placeholders, up to 80 chars, the max length of a DATA statement in TI-74 BASIC. A TI-74 "main" pgm always starts at HIRAM;

Re: [M100] M200 differences

2018-05-31 Thread Gregory McGill
I had this problem with a wimodem sending xon/xoff to my term program on a commodore and I ended up having to disable xon/off in the terminal to get it to stop locking the terminal up On Wed, May 30, 2018 at 10:13 PM, John R. Hogerhuis wrote: > > Instead of connecting to Wifi232 can you try

Re: [M100] compact embedded ML coding

2018-05-31 Thread Ken Pettit
Hi Steve, Search through BASIC lines? Nah, don't do that! Put a dummy DATA statement and then your ML code: 10 DATA "a", "encoded ML" Then do a READ D$. The BASIC ROM will perform the search and update address FBB8H (on M100/T102) with the address where READ will start it's search next.

[M100] Fwd: compact embedded ML coding

2018-05-31 Thread Stephen Adolph
here is an example - RAMTST - 64704 to 64936, so 232 bytes this was the intel hex :18FCC000CD3142F33E01D3E02E0926FECD8EFD2136802E0926BE62 :18FCD800CD8EFD2136402E0926FECD8EFD217E32A8FDAFD37A :18FCF000E0FB3E0232A7FD3AA8FD4F3AA7FDB9C83C3C32A7FD2101010D

Re: [M100] compact embedded ML coding

2018-05-31 Thread Stephen Adolph
John I think a scheme like that could work, however you'd need to eliminate all codes under 32decimal. To run in place, you lose the ability to encode/decode the problematic characters. finding the DATA statements in RAM can be done but it is a bit of work. I think you'd have to start from the