Re: [hatari-devel] Re: [Emutos-devel] floppy issue

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


Hi,

On keskiviikko 12 helmikuu 2014, Eero Tamminen wrote:
> Necessary tracing can be done easiest with with these 3 debugger scripts:
> 
> ==> fcreate.ini <==
> # break on Fcreate() and trace all GEMDOS calls
> b GemdosOpcode = 0x3C :trace :file trace.ini
> trace gemdos

Roger, add here:
	symbols etos512k.sym

> ==> trace.ini <==
> # trace FDC in addition to GEMDOS during this OS call
> trace gemdos,fdc

And replace above with:
	trace gemdos,fdc,cpu_symbols

> b pc = "NextPC" :once :trace :file regs.ini
> ==> regs.ini <==
> # show GEMDOS call return value (D0) & continue tracing just GEMDOS
> e d0
> trace gemdos
> ==================
> 
> And invoking Hatari like this:
> 	hatari --parse fcreate.ini -d . disk.st
> 
> It will trace all GEMDOS calls, and additionally trace FDC
> register/DMA usage during Fcreate() call (which is what fails),
> and show return value for the GEMDOS call, while you use EmuTOS.  [1]

To get also all EmuTOS symbols calls traced.

If you want to see also IO register accesses, add
"io_all" to the trace options.


> [1] Here's an example of what FDC operations EmuTOS tries to do
>     with the DMA failing Fcreate():

The symbols leading to FDC operations are:
....
floppy_rw
__modsi3
__divsi3
__udivsi3
__mulsi3
__divsi3
__udivsi3
flush_data_cache

During FDC operations following ones can also be called:
set_dma_addr
timeout_gpip
int_timerc
int_vbl
blink
flopvbl


	- Eero



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/