Hi there,

Today I finally managed to make my first OS4 program ever. It's a straight port of the MorphOS version (as straight as possible, so its not reentrant as the versions for MorphOS or m68k). It's completly untested too, so it might just crash and die or something.

After all it's just a proof-of-concept try to see how much work is involved to do ports for OS4 by using MorphOS. I don't even know if it has use at all on OS4... but what the hell.. here u go. Feedback appreciated (would like to know if it works at all ;) ).

OS4 version:
http://tokai.binaryriot.org/public/serialecho-50.2-os4.lha

MorphOS version:
http://tokai.binaryriot.org/public/serialecho-50.2-morphos.lha

AmigaOS (m68k) version:
http://tokai.binaryriot.org/public/serialecho-50.2-amigaos.lha

Source Archives:
http://tokai.binaryriot.org/public/serialecho-50.2-source.tar.bz2
http://tokai.binaryriot.org/public/serialecho-50.2-source.tar.gz


with kind regards,
tokai
--
MorphOS Team Member

_________________
tokai.binaryriot.org binaryriot.de

@tokai

Thanks for yor port, any type of program compiled for OS4 is welcomed here. I hope I'll be able to dig out a serial cable to test the program. BTW I believe to have seen the archive of the 68k/MOS versions this morning on aminet, have they been removed?

Varthall

_________________
AmigaOne XE - AmigaOS 4.1 - Freescale 7457 1GHz - 1GB ram

@Varthall

if Sashimi works on OS4 you could use that instead a serial cable. Dunno if OS4 has some dedicated debug machnism like MorphOS does which redirecty all kind of debug to some buffer in RAM (hence its called Ramdebug on MorphOS).

And nope, I didn't uploaded archives to aminet. I'm too lazy for this. Once cgutjahr did it for me. Dunno if he'll have time to upload this archives too some day. ;) You probably saw them in the amiganews.de news section.

regards,
tokai

_________________
tokai.binaryriot.org binaryriot.de

@tokai

it works as aspected here on AmigaOS4 classic with sashimi

_________________

@tokai

Quote:

tokai wrote: Dunno if OS4 has some dedicated debug machnism like MorphOS does which redirecty all kind of debug to some buffer in RAM (hence its called Ramdebug on MorphOS).

It does, and it's really useful. The command is called DumpDebugBuffer which will write the debug buffer contents to disk. The debug buffer survives a crash/soft-reboot.

BTW, what does your program do?

Hans

_________________
Join the Kea Campus - upgrade your skills; support my work; enjoy the Amiga corner.
https://keasigmadelta.com/ - see more of my work

@tokai

What kind of program did you port?

Is an app,a game or other?

Anyway nice to see more OS4 soft.

_________________
AMIGA 500 1.5 MB ACA500/ACA1232 accelerators
AMIGA 500 German
CD32 unexpanded
Amiga 1200 Tower on AmigaKit since years
AMIGA 1300 030/50 Mhz/32 MB WB 3.9 with lots of games&demos
AMIGA ONE XE G3 PPC 800 Mhz/1 GB RAM/RADEON 9250 128 MB/SATA CONTROLLER

@newlight

From the readme of an older version on Aminet:

Quote:

Works like "echo" command, but dumps output to serial debug log.

Varthall

_________________
AmigaOne XE - AmigaOS 4.1 - Freescale 7457 1GHz - 1GB ram

SerialEcho 50.2
Dumps a line to serial debug output

Copyright © 2005-2008 Christian Rosentreter.
All rights reserved.

Introduction
------------
"SerialEcho works like the AmigaDOS built-in command 'Echo',
but its output is redirected to the serial port instead
(which can be catched with another computer connected to
the serial port or a tool like Sashimi)."

Last edited by Framiga on 04-Mar-2008 at 04:02 PM.

_________________

@Hans

Quote:

BTW, what does your program do?

Well.. its a 'echo' command which writes its output to serial debug and not to the standard output. So the output should theoretically appear in this ram debug buffer of OS4 (or over the serial port.. depending on os4 settings, I guess).

Anyway... the use is quite limited. But like I said: it's more of some proof-of-concept port to see if things work at all or not. I don't have OS4 myself to test things obvioulsy. :)

regards,
tokai

_________________
tokai.binaryriot.org binaryriot.de

@tokai

Quote:

Anyway... the use is quite limited. But like I said: it's more of some proof-of-concept port to see if things work at all or not. I don't have OS4 myself to test things obvioulsy. :)

You'll find quite a number of people here happy to test for you on OS4.
Somewhat off-topic, but would you be so kind as to take a look at:
this thread
Apparently something has caused a conflict since you folks helped out with a prior issue concerning ANR.
Is there anything we could do testing wise to help get this addressed?
I know a lot of people miss being able to run this fine program. (me, amongst them)

Best wishes,

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

AFAIK UltraGelb investigated theses issues already. Don't know yet anything about the status/progress/outcome. Best is to join #amigazeux (irc.amigazeux.net) and poke Gelb directly about such things.

regards,
tokai

_________________
tokai.binaryriot.org binaryriot.de

@tokai

Im sometimes there and did some testings without success, but its better if people that know coding and understand os4/classic etc could talk with ultragelb and discuss this. Maybe you could fix it somehow to run this really fine music player (ANR) on os4 too.

@tokai

I don’t get it, way not type:

Echo “Some text” >SER:

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

You can't catch Echo "something" >SER: with Sashimi f.ex. It also would not appear in the (MorphOS) debug log as it would always go to the real (hardware) serial port. Further you need SER: mounted, which you might not have when using it on some 68k floppy to get some debug info out of some script. E.g. an old friend of mine uses the 68k version of SerialEcho now with an old A1200 to get some log, as the machine just boots from some floppy for a custom task and has no monitor attached. Since SerialEcho is less than 400 bytes in size it even fits on his fully packed floppy disk.

The practical use for the average user is very limited, like I said.

regards,
tokai

_________________
tokai.binaryriot.org binaryriot.de

@tokai

So it more like debugecho then serecho, cool

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Probably that would have been a better name. ;)

_________________
tokai.binaryriot.org binaryriot.de

Once again I took some time and compiled a MorphOS cli command with vbcc for OS4. And once again I have no idea if it will work or not (you might just crash if you're lucky).

Quote:

Tooltype is a commandline tool for manipulation of the tooltype array wich is contained in icon files (#?.info). Actually I don't know what this is good for really, but a few years back a friendly fellow (hello analogkid!) on #amiganews.de (irc.freenode.net) asked me for such tool which works on MorphOS and since there was no proper one and I was bored at the time this little tool was created. Tooltype can be made resident (note: the OS4 port can't be made resident yet).

The OS4 binary is almost 4 times as large as the MorphOS version. If someone can point out an elegant way to optimize this (I have to redefine NewRawDoFmt() to use sprintf() instead atm.) this would be appreciated. Already all the Interface stuff blows a lot and adds chaos to the source. :)

regards,
tokai


forgot the links ;)

OS4 version:
http://tokai.binaryriot.org/public/tooltype-1.4-os4.lha

MorphOS version:
http://tokai.binaryriot.org/public/tooltype-1.4-morphos.lha

Last edited by tokai on 06-Mar-2008 at 02:39 PM.

_________________
tokai.binaryriot.org binaryriot.de

@tokai

Quote:

tokai wrote: The OS4 binary is almost 4 times as large as the MorphOS version. If someone can point out an elegant way to optimize this (I have to redefine NewRawDoFmt() to use sprintf() instead atm.) this would be appreciated. Already all the Interface stuff blows a lot and adds chaos to the source. :)

Did you strip the binary? Otherwise all symbols (only useful for debugging) remain.

Also, compile with the -mcrt=newlib switch (make sure you do this on linking too). The newlib version of the c runtime library is much smaller than clib2.

Hans

_________________
Join the Kea Campus - upgrade your skills; support my work; enjoy the Amiga corner.
https://keasigmadelta.com/ - see more of my work

@Hans

well.. vbcc doesn't add debug symbols like gcc on default, so striping is not the issue.

The issue is the rather large sprintf() which currently gets statically linked to the binary.

Newlib probably could avoid this. But I have no newlib support (target) for vbcc and not really time/mood to find out how to do it. I'm a gcc user after all and use vbcc only for some quick compiles for non-morphos targets (os4 only atm., as m68k doesn't want), if easily possible w/o too much hassle.

Anyway... I really would prefer something direclty from exec, so I just need to change the NewRawDoFmt() define. Thats what I just was wondering: If OS4 also has some extended/PPC compatible RawDoFmt() which could be used for this. If not then its fine too, just the binary is noticable larger then.

regards,
tokai

Last edited by tokai on 06-Mar-2008 at 02:51 PM.

_________________
tokai.binaryriot.org binaryriot.de

@tokai

Try vbcc +newlib (or vc +newlib, I've never used vbcc personally).

If you're a GCC user, why not use GCC for your OS4 ports? There are GCC cross-compilers available (courtesy of zerohero). You could use virtually identical makefiles. Regarding RawDoFmt() in the exec; I'm not sure about that one. You'll have to look at the OS4 autodocs in the SDK (which you must have as you're cross compiling; other wise, download it here).

What would be nice would be to have a set of easliy installable cross-compilers that run natively on OS4 and MorphOS.

Hans

_________________
Join the Kea Campus - upgrade your skills; support my work; enjoy the Amiga corner.
https://keasigmadelta.com/ - see more of my work