forums.jaspp.org.uk

Posted: **Thu Oct 27, 2022**

JonAbbott wrote: Fri Oct 21, 2022 I've just updated the IDEFS support in the attached, could you please try it against the APDL in your A540 and post the DEBUG/TXT. Same for the Simtec in the A480

Hmm. Just (re?)downloaded this. It causes the A540 (APDL) to go completely SPLAT, even if I don't hold alt. Complete machine lock - very nasty.

Here's the debug.txt from the 'A480' (Simtec) anyway...

Code: Select all

PartMgr v0.89 21/10/22 DEBUG
OS Version=310
ADFS found
IDEFS found
BASIC END=44C30

read_drives
===========

IDEFS
-----
Potentially 4 drives
IDEFS detected as Simtec
IDEFS_IDEUserOp failed R0=1000000 R4=200 flags=6
IDEFS_IDEUserOp failed R0=1000000 R4=200 flags=6
IDEFS_IDEUserOp failed R0=1000000 R4=200 flags=6
IDEFS_IDEUserOp failed R0=1000000 R4=200 flags=6
BASIC END=45024

Posted: **Thu Oct 27, 2022**

IanJeffray wrote: Thu Oct 27, 2022 It causes the A540 (APDL) to go completely SPLAT, even if I don't hold alt. Complete machine lock - very nasty.

Either the APDL SWI aren't the same as the ICS - or more likely, it's waiting for a response from non-existent drives.

Did it write anything to the debug log? It closes the file after each debug log entry, so it should in theory have written the last thing it did.

Posted: **Thu Oct 27, 2022**

JonAbbott wrote: Thu Oct 27, 2022 Did it write anything to the debug log? It closes the file after each debug log entry, so it should in theory have written the last thing it did.

Ah. Hm. It seems it did, yes. Even when running from the IDEFS that it choked on.

Code: Select all

PartMgr v0.89 21/10/22 DEBUG
OS Version=311
ADFS found
CDFS found
IDEFS found
SCSIFS found
BASIC END=47E58

read_drives
===========

CDFS
----

IDEFS
-----
Potentially 4 drives
IDEFS detected as APDL
Trying DiscOp 3 against IDEFS:0
IDEFS discop_ICS(0,3,&0,&0,..,&0)
  IDEFS_DiscOp+&3F,,3,&0,..,&0,,0
DiscOp 3 response: DiscRec
Address :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F
&000000 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000010 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000020 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000030 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................

DiscOp 3 response: ID block
Address :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F
&000000 : 8A 84 47 1E 00 00 10 00 00 00 40 02 3F 00 77 00   ..G.......@.?.w.
&000010 : 00 38 00 00 20 20 20 20 44 20 5A 43 34 30 33 30   .8..    D ZC4030
&000020 : 32 31 35 31 30 35 34 34 02 00 02 00 04 00 44 48   21510544......DH
&000030 : 20 58 2E 36 32 30 61 53 44 6E 73 69 20 6B 44 53    X.620aSDnsi kDS
&000040 : 46 43 2D 48 30 30 47 34 20 20 20 20 20 20 20 20   FC-H00G4        
&000050 : 20 20 20 20 20 20 20 20 20 20 20 20 20 20 01 80                 ..
&000060 : 00 00 00 23 00 00 00 02 00 00 07 00 47 1E 10 00   ...#........G...
&000070 : 3F 00 90 37 77 00 00 01 00 38 77 00 00 00 07 00   ?..7w....8w.....
&000080 : 03 00 78 00 78 00 78 00 78 00 20 40 00 00 00 00   ..x.x.x.x. @....
&000090 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0000A0 : 00 00 00 00 20 70 0C 74 40 40 20 70 04 04 40 40   .... p.t@@ p..@@
&0000B0 : 1F 00 00 00 00 00 00 00 FE FF 00 00 00 00 00 00   ................
&0000C0 : 00 00 00 00 00 00 00 00 00 38 77 00 00 00 00 00   .........8w.....
&0000D0 : 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000140 : F4 81 00 00 00 00 82 00 00 00 00 00 00 00 00 50   ...............P
&000150 : 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
&0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................

Flash based drive
Drive supports LBA addressing
Physical drive is IDEFS 0
LBA Size    =512
Size in LBA =&000773800
D_Removable%=-1
Trying DiscOp 3 against IDEFS:1
IDEFS discop_ICS(1,3,&0,&0,..,&0)
  IDEFS_DiscOp+&3F,,3,&0,..,&0,,1

Posted: **Fri Oct 28, 2022**

IanJeffray wrote: Thu Oct 27, 2022

Code: Select all

PartMgr v0.89 21/10/22 DEBUG
Trying DiscOp 3 against IDEFS:1
IDEFS discop_ICS(1,3,&0,&0,..,&0)
  IDEFS_DiscOp+&3F,,3,&0,..,&0,,1

Probably as I suspected, it's waiting for a non-existent drive instead of immediately returning an error. I'll see if the APDL Module has an SWI to validate physical devices, so I can restrict DiscOp 3 use.

As for the Simtec in the A480, SWI IDEFS_IDEUserOp doesn't appear to respond as expected. Could you confirm which version of the Module the Podule has? I thought I'd added it to the debug output, but clearly not in the right place

Posted: **Fri Oct 28, 2022**

JonAbbott wrote: Fri Oct 28, 2022 As for the Simtec in the A480, SWI IDEFS_IDEUserOp doesn't appear to respond as expected. Could you confirm which version of the Module the Podule has? I thought I'd added it to the debug output, but clearly not in the right place

It's 1.30 - attached.

I've just pulled out an A3010 with a Simtec IDE podule (again, 8 logical drives) - this is an 8bit podule though, of course. Same debug output as A480 again - nothing displayed in the window.
This podule has IDEFS 1.11e - attached.

Finally, I ran the latest 0.89 on a RiscPC with UniPod, which is again the same Simtec 1.30 - it shows the same debug output as the A480 does and displays nothing in the window.

Posted: **Fri Oct 28, 2022**

IanJeffray wrote: Thu Oct 27, 2022 It causes the A540 (APDL) to go completely SPLAT

Could you dump the 4 words starting at &3B0 in the Module's private area please. They appear to be the internal ID of the physical drives.

Posted: **Fri Oct 28, 2022**

IanJeffray wrote: Fri Oct 28, 2022
JonAbbott wrote: Fri Oct 28, 2022 As for the Simtec in the A480, SWI IDEFS_IDEUserOp doesn't appear to respond as expected. Could you confirm which version of the Module the Podule has? I thought I'd added it to the debug output, but clearly not in the right place
It's 1.30 - attached.

Although the Simtec has IDEFS_IDEUserOp in the SWI list - its not implemented, hence why its not detecting any drives. I'll have to get my hands on a Simtec Podule to take it further as I'll need to throw values at various SWI to see how they respond.

Posted: **Sat Oct 29, 2022**

JonAbbott wrote: Fri Oct 28, 2022
IanJeffray wrote: Thu Oct 27, 2022 It causes the A540 (APDL) to go completely SPLAT
Could you dump the 4 words starting at &3B0 in the Module's private area please. They appear to be the internal ID of the physical drives.

Here's the entire workspace, as yoinked with Zap.

Posted: **Sat Oct 29, 2022**

IanJeffray wrote: Sat Oct 29, 2022 Here's the entire workspace, as yoinked with Zap.

Thanks. I think I've made some progress, could you see what the Simtec outputs for the following:

Code: Select all

FOR A%=&10000 TO &10200:!A%=0:NEXT
SWI "IDEFS_Enumerate",-1 TO A%
PRINT ~A%
SWI "IDEFS_Enquire",A%,&10000
*MEMORY B 10000+200
SWI "IDEFS_Enumerate",A% TO A%
PRINT ~A%
IF A%>0 THEN SWI "IDEFS_Enquire",A%,&10000

That hopefully performs an IDENTIFY on the drive and the last SWI should either not be called or should error

Posted: **Sat Oct 29, 2022**

JonAbbott wrote: Sat Oct 29, 2022
IanJeffray wrote: Sat Oct 29, 2022 Here's the entire workspace, as yoinked with Zap.
Thanks. I think I've made some progress, could you see what the Simtec outputs for the following:
Code: Select all
FOR A%=&10000 TO &10200:!A%=0:NEXT
SWI "IDEFS_Enumerate",-1 TO A%
PRINT ~A%
SWI "IDEFS_Enquire",A%,&10000
*MEMORY B 10000+200
SWI "IDEFS_Enumerate",A% TO A%
PRINT ~A%
IF A%>0 THEN SWI "IDEFS_Enquire",A%,&10000
That hopefully performs an IDENTIFY on the drive and the last SWI should either not be called or should error

Just to be clear - you replied to a request for the APDL workspace, but this is a question about the Simtec interface?

forums.jaspp.org.uk

Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback

Re: Partition Manager feedback