Welcome, Guest. Please login or register.

Author Topic: RomWACK and SAD  (Read 2595 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline shIvaTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 751
    • Show only replies by shIva
    • http://preshi.blogspot.com
RomWACK and SAD
« on: April 11, 2004, 05:39:41 PM »
using loadwb -debug one can access the ROMWACK from the additional appearing menu. if activated a terminal with 9600-8N1 will show the output from the serial-port.
iirc when using kick1.2/1.3 the output was some sort of monitor - now with kick3.1 the connected terminal ony prints SAD? (which is (afaik) a debugger).
now : how do i get the full features of RomWACK with the console, without always getting SAD? ? :-?
shIva
the answer is [color=CC3300]42[/color] Support  Distributed Amiga - moo ;)
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: RomWACK and SAD
« Reply #1 on: April 11, 2004, 06:26:38 PM »
Quote
how do i get the full features of RomWACK with the console, without always getting SAD?

You don't.

For space shortage reason (afaik) ROMWack was replaced with barebone communication layer that is called SAD. SAD only defines very basic protocol to talk to external console debugger application. However, SAD can be used to upload higher level debugger if preferred (obviously you need a client to talk to SAD to upload replacement SAD!).

Most of the debugger functionality would reside on the client console application side.

Whether any SAD console clients ever existed is unknown, but at least I have never heard of any. I would imagine these tools did exist, but unfortunately were not made available for public.


YAY - this is my 500th post btw :-)