Iyonix softload for 09th Jan 2016 won't load.

The softload for the Iyonix (TungstenDev/523)loads until it reaches init.mod ADFSError: DataAbort: on data transfer at &FC2058F4 (Error number &80000002)

No more information I am afraid.

regard Ron.

The softload for the Iyonix (TungstenDev/523)loads until it reaches init.mod ADFSError: DataAbort: on

Had you tried the 2016-01-03 and 2016-01-08 builds or is the first 2016 you’ve run?
That would give a change point for the error.

Steve,
The 2016-01-03 ROM loads OK.

The 2016-01-08 ROM loads until;
init mod ADFSError: DataAbort: Abort on data transfer at &FC208F4 (error number &80000002)

Regards Ron.

The 2016-01-03 ROM loads OK.

Probably this change on Thursday.

@Steve,
Possible, prabable maybe ;-).

Whatever the cause neither the 8th or 9th of january softloads work on this Iyonix.

Regards Ron.

Should be fixed with the 2016-01-10 ROM – it was the changes to ADFS that broke it, due to some subtle differences between OS_Hardware and direct HAL calls.

it was the changes to ADFS that broke it

IANAP

One thing I would say is that the technique for narrowing the search is always valid and anyone can do it. So everyone reading this needs to take note.
Find the last working instance and the first broken instance and the cause, or at least the trigger, is between the two.

@ Jeffrey,
The 2016-01-11 Rom is OK. Thanks.
@ Steve,
I had tried the previous two ROMs but noticing that further work had been done for the 2016-01-09 ROM, reported that.

As the error happened when init.mod ADFSError: showed up on the loading list for both the 8th and the 9th softloads, I thought that was clue enough.

Icould of course put that after the abort notice there was only an asterik ;-).

Regards Ron.

@ Steve,
I had tried the previous two ROMs but noticing that further work had been done for the 2016-01-09 ROM, reported that.

As the error happened when init.mod ADFSError: showed up on the loading list for both the 8th and the 9th softloads, I thought that was clue enough.

Bear in mind that the first non-working is a marker for the latest bit worth looking at.
Once the fault has presented its continuance is no surprise rather like seeing butter on the carpet on Monday, it will stay until it is cleaned up so seeing it on the following Thursday informs you of nothing more than the fact no one cleaned up.
However, absence on the previous Friday means the accident happened on late Friday, or sometime Saturday or Sunday…