Zorro III Bus Specifications wanted - Page 6

tnt23 · 16 February 2010, 15:28

Quote:

Originally Posted by alexh

http://amigadev.elowar.com/read/ADCD.../node028B.html

Cool, I wish I've had this link in the first place

chiark · 16 February 2010, 16:00

That is fantastic stuff

! Congrats tnt23, great to see this working!

tnt23 · 16 February 2010, 21:44

@chiark, nice to see ya! Did you manage to hook your emulator to your 2000?

I've got another shot of Early Boot w/proto board, can't help but post it too:

85 comes from 0x55 which is just some cute hex number. Using Commodore's manufacturing number isn't sane, something like 0xBABE, or 0xDEAD, or 0xBEEF will be more fun

alexh · 16 February 2010, 22:53

I am not familiar with the numbering scheme but is it necessary to choose a valid number? One which is not already taken, to prevent conflict?

I remember reading somewhere on the net a list of all board id's (perhaps in the source code to something like scout)

Shadowfire · 17 February 2010, 01:26

IIRC, the product/device is used by device drivers (using the expansion.library) to find out where in memory the system has mapped it's board. There exists a small, but nonzero chance that assigning a number nilly-willy might conflict with a real product installed in someone's machine, somewhere. That would be unfortunate, since you would likely have improper drivers bound to the hardware.

tnt23 · 17 February 2010, 07:42

Quote:

Originally Posted by alexh

I am not familiar with the numbering scheme but is it necessary to choose a valid number? One which is not already taken, to prevent conflict?

I remember reading somewhere on the net a list of all board id's (perhaps in the source code to something like scout)

The zorro.ids file from linux sources lists some known ids:

Code:

#
#       List of Zorro IDs
#
#       Maintained by Geert Uytterhoeven <zorro@linux-m68k.org>
#       If you have any new entries, please send them to the maintainer.
#

# Manufacturers and Products. Please keep sorted.

# Syntax:
# manufacturer  manufacturer_name
#       product  product_name                           <-- single tab

00d3  Pacific Peripherals
        0000  SE 2000 A500 [HD Controller]
        0a00  [SCSI Host Adapter]
00dd  Kupke
        0000  Golem RAM Box 2MB [RAM Expansion]
0100  MacroSystems USA
# The Stormbringer is actually made by Memphis
        0000  Stormbringer [Accelerator]
        1300  Warp Engine [Accelerator, SCSI Host Adapter and RAM Expansion]
0200  3-State
        0200  Megamix 2000 [RAM Expansion]
0201  Commodore Braunschweig
        0100  A2088 XT/A2286 AT [ISA Bus Bridge]
        0200  A2286 AT [ISA Bus Bridge]
        5400  A4091 [SCSI Host Adapter]
        6700  A2386-SX [ISA Bus Bridge]
0202  Commodore West Chester
        0100  A2090/A2090A [SCSI Host Adapter]
...

The list misses E3B and DENEB. I was sure E3B has had manufacturer code of 0x0e3b.

tnt23 · 17 February 2010, 07:45

Quote:

Originally Posted by Shadowfire

IIRC, the product/device is used by device drivers (using the expansion.library) to find out where in memory the system has mapped it's board. There exists a small, but nonzero chance that assigning a number nilly-willy might conflict with a real product installed in someone's machine, somewhere. That would be unfortunate, since you would likely have improper drivers bound to the hardware.

I agree. I will try using numbers not known to Linux (zorro.ids), I think this file is being kept up to date. By Linux people and for Linux people of course, so it may well miss a bunch of devices never known or used outside AmigaOS.

alexh · 17 February 2010, 11:37

Quote:

Originally Posted by tnt23

I was sure E3B has had manufacturer code of 0x0e3b.

They are

Minuous · 18 February 2010, 00:44

>I remember reading somewhere on the net a list of all board id's (perhaps in the source code to something like scout)

http://amigan.1emu.net/reg/manuf.html

Source code for Report+ has them too.

tnt23 · 18 February 2010, 16:37

Are there any tools except SysInfo to list installed Zorro cards? Seems like SysInfo is unable to show correctly Z3 sizes of over 16M.

alexh · 18 February 2010, 16:57

http://aminet.net/package/util/moni/Scout_os3

http://aminet.net/package/util/misc/ReportPlus

tnt23 · 18 February 2010, 18:42

Quote:

Originally Posted by alexh

http://aminet.net/package/util/moni/Scout_os3

http://aminet.net/package/util/misc/ReportPlus

Scout works, but doesn't tell the card size, and complains about some identify.library missing.

ReportPlus requires OS3.9, and I've got 3.1.

alexh · 18 February 2010, 18:46

http://aminet.net/package/util/misc/ReportPlus4_71

Zack · 18 February 2010, 20:59

http://www.shredzone.de/projects/identify/

http://aminet.net/package/util/libs/IdentifyUsr
http://aminet.net/package/util/libs/IdentifyDev

wawa · 18 February 2010, 23:28

im not sure, but isnt it like, that identify.library just contains data related to identified hardware. so in this case scout will not return anything anyway since the information about the card in question is not yet stored in the database?

tnt23 · 19 February 2010, 07:46

Quote:

Originally Posted by wawa

im not sure, but isnt it like, that identify.library just contains data related to identified hardware. so in this case scout will not return anything anyway since the information about the card in question is not yet stored in the database?

That is quite possible. Maybe the said library is used to translate those pesky ID numbers to human readable format.
However, the SysInfo reports the card size up to 16Mb correctly, by just reading the appropriate AUTOCONFIG register(s).

tnt23 · 19 February 2010, 07:51

Quote:

Originally Posted by Zack

http://www.shredzone.de/projects/identify/

http://aminet.net/package/util/libs/IdentifyUsr
http://aminet.net/package/util/libs/IdentifyDev

Thanks! This looks promising:

Code:

Four example Shell tools are also included:

ListExp     Analyses your system, searches for expansion boards and
            optionally, shows what Commodities are available. This is
            an easy way to describe your system for bug reports etc.

mboehmer_e3b · 23 February 2010, 20:22

Quote:

Originally Posted by tnt23

The list misses E3B and DENEB. I was sure E3B has had manufacturer code of 0x0e3b.

0x0E3B is officially assign to E3B. Hands off! :-)

mboehmer_e3b · 23 February 2010, 20:31

Quote:

Originally Posted by alexh

I never understood why Michael Boemer did not include a RAM interface on Deneb!? I'm sure it was discussed several times.

Simple answer: pincount of the FPGA. It's fully loaded, as DENEB can do Zorro II/III autosensing and operation. 32bit interfacing to the USB host controller needs also quite some pins, as well as the DMA interface.
The FPGA fabric has plenty of resources left - I even compiled in a logic analyzer once to debug Zorro interface signals "remotely" in customer's computers...

Michael

alexh · 23 February 2010, 20:38

Quote:

Originally Posted by mboehmer_e3b

32bit interfacing to the USB host controller needs also quite some pins

I take it there was no 16-bit or 8-bit mode interface mode for the USB host controller? There sometimes are. I guess non that were practical or you would have used it in that mode.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Amiga 3000 Zorro Bus Problems	Ze_ro	support.Hardware	18	30 April 2021 06:27
Wanted - A4000 Tower case and Zorro bus board	AmigaFun	MarketPlace	8	03 June 2011 13:03
Zorro Bus Termination...	chiark	support.Hardware	3	15 October 2010 09:50
PCMCIA card reader in Zorro bus	protek	Hardware mods	17	06 November 2009 00:46
Zorro II Card - Zorro III Slot ?	THX1138	support.Hardware	4	03 May 2003 11:03

16 February 2010, 16:00	#102
chiark Needs a life Join Date: Jan 2008 Location: England Posts: 1,707	That is fantastic stuff ! Congrats tnt23, great to see this working!

16 February 2010, 21:44	#103
tnt23 Registered User Join Date: Feb 2008 Location: Saint-Petersburg / Russia Posts: 324	@chiark, nice to see ya! Did you manage to hook your emulator to your 2000? I've got another shot of Early Boot w/proto board, can't help but post it too: 85 comes from 0x55 which is just some cute hex number. Using Commodore's manufacturing number isn't sane, something like 0xBABE, or 0xDEAD, or 0xBEEF will be more fun

16 February 2010, 22:53	#104
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,461	I am not familiar with the numbering scheme but is it necessary to choose a valid number? One which is not already taken, to prevent conflict? I remember reading somewhere on the net a list of all board id's (perhaps in the source code to something like scout)

17 February 2010, 01:26	#105
Shadowfire Registered User Join Date: Aug 2001 Location: Connecticut USA Posts: 617	IIRC, the product/device is used by device drivers (using the expansion.library) to find out where in memory the system has mapped it's board. There exists a small, but nonzero chance that assigning a number nilly-willy might conflict with a real product installed in someone's machine, somewhere. That would be unfortunate, since you would likely have improper drivers bound to the hardware.

18 February 2010, 00:44	#109
Minuous Coder/webmaster/gamer Join Date: Oct 2001 Location: Canberra/Australia Posts: 2,673	>I remember reading somewhere on the net a list of all board id's (perhaps in the source code to something like scout) http://amigan.1emu.net/reg/manuf.html Source code for Report+ has them too.

18 February 2010, 16:37	#110
tnt23 Registered User Join Date: Feb 2008 Location: Saint-Petersburg / Russia Posts: 324	Are there any tools except SysInfo to list installed Zorro cards? Seems like SysInfo is unable to show correctly Z3 sizes of over 16M.

18 February 2010, 16:57	#111
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,461	http://aminet.net/package/util/moni/Scout_os3 http://aminet.net/package/util/misc/ReportPlus

18 February 2010, 18:46	#113
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,461	http://aminet.net/package/util/misc/ReportPlus4_71

18 February 2010, 20:59	#114
Zack Registered User Join Date: Feb 2004 Location: Valby, Denmark Age: 48 Posts: 90	http://www.shredzone.de/projects/identify/ http://aminet.net/package/util/libs/IdentifyUsr http://aminet.net/package/util/libs/IdentifyDev

18 February 2010, 23:28	#115
wawa Registered User Join Date: Aug 2007 Location: berlin/germany Posts: 1,054	im not sure, but isnt it like, that identify.library just contains data related to identified hardware. so in this case scout will not return anything anyway since the information about the card in question is not yet stored in the database?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)