dcal linux

Hope am in the right place here...

Here a small appetizer from over the pond (germany)

I am using many feats like the windows-version of dcal and wrote my own linux version.
There is no reverse engeneering, it's all written from scratch. I started 4 yrs ago with lots of breaks inbetween but now it's become somewhat usable.

If there is any interest, then of course am gonna share this all to the community later.

The binary tables may be edited either in Hex/Ascii (by hand) or by snapping the points with mouse and moving them within the graph.

Here a screenshot of the linux variant :D

http://desmond.imageshack.us/Himg825...1.png&res=crop

Any feedback is highly appreciated.

Future plan is to integrate a software 6811 emulation into dcal-linux itself to dry-run the .bin on the pc/laptop and to directly control sorta ostrich thingie directly from dcal ...

Just wanted to let you know that there is still some activity out there :eyebrows:

btw, here my site : www.lebaron.de (attn: its german)

And Rob, big Thankies for all the .asm docu detective stuff, the project wouldnt be doable without it.

Nice, I'm sure there are a few Linux fans around here who'd like to try it. Your site looks good too.

Interesting...

Any chance it would run on Android? I have Android x86 running on my netbook...

Android ... hmmm

It's written in plain c and the windows&clicksy stuff is entirely gtk, so if that is available on android then it should work.
It runs on anything linux and mac with backport stuff and i guess on win with the cygwin environment.

I'll show you an excerpt of the Makefile so you see for yourself if it runs.

----- 8< ------ SNIP ------- 8< --------

INCLUDES = \
-DPACKAGE_DATA_DIR=\""$(datadir)"\" \
-DPACKAGE_LOCALE_DIR=\""$(prefix)/$(DATADIRNAME)/locale"\" \
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12


dcal_SOURCES = \
main.c \
support.c support.h \
interface.c interface.h \
callbacks.c callbacks.h \
dcal.h \
table.c \
table.h \
sbec_file.c \
sbec_tab.c \
sbec_info.c \
sbec_asm.c \
sbec-tool.c \
sbec-tool.h \
sbec_draw.c \
sbec_draw.h \
utils.c \
utils.h \
background.h \
global.h \
global.c \
sbec_info.h \
hexview.c \
hexview.h \
gtkhex-private.h \
ghex-marshal.c \
ghex-marshal.h \
ghex-marshal.list \
gtkhex.c \
gtkhex.h \
hex-document.c \
hex-document.h


dcal_LDADD = -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 $(INTLLIBS)


------ 8< ------ SNIP ----- 8< ------

I think chances are good for Android or even porting it to an app for mobiles/tablets.

There is still a long way to go ...

the values (scaling) for the axis x/y isn't done yet
neither the 2D tables yet,
neither the detection of vars in the 0x00-0xff ram area
serial (sci / spi) stuff not yet implemented.
automatic removal of speed/rev limit and auto-speed limits not yet implemented.

I still need a way to identify the ram-locs (0x00-0xff), i dont want to go the hard DRB-way, say executing all tests just to find out where everything resides. Bad thing is, on every different .bin i skimmed thru i saw them on diff. locations, obviously.
Executing or tracing the foo_MM routines is the other stony way.

btw, i just use the expression dcal, only to have a reference of what i am talking about, although similarities in optic and design and and usebility are intended, LOL.

Of course if the program finds a .tbl file then one does not need to press the "SCAN" button for the program to do an in-depth search in the loaded .bin by comparing and tinkering with known tables to fish for rom-tables.
The hit probability is quite high, even slightly changed/modified tables are still identified even if you do not have a .tbl.

Vielen dank!!

Keep up the good work!