Corrections to Sources
ricortes
hobby to make a couple of corrections if I haven't done them already.
A bit of background: I have a couple of Cybiko hand held PDAs. They
were pretty capable systems in their time H8 ~16/32 bit main processor
depending on how you define your processor running at 11 mHz. There is
a Cybiko Xtreme that runs faster but it doesn't have a built in serial
port so it is less interesting for the task at hand. I *THINK* they
sold something like 3 million of them and they appear on fleabay for
$5-$20 every once in a while.
Pavel Machek wrote a linux sio2pc type program and says he used a
75LS149 for his device. I think this is a typo or misspeak. There are
MC1489, MC1489A, SN55189, SN55189A, SN75189, SN75189A but to the best
of my knowledge there is no such animal. I think TI did come out with
something like a 75LS155 back in the CP/M days but I just can't
remember there every being a 75LS149.
Other thing is the 74LS138 in most of the schematics available online
is wrong, other then that they are pretty good.
When I took a C programming class it was back in the 80s. Honestly
looking at the make files in all their derivations I think they are
more sophisticated and more complex then anything C used to be.
Sheesh! I am trying to get back up to speed with the Cybiko SDK and
think I need to take a class in 'make file programming.' I had the
same gripe when working with cc65!
On the bright side I have femul.c compiling for the Cybiko mostly
right except for what should be simple stuff like include paths. The
Cybiko's default serial speed is 57k so making one work as an Atari
sio2pc drive should be trivial. It doesn't mean much for a non
expanded device, only ~512 flash and 512k ram, but i have a couple of
accessories like 1 meg expansion and mp3 player with a 16 meg SD card.
Kind of laughable these days but I think the max SD card you can have
is 64 megs. I think the smallest I have in my parts drawer is either
128 or 512 megs so I will probably crash it if I try to use it.<grin>
Been doing some ugly hacking: Tore apart a dead cell phone so I now
have a Cybiko running on Li ion batteries. It's only important in that
replacement batteries go for about $6 each plus shipping and you need
two of them. Seems to be working OK but I really should do some kind
of hack to get the voltage levels for charging right.
It's a hobby so I don't have to do something useful. I figure if I get
a stock Cybiko that holds a single 88k Atari disk image in the next
year I will call it a win. Anything beyond that will be gravy. Back
when i was writing a lot of software my development system was
typically just a 720k disk. I should just burn myself a sio2sd device
but I am obsessing on the Cybiko for some reason. I will ask on the
Cybiko forums is anyone is still around.
Rick
ricortes
Bill Kendrick
> When I took a C programming class it was back in the 80s. Honestly
> looking at the make files in all their derivations I think they are
> more sophisticated and more complex then anything C used to be.
> Sheesh! I am trying to get back up to speed with the Cybiko SDK and
> think I need to take a class in 'make file programming.' I had the
> same gripe when working with cc65!
of "Managing Projects with Make" by O'Reilly. Was pretty useful.
My naiive use is basically:
--- begin ---
# Var. for where to install my app
PREFIX=/usr/local
# ... and its data
DATA_PREFIX=($PREFIX)/share/my_app
# Flags to send C compiler. Including a hard-coded (#define) value
# that'll tell the app where to find its data. -Wall turns on 'all' warnings.
CFLAGS=-Wall -DPREFIX="$(DATA_PREFIX)"
# Default make target: build the app
all: my_executable
# Target for installing app and its data
install:
cp my_executable $(PREFIX)/bin/
cp -r data/ $(DATA_PREFIX)/
# Link the objects into the final executable
my_executable: my_app.o some_other_funcs.o
$(CC) ($LDFLAGS) my_app.o some_other_funcs.o -o my_executable
# Create my main object
my_app.o: my_app.c some_other_funcs.h
# Make's default rule is sufficient; it'll come out as:
# $(CC) my_app.c $(CFLAGS) -o my_app.o
# Create object for some other functions
some_other_funcs.o: some_other_funcs.c some_other_funcs.h
# Ditto
--- end ---
Or, yknow, something like that. :) There's some insanely clever stuff
you can get Make systems to do, but 99% of the time I just want it to handle
dependencies and take care of some variables.
For example, in the above case, on Linux a:
$ sudo make install
would install it into /usr/local/. But I could easily install it in the
non-local place:
$ make PREFIX=/usr
$ sudo make install PREFIX=/usr
or, like back when I was on a shared Unix (Solaris and SunOS) box in
college, I could tell it I want things to run from somewhere in my homedir.
(Notice I don't need to have root privileges -- no "sudo")
$ make PREFIX=/home/kendrick/opt
$ make install PREFIX=/home/kendrick/opt
I'm rambling. :)
--
-bill!
Sent from my computer
ricortes
> ricortes <ricor...@earthlink.net> wrote:
<snip>
Thanks for the tip, I am downloading Managing Projects with GNU Make,
3.Xth Edition to see if I can be enlightened.
"An implicit rule is either a pattern rule or a suffix rule.
There are built-in pattern rules for C, C++, Pascal, FORTRAN, ratfor,
Modula, Texinfo, TEX (including Tangle
and Weave), Emacs Lisp, RCS, and SCCS. In addition, there are rules
for supporting programs for these
languages, such as cpp, as, yacc, lex, tangle, weave and dvi tools. If
you are using any of these tools,
you'll probably find most of what you need in the built-in rules. If
you're using some unsupported languages
such as Java or XML, you will have to write rules of your own."
This could take a while.
> I'm rambling. :)
>
> --
> -bill!
> Sent from my computer
It's where I live. :) I feel like Rip Van Winkle. When I was last
awake I could go to Fry's to pick up some EPROMs and a bag of Doritos.
Went there yesterday and they had squat EPROMs but you could still get
a bag of chips<sic>. They had a stack of 6821's but the price was
double everyone online. I was thinking of trying to keep my SDX 4.19
ROM as is just in case something goes wrong when I burn 4.22 but the
nearest place to get a 27C512 is a 20 mile drive. I have an old 386sx
working motherboard I am trying to tell myself I should pull parts off
of. It was a back up position but my new EPROM burner seems to be
working OK.
BTW: I did get Puppy Linux burned into a CD and it worked well.
Unfortunately all the laptops I fixed went back and I left the CD in
one of them. Hard times: Woman I fixed them for took them all
including the one I was supposed to get to keep to sell for cigarette
money! Ah, life is but a joke.
Rick
Yo$$1960
> Pavel Machek wrote a linux sio2pc type program and says he used a 75LS149
> for his device. I think this is a typo or misspeak. There are MC1489,
Possibly 74LS149?
^
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
I'll be the rubbish you'll be the bin
Love Song - The Damned
ricortes
different designs, 74LS00, 4049, et cetera. Just about any inverting
logic or amp will work.
I guess it isn't a big deal: Everyone left probably already has one of
[sio2pc, sio2usb, sio2sd, sio2ide, emulator, ...]
Rick
Yo$$1960
> I can't find a 74LS149 in my data books either. I made several different
> I guess it isn't a big deal: Everyone left probably already has one of
> [sio2pc, sio2usb, sio2sd, sio2ide, emulator, ...]
years. Lack of space, TBH. However, I hope for that to change soon(-ish).
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
This Is Pop - XTC
ricortes
finally pulled the tags off my SDX ROM and it turns out it was a OTP
type w/o a window! I have version the 4.21 binary and didn't have
version 4.22. If I understand it only had code changes to detect a
65C816 processor and switch to FTE as the copyright holder. Correcting
my post about corrections!
I'm real slow coming back up to speed. For the last year or so my
Atari has been a gypsy system that I set up in front of the TV or 1702
monitor. Its been hooked up via sio2pc to half a dozen different
clones and laptops. I had it hooked up to my ATR8000 for a while but
SDX never played nicely with it: IIRC the time out is set way too
short in SD so you hear the babbling sio sounds a couple of times
before the built in head load delays in an ATR8000 start to read. I
may have to look into that...
Anyway, after 20 years of significant others who treated my Ataris
like an infectious disease I finally have a bit of tolerance with
space for a table and an LCD monitor somewhere other then a flooded
basement. Really feels good!
Found out the hard way there is no such thing as a 28 pin 512k flash
but that 386sx motherboard died for a good cause. Built a monitor
cable, still have 2-4 flavors of sio2pc cable laying around. Fatih
Aygün has a new sio2pc type Windows software AspeQt with high speed
routines. I still do have a small footprint PC running Windows XP
embedded with a fresh 10 gig CF I put in it last week to compliment
its 512 meg boot CF. That Puppy Linux Bill pointed me to can install
to a USB thumb drive so I even have a back up position. My old
Dataerase is taking an hour to erase an EPROM but there are a bunch of
<$30 ones on fleabay. Life is looking good.
Rick
Clu
> It's a hobby so I don't have to do something useful. I figure if I get
> a stock Cybiko that holds a single 88k Atari disk image in the next
> year I will call it a win. Anything beyond that will be gravy. Back
> when i was writing a lot of software my development system was
> typically just a 720k disk. I should just burn myself a sio2sd device
> but I am obsessing on the Cybiko for some reason. I will ask on the
> Cybiko forums is anyone is still around.
>
> Rick
Whoa, sounds pretty good actually. I have always liked the idea of
running a SIO2PC like device off something about the size of a
Portfolio, so this would be interesting to see.
. _ . Doctor Clu (of...)
/{_}{} =PRISON BOARD BBS=
/(- _O) 972-329-0781
( \____ ) telnet://rdfig.net