freemint-discuss

[Freemint-discuss] Debugging

[Mark D. <mdu...@at...>]

Hello all,

I was considering working on the freemint kernel, specifically the RWABS
issue on MiST.  I was wondering what your preferred way is to debug
problems... serial console/debugging, turning up the console output
error level, or what.  And what way do you have to upload new kernel
builds quickly.  How would you go about debugging an io issue that
prevents the filesystem from working (broad strokes here, I'm just
looking for something to start with).  Is there a way to step debug the
kernel and view memory?  I guess not as you would need something like a
BDM cable.

Thanks,
Mark

Re: [Freemint-discuss] Debugging

[Miro K. <mir...@gm...>]

Hi,

I was wondering what your preferred way is to debug problems...

I rely mostly on Aranym's /dev/nfstderr device, so in a way, the serial
console, yes. Many parts of the kernel offer additional detailed debugging
via #if 0's if needed. So I just usually collect a few MBs of data, look
what's happening, add / remove some outputs and fix the issue if possible.
If you can get to the desktop, it's nicer for real hardware as you can use
TosWin2 for debugging (/dev/xconout2 device).

Oh and often I just let the kernel crash, some kind of really strong
assert. ;-)

This has been usually enough for debugging even such fine grained issues as
this one:
https://github.com/freemint/freemint/issues/40#issuecomment-304434775

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org

Re: [Freemint-discuss] Debugging

[Thorsten O. <ad...@th...>]

On Dienstag, 6. Februar 2018 01:28:00 CET Miro Kropáček wrote:
> I rely mostly on Aranym's /dev/nfstderr device, so in a way, the serial
> console, yes.

When running under Aranym, i prefer the direct output via nf_call(NF_STDERR , 
...) calls. That has the big advantage that the output goes to the terminal 
where you started it, and does not mess up the atari screen in any way.

However, i think that does not help in his case, as he is running MiNT on real 
hardware (even if it is a clone)

Re: [Freemint-discuss] Debugging

[Markus F. <mf...@mu...>]

I'm wondering what Rwabs() issue we might have on MiST?

Works for me (EmuTOS 0.9.9 + FreeMiNT latest), mainly. Some issues with
warm resets (such that 'reboot' doesn't work reliably, but hangs with
scrambled screen most of the time) but other than that, it's working
fine, fast (faster than a real Falcon) and pretty stable.

I'd assume the reboot failure is caused by the MiST core's handling of
the asynchronous reset and not a FreeMiNT code issue.


Am 06.02.2018 um 01:04 schrieb Mark Duckworth:
> Hello all,
>
> I was considering working on the freemint kernel, specifically the RWABS
> issue on MiST.  I was wondering what your preferred way is to debug
> problems... serial console/debugging, turning up the console output
> error level, or what.  And what way do you have to upload new kernelot
> builds quickly.  How would you go about debugging an io issue that
> prevents the filesystem from working (broad strokes here, I'm just
> looking for something to start with).  Is there a way to step debug the
> kernel and view memory?  I guess not as you would need something like a
> BDM cable.
>
> Thanks,
> Mark
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Freemint-discuss mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freemint-discuss

Re: [Freemint-discuss] Debugging

[Mark D. <mdu...@at...>]

I didn't think to try with Emutos which might make all the difference.
I was using Tos 2.06.  The issue is that reads/writes don't really work
properly.  I am able to get it to mostly boot to XaAES with the old fast
fs but when I use newfatfs I get some RWABS error whose specific code I
can't remember.  I believe it was "attempt to read past end of
partition".  Which kind of disk mode are you using.  Are you using an
ACSI or are you using the hybrid SD mode?

Thanks,
Mark


On 02/06/2018 12:08 AM, Markus Fröschle wrote:
> I'm wondering what Rwabs() issue we might have on MiST?
> 
> Works for me (EmuTOS 0.9.9 + FreeMiNT latest), mainly. Some issues with
> warm resets (such that 'reboot' doesn't work reliably, but hangs with
> scrambled screen most of the time) but other than that, it's working
> fine, fast (faster than a real Falcon) and pretty stable.
> 
> I'd assume the reboot failure is caused by the MiST core's handling of
> the asynchronous reset and not a FreeMiNT code issue.
> 

Re: [Freemint-discuss] Debugging

[Markus F. <mf...@mu...>]

Am 06.02.2018 um 06:38 schrieb Mark Duckworth:
> I didn't think to try with Emutos which might make all the difference.
> I was using Tos 2.06.  The issue is that reads/writes don't really work
> properly.  I am able to get it to mostly boot to XaAES with the old fast
> fs but when I use newfatfs I get some RWABS error whose specific code I
> can't remember.  I believe it was "attempt to read past end of
> partition".  Which kind of disk mode are you using.  Are you using an
> ACSI or are you using the hybrid SD mode?
I'm using an ACSI image on SD. Can try TOS2.06 when I'm at my MiST next
time (but this might take a while).