From: "benjaminmaggi" <benjaminmaggi@...>
Mar 11, 2006
I've brought MailStation model DET1 with the hope to start puting my
own pr=
ograms in it, but i dont know where to start, what cable
conections i need =
to transfer the programs and data, how to show
hidden menues, or what progr=
ams do i need to send and compile my
programs for the mcu.
From: "Cyrano Jones" <cyranojones_lalp@...>
Mar 12, 2006
model DET1 with the hope to start puting my
t know where to start,
Mailbug is a program I wrote that will let you loa=
d & run
your own code, in either the mailstation flash or ram.
(URL)
ps.yahoo.com/group/mailstation/files/Mailbug/mailbug_0.0.3/
onections i need to transfer the programs and data,
A parallel-laplink ca=
ble.
On the older DET1 models, you power up=
while holding
down <fn><sh><t> until you see the test mode menu.
You don'=
t need this menu to install and use mailbug
version 0.0.3.
Installing sb=
oot.rom (required with mailbug 0.0.3) will
wipe out most of the original f=
irmware in your mailstation.
If you would like to keep your original firmwa=
re intact,
you might want to wait for version 0.0.4 (hopefully
ready in jus=
t a few more days).
programs for the mcu.
There is no compiler yet. Can you program in z80 as=
sembler?
A free cross-assembler (as80) is in the file area, under mailbu=
g
directory. There is also a "hello world" example.
From: "John R. Hogerhuis" <jhoger@...>
Mar 12, 2006
On Sun, 2006-03-12 at 11:29 +0000, Cyrano Jones wrote:
Well there are lots of C and Pascal compilers for Z80. Most of them need
to run under a CP/M emulator and target a CP/M environment, but whether
generated code is dependent on the environment is usually a function of
the nature of the code itself, not the compiler.
There's also sdcc which comes with full source code.
(URL)
To my knowledge no one has used these with Mailstation yet. If you want
to generate short swaths of code I think you wouldn't have to do
anything special. If you want to use the standard library they provide,
you'll need to modify them so that they use the built in I/O routines or
you need to write your own i/o routines.
From: "benjaminmaggi" <benjaminmaggi@...>
Mar 12, 2006
rote:
ailStation model DET1 with the hope to start puting my
it, but i dont know where to start,
will let you load & run
r ram.
_0.0.3/
ta,
On the older DET1 models, you power up while holding
til you see the test mode menu.
d use mailbug
ailbug 0.0.3) will
ation.
ht want to wait for version 0.0.4 (hopefully
s).
or the mcu.
r?
=
Thanks !=
I've used parallax 8051 assembler to make my pic programs in the past
so =
im going to see if AS80 works for me, im not shure about the C or
pascal co=
mpilers.
So i hook up my laplink cable, then load mbug (in msdos) and then =
i
power on my DTE1, im i right thats the procedure ?
From: "Cyrano Jones" <cyranojones_lalp@...>
Jul 31, 2006
2006-03-12 at 11:29 +0000, Cyrano Jones wrote:
njaminmaggi@> wrote:
e hope to start puting my
o start,
r?
bug
re are lots of C and Pascal compilers for Z80. Most of them need
nder a CP/M emulator and target a CP/M environment, but whether
code is dependent on the environment is usually a function of
of the code itself, not the compiler.
ith full source code.
o one has used these with Mailstation yet. If you want
swaths of code I think you wouldn't have to do
ant to use the standard library they provide,
so that they use the built in I/O routines or
i/o routines.
What you said finally sunk in to my brain toda=
y. I don't think we would
need the putchar or getchar routines at all, as =
long as we are not writing
an old-fashioned-user-interface style program. =
(O-FUI????) <lmao>
If you are writing an event-driven GUI style app, you =
don't ever
do any input yourself. The OS receives the input, and packages=
up the
keystrokes from the keyboard (and input from other devices) and
pa=
sses them to your program as *parameters* in calls to your apps
event-handl=
er. You would never call getchar.
This is the format for the mailstations=
event records:
(who, signal, this, that)
"who" is the app number tha=
t the event is for.
"signal" is the event type (such as keydown, keyup, etc=
).
"this" and "that" are the data payload that go with the particular event=
.
In the case of key events, "this" is scancode, and "that" is ascii.
A ma=
ilstation app is basically an event handler. The mailstation
OS passes the=
se parameters to your apps event handler:
handleevent(who, state, sign=
al, this, that);
"state" is a single byte state variable that the OS keeps=
track of
for your app, between calls to handleevent. (handleevent returns=
this "state" on exit as the function result.)
The other four parameters =
are the event.
From: "John R." <jhoger@...>
Aug 1, 2006
On 7/31/06, Cyrano Jones <cyranojones_lalp@...>
CLI (command line interface)
True.
Come to think of it, what program isn't? ;-)
I typically call this state a "cookie" or "(execution) context." The
server/kernel/OS lets you register it with the system and it just
returns it to the client application as-is. I would guess it is fairly
easy to trade the cookie for a memory pointer which holds the rest of
the application's state (object oriented types would call this memory
"Self" or "This").
From: Gary Clouse <niklaus37217@...>
Aug 1, 2006
There are a few cross-compiler versions of small-C
that run under dos and output target code for various
8 bit cpus. Have to look around for one.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
(URL)
From: "John R." <jhoger@...>
Aug 3, 2006
On 8/1/06, Gary Clouse <niklaus37217@...> wrote:
SDCC, a C compiler, : (URL)
It already targets Z80.