amigaspirit.hu - pegasos.hu Wiki - Felhasználó közreműködései [hu]

TF1260 firmware upgrade using a Raspberry Pi

2022-01-07T22:58:34Z

Chain-Q: typofix (thx Alb42!)

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to Header pin 7
* TDI to Header pin 15
* TDO to Header pin 13
* TCK to Header pin 11
* GND to Header pin 9

[[Kép:jtag-rpi3.jpg|thumb|none|400px|JTAG wiring, Raspberry Pi 3 side]]
[[Kép:jtag-tf1260.jpg|thumb|none|400px|JTAG wiring, TF1260 side]]

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

[[Kép:jtag-tfpress.jpg|thumb|none|320px|Pressing gently on the connectors for better contact]]

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matrix_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matrix_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

Fájl:Jtag-tfpress.jpg

2022-01-05T14:01:21Z

Chain-Q: JTAG wiring for TF1260 CPLD flashing, Pressing gently to the right during flashing

JTAG wiring for TF1260 CPLD flashing, Pressing gently to the right during flashing

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T14:00:21Z

Chain-Q: press gently

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to Header pin 7
* TDI to Header pin 15
* TDO to Header pin 13
* TCK to Header pin 11
* GND to Header pin 9

[[Kép:jtag-rpi3.jpg|thumb|none|400px|JTAG wiring, Raspberry Pi 3 side]]
[[Kép:jtag-tf1260.jpg|thumb|none|400px|JTAG wiring, TF1260 side]]

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

[[Kép:jtag-tfpress.jpg|thumb|none|320px|Pressing gently on the connectors for better contact]]

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T13:59:07Z

Chain-Q: smaller

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to Header pin 7
* TDI to Header pin 15
* TDO to Header pin 13
* TCK to Header pin 11
* GND to Header pin 9

[[Kép:jtag-rpi3.jpg|thumb|none|400px|JTAG wiring, Raspberry Pi 3 side]]
[[Kép:jtag-tf1260.jpg|thumb|none|400px|JTAG wiring, TF1260 side]]

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

Fájl:Jtag-tf1260.jpg

2022-01-05T13:58:07Z

Chain-Q: JTAG wiring for TF1260 CPLD flashing, TF1260 side

JTAG wiring for TF1260 CPLD flashing, TF1260 side

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T13:57:13Z

Chain-Q: fix img crap

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to Header pin 7
* TDI to Header pin 15
* TDO to Header pin 13
* TCK to Header pin 11
* GND to Header pin 9

[[Kép:jtag-rpi3.jpg|thumb|none|640px|JTAG wiring, Raspberry Pi 3 side]]
[[Kép:jtag-tf1260.jpg|thumb|none|640px|JTAG wiring, TF1260 side]]

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

Fájl:Jtag-rpi3.jpg

2022-01-05T13:44:49Z

Chain-Q: JTAG wiring for TF1260 CPLD flashing, Raspberry Pi 3 side

JTAG wiring for TF1260 CPLD flashing, Raspberry Pi 3 side

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T13:39:51Z

Chain-Q: flubb flubb

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to Header pin 7
* TDI to Header pin 15
* TDO to Header pin 13
* TCK to Header pin 11
* GND to Header pin 9

[[Kép:jtag-rpi3.jpg|frame|none|JTAG wiring, Raspberry Pi 3 side]]
[[Kép:jtag-tf1260.jpg|frame|none|JTAG wiring, TF1260 side]]

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T13:07:09Z

Chain-Q: wiring

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following list to wire up the TF1260 header to the Raspberry Pi. The numbers in the list are '''physical''' pin numbers. Also refer to the pictures below to see the correct wiring.

* TMS to GPIO 7
* TDI to GPIO 15
* TDO to GPIO 13
* TCK to GPIO 11
* GND to GPIO 9

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T12:28:28Z

Chain-Q: blip blop

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following table to wire up the TF1260 header to the Raspberry Pi. Also refer to the picture below to see the correct wiring.

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring, or the way '''xc3sprog''' bitbangs the GPIO, or other software issue. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T12:26:43Z

Chain-Q: typo

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following table to wire up the TF1260 header to the Raspberry Pi. Also refer to the picture below to see the correct wiring.

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verify time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T12:26:00Z

Chain-Q: reworded the fail-o-matic, added release link.

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

https://www.exxoshost.co.uk/forum/viewtopic.php?f=75&t=4947

Make sure to read and understand what's written there, before proceeding further with this description.

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following table to wire up the TF1260 header to the Raspberry Pi. Also refer to the picture below to see the correct wiring.

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands several times to get the CPLD flashed properly. I can't tell why. Repeat until you get the message '''Success! Verigy time <a number> ms'''. If you get the message '''Mismatch at fuse <a number>:''' then you need to repeat the operation. If you're an expert in '''xc3sprog''' and you know why this happens or how to correct it, post it somewhere (not Facebook) so I can read it and fix this description. :) It could be that it's a weakness in wiring. Soldering a header into the card might work better, I don't know.

Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T11:59:28Z

Chain-Q: added link, tweaks

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered '''OFF''' at this point. Use the following table to wire up the TF1260 header to the Raspberry Pi. Also refer to the picture below to see the correct wiring.

Note that while you do not need to connect 3V3, in fact I advise you not to, '''you absolutely and under all circumstances need to connect GND (Ground)'''. If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands '''TWICE''' to get the CPLD flashed properly. I can't tell why. The second run takes up several seconds, the first one only 1 second, so it was obviously not right. If you're an expert in '''xc3sprog''' and you know why, post it somewhere (not Facebook) so I can read it and fix this description. :) Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

=Other resources=

* Upgrading a Xilinx 9500 series CPLD using xc3sprog. [https://anastas.io/hardware/2020/09/29/xc9500-cpld-raspberry-pi-xc3sprog.html] This also covers using the '''xc3sprog''' Wiring Pi method, which might work on Raspberry Pi 4.

TF1260 firmware upgrade using a Raspberry Pi

2022-01-05T11:48:07Z

Chain-Q: TF1260 fw upgrade, basics

=DISCLAIMER=
This is a description of how I upgraded the firmware in my TerribleFire TF1260 accelerator. It is my own personal experience, and in no way, shape, or form an official or endorsed description by Stephen, or any of the card builders. It worked for me, but it might not work for you, or just as well break, brick, or kill your Amiga, your Raspberry Pi, or your TF1260. It might even cause a terrible fire, and I won't be responsible. In other words: '''DO NOT DO THIS, IF YOU'RE NOT COMFORTABLE ACCEPTING THE RISK. YOU'RE ON YOUR OWN.'''

=Intro=
This description was tested using the December 2021 firmware release by Stephen Leary. His release is available here:

I used my older '''Raspberry Pi 3''', running '''Raspberry OS Buster''', which was "oldstable" at the time of writing this documentation. Your mileage '''WILL''' vary with other combinations. I refer to further documentation where possible.

=Getting and building the tools=
First, you need to get and build the Matrix.io fork of '''xc3sprog'''. This software can program the Xilinx CPLDs on the TF1260, and in particular, this fork can do it via the GPIO pins of the Raspberry Pi.

'''PLEASE NOTE THAT THE xc3sprog VERSION YOU CAN INSTALL VIA APT WON'T WORK FOR THIS PURPOSE'''.

First, install the build requirements:

$ sudo apt-get update
$ sudo apt-get install build-essential libusb-dev libftdi-dev libgpiod-dev wiringpi git cmake

Then, build it:

$ git clone https://github.com/matrix-io/xc3sprog
$ cd xc3sprog
$ mkdir build
$ cd build
$ cmake ..
$ make

This will print a bunch of warnings between the build messages, but just ignore those until the build is finished.

=Wiring things up=
Now, lets wire up the pins for JTAG. I used some pre-made Dupont cables I bought on Amazon [https://www.amazon.de/AZDelivery-Jumper-Arduino-Raspberry-Breadboard/dp/B07K8PVKBP], with male pins on one end, and female plugs on the other end. The TF1260 has a 6 pin JTAG header, but we won't connect 3V3, so we'll use 5 wires.

Make sure your TF1260 and Amiga is powered ''OFF''' at this point. Use the following table to wire up the TF1260 header to the Raspberry Pi. Also refer to the picture below to see the correct wiring.

Note that while you do not need to connect 3V3, you absolutely and under all circumstances need to connect GND (Ground). If you got the wiring right, power the Amiga '''ON'''. The card is immediately ready to be talked through JTAG. Note that you may need to '''GENTLY''' press the side of Dupont cable pins on the TF1260 while communicating with the card, so they make better contact.

While pressing the pins, the execute the following command on the Raspberry Pi:

$ ./xc3sprog -c matrix_creator -j

The result you get should be something like this:

XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
Free software: If you contribute nothing, expect nothing!
Feedback on success/failure/enhancement requests:
http://sourceforge.net/mail/?group_id=170565
Check Sourceforge for updates:
http://sourceforge.net/projects/xc3sprog/develop

JTAG loc.: 0 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8
JTAG loc.: 1 IDCODE: 0x59616093 Desc: XC95288XL Rev: E IR length: 8

The last two lines must show the two CPLDs on the card. Do '''NOT''' proceed further, if you don't get this output.

=Flashing the CPLDs=

Now, download the archive released by Stephen onto your Raspberry Pi, and extract it. You will need two files from it:

tf1260r1_ram_top.jed
tf1260r1_bus_top.jed

NOTE: If you have a card with 6ns CPLD, you might want to use the file '''tf1260r1_ram_top_6ns.jed''' instead of '''tf1260r1_ram_top.jed'''. If you are unsure, ask your builder, or imply use the regular file.

'''IMPORTANT:''' The CPLD at JTAG location 0 (zero), is the '''RAM''' CPLD. The CPLD at JTAG location 1 (one) is the '''BUS''' CPLD. Do not mix the CPLD files up!

You can flash the CPLDs with the following commands. Remember to '''GENTLY''' press on the connector pins on the card! Also remember your Amiga must be '''POWERED ON''' for this to work.

Do the RAM CPLD first:

$ ./xc3sprog -c matric_creator -p 0 -v <path_to_the_tf1260_files>/tf1260r1_ram_top_jed

and the BUS CPLD second:

$ ./xc3sprog -c matric_creator -p 1 -v <path_to_the_tf1260_files>/tf1260r1_bus_top_jed

Note that I had to execute each of these commands '''TWICE''' to get the CPLD flashed properly. I can't tell why. The second run takes up several seconds, the first one only 1 second, so it was obviously not right. If you're an expert in '''xc3sprog''' and you know why, post it somewhere (not Facebook) so I can read it and fix this description. :) Also remember the Amiga will stop working during the flashing operation. This is nothing to be alarmed of, and completely normal.

After both flashing have succeeded, power your Amiga '''OFF'''. Wait a few seconds, then power it '''ON''' again. The machine should boot normally, but with the new firmware.

Have fun with your upgraded TF1260! If you have troubles, well, you're out of luck here. Try to use the official method using a proper JTAG adapter.

Fájl:Uaepart-hdtoolbox-buffersize.png

2021-11-19T10:40:40Z

Chain-Q:

Fájl:Uaepart-hdtoolbox-fs-change.png

2021-11-19T10:39:51Z

Chain-Q:

Fájl:Uaepart-hdtoolbox-fs-select.png

2021-11-19T10:39:15Z

Chain-Q:

Fájl:Uaepart-hdtoolbox-fs-id.png

2021-11-19T10:38:08Z

Chain-Q:

Fájl:Uaepart-hdtoolbox-tooltype.png

2021-11-19T10:27:17Z

Chain-Q: A HDToolBox ToolType-jainak beállítása UAE HardFile-hoz.

A HDToolBox ToolType-jainak beállítása UAE HardFile-hoz.

Kezdőlap

2020-08-04T08:39:06Z

Chain-Q:

Üdvözlünk az [http://amigaspirit.hu amigaspirit.hu] - [http://pegasos.hu pegasos.hu] közös Wiki oldalán!

Ez egy WikiWiki projekt, amelynek célja egy teljes és lehetőség szerint minél pontosabb tartalmú, az [http://amigaspirit.hu amigaspirit.hu] és a [http://pegasos.hu pegasos.hu] témaköreihez kapcsolódó információs tár elkészítése.

== Tartalom ==

'''Klasszikus Amiga hardverek'''

[[Amiga]] - [[PowerUP]] - [[Minimig]] - [[NatAmi]]

'''Újgenerációs hardverek'''

[[AmigaOne]] - [[SAM440EP]] - [[Pegasos]] - [[Efika]]

'''Operációs rendszerek'''

[[AmigaOS]] - [[AmigaOS4]] - [[MorphOS]] - [[AROS]]

'''Cégek'''

[[Commodore]] - [[Amiga Inc]] - [[Hyperion Entertainment]] - [[ACube|ACube Systems]] - [[Genesi]] - [[BPlan|bplan]] - [[Motorola]] - [[Phase5]] - [[Escom|ESCOM]]

'''Személyek'''

[[Jay Miner]] - [[Jeri Ellsworth]] - [[Bill McEwen]]

'''Technológia'''

[[M68K]] - [[PowerPC]] - [[Pre-emptive multitasking]] - [[Exec]] - [[Zorro]] - [[CHRP]] - [[PC]]

'''Kérdések és válaszok'''

[[Faq| Általános Amiga FAQ]] - [[MorphOS PowerUP|MorphOS PowerUP GYIK]]

'''Leírások, Hogyanok'''

[[Amiga programok|AmigaOS programok listája]] - [[MorphOS programok|MorphOS programok listája]] - [[AmigaDOS]] - [[FTPMount|FTP Mount]]

[[ISHAR játékleírás]] - [[ISHAR Végigjátszás]] - [[ISHAR Walkthrough - english]]

[[CD32WB|CD32WB Workbench 3.1 CD32-höz]]

[[MiamiDx hálózati beállítások egyszerűen]] - [[MiamiDx networking simplified|MiamiDx networking simplified (english)]]

'''Események, rendezvények'''

[[Amiga Klub]] - [[AmiCon|AmiCon találkozó]] - [http://www.scenecon.hu SceneCON party] - [http://function.hu Function party] - [[Retro video- és kvarcjáték kiállítás]]

'''Kapcsolat'''

[[Amigaspirit|#amigaspirit IRC csatorna]] - [[Banner|amigaspirit.hu és pegasos.hu bannerek]] - [http://forum.amigaspirit.hu amigaspirit.hu fórum] - [http://forum.pegasos.hu pegasos.hu fórum]

MiamiDx networking simplified

2020-08-03T07:17:37Z

Chain-Q: attempt at better English (probably a fail)

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through exactly. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and the network hardware and the physical connection works, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

This is the English translation of the [[MiamiDx_hálózati_beállítások_egyszerűen|original Hungarian]] I published in 2012. Feel free to copy it to other places or translate it to your language.

MiamiDx networking simplified

2020-08-03T07:15:07Z

Chain-Q: the the the

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through exactly. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

This is the English translation of the [[MiamiDx_hálózati_beállítások_egyszerűen|original Hungarian]] I published in 2012. Feel free to copy it to other places or translate it to your language.

MiamiDx networking simplified

2020-08-03T07:12:43Z

Chain-Q: then then then

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through exactly. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click the ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

This is the English translation of the [[MiamiDx_hálózati_beállítások_egyszerűen|original Hungarian]] I published in 2012. Feel free to copy it to other places or translate it to your language.

MiamiDx networking simplified

2020-08-02T11:03:26Z

Chain-Q: note added about original

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through exactly. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click the ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

This is the English translation of the [[MiamiDx_hálózati_beállítások_egyszerűen|original Hungarian]] I published in 2012. Feel free to copy it to other places or translate it to your language.

MiamiDx networking simplified

2020-08-02T10:55:17Z

Chain-Q: burp

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through exactly. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click the ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

MiamiDx networking simplified

2020-08-02T10:54:22Z

Chain-Q: fix typo

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through as described. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click the ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online''. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

MiamiDx networking simplified

2020-08-02T10:53:45Z

Chain-Q: first translation of the Hungarian MiamiDx setup article

== Introduction ==

This article aims to assist beginners to get their classic Amiga connected to a network. It explains the setup of '''Miami Deluxe''' (abbreviated as '''MiamiDx'''), which is an [[AmiTCP]] compatible TCP/IP networking stack for classic [[AmigaOS]]. It assumes that the Amiga will be connected to an already established networking environment where the various required parameters are known, and/or the hosts are automatically configured via a DHCP server. It also assumes that the hardware is functioning properly, and it's physically attached to the network already. Additionally, it assumes the driver for our networking hardware already obtained, and it is copied into folder ''DEVS:Networks''. All steps described in the article until the [[Amiga]] goes ''Online'' must be followed through as described. Failing to do so might result in a non-working setup.

''Apart from classic [[Amiga]] hardware, this description can be used for the [[WinUAE]] emulator, to connect to the network using '''uaenet.device''' and/or using the [[Commodore A2065]] network card emulation, if the '''bsdsocket.library''' emulation is disabled. It also applies to [[Pegasos]] I/II computers running [[MorphOS]] version 1.4.x and older, but please note the hardware specific settings for various configurations are not discussed.''

== Installation ==

The installer of MiamiDx is available via Aminet. [[MUI]] is required to use the [[GUI]] described in this article.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx main archive]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI archive]

Extract both archives into the same directory, then then execute the Installer script.

If everything went fine, the following window should appear after clicking on the '''MiamiDx''' icon:

[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx main window]]

== Configuring the hardware ==

As a first step, the networking hardware and its device driver must be configured. Click on the ''Hardware'' tab, then click the ''New'' button. In the pop-up window, select ''Ethernet''.
[[Kép:Miami-02-newhardware.PNG|frame|none|Add hardware wizard]]

At this point, a name or identifier must be specified for the networking hardware. This identifier will be used throughout the rest of the configuration process. It's recommended to specify a name which refers to the networking hardware type or model. The name must be entered into the ''Name'' field. If the hardware has a ''MiamiDx'' specific (MNI) driver, it's recommended to use it. In this case, the ''Type'' field must be set to ''MNI driver'', then the driver's file name must be specified. After clicking the ''Find boards...'' button, the networking hardware can be selected in the pop-up window.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|MNI driver settings]]

The hardware and driver functionality can be verified by clicking the ''MNI Parameters... button''. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Verifying the MNI driver settings]]

If the networking hardware has a SANA-II driver, ''SANA-II driver'' must be selected in the same window, and the driver's file name must be specified in the entry field. The functionality of the driver and hardware can be verified by clicking the ''SANA-II Parameters..'' button. In the pop-up window, click ''Query device''. The MAC address of the hardware should appear.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|SANA-II driver settings and verification]]

If everything went as described, click the ''OK''. The newly configured networking hardware should appear in the list. It's possible to add multiple different hardware. A null-modem cable for serial computer-to-computer network it, or in case of an [[Amiga 1200]] or [[Amiga 600]] both the wired and the wireless networking card can be added here. It's possible to edit or delete hardware entries using the buttons below.
[[Kép:Miami-06-hwdone.PNG|frame|none|Finalizing the hardware settings]]

== Configuring the network interface ==

After specifying the hardware, a logical network interface must be created and configured. For this, click the ''New'' button on the ''Interfaces'' tab. Select ''Ethernet'' and ''Internet'' in the pop-up window, then click ''OK''.
[[Kép:Miami-07-newinterface.PNG|frame|none|Adding a new interface]]

One of the previously specified hardware must be selected for this interface. In case of more than one hardware, switching between them is possible, but for the creation of the interface one must be chosen regardless. After choosing the hardware, click ''OK''.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Selection of hardware for the interface]]

Now the interface settings must be defined. This is the most cruical part of the setup process. If the network has a DHCP server, so the devices connected to the network are autoconfigured (most likely these days), all fields should be set from ''static'' to ''DHCP''. Alternatively, it's possible to specify a static IP, a subnet mask, and a gateway IP. It's important that for the default interface, ''GUI Default'' must be enabled. If DHCP is used, after finishing the settings in this window, click ''TCP/IP Settings...'' for DNS (domain name server) auto-configuration. ''(Note: for static DNS settings, please see chapter [[#Advanced settings|Advanced settings]]).''
[[Kép:Miami-09-interfacedef.PNG|frame|none|Network interface definition]]

In the pop-up window, set option ''Get dynamic DNS servers'' from ''ignore'' to ''add''. Ignoring and not changing this setting is the most likely reason when name resolution is not working. No further settings are needed here. To close this window, click ''OK''.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|Network interface definition, continued]]

Clicking ''OK'' again will close the ''Interface definition'' window. In the list, the newly crated interface will appear, which is ready to connect by clicking ''Online''.
[[Kép:Miami-11-interface-done.PNG|frame|none|Finalizing the interface definition]]

If everything went well to this point, and our network is functioning as expected, '''MiamiDx''' loads the network card driver, sends a configuration request to the DHCP server, if it receives a configuration applies it, then puts our interface ''Online''. The functionality of the network can be easily verified from the shell, using the command ''miamiping''. If the interface is successfully configured, the target host will send a valid response, and the Amiga is finally connected to the network! ''(Hint: the execution of the ''miamiping'' command can be stopped by pressing CTRL-C.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Verifying the network connectivity]]

== Saving the configuration ==

The configuration specified in the earlier steps should be saved. '''MiamiDx''' can load and save different configurations easily, but in case of simple setups, it's the easiest to save everything as default. In this case '''MiamiDx''' will start the next time with the configuration just defined. In the ''Settings'' menu, click ''Save as default'' to store the current configuration as default.
[[Kép:Miami-13-savesettings.PNG|frame|none|Saving the configuration]]

== Advanced settings ==

This section details some advanced settings, which makes the everyday use of '''MiamiDx''' more convenient. Remember to save the configuration again after changing these settings.

In case of a well setup system, '''MiamiDx''''s configuration GUI won't be needed on each start. To disable the GUI on start, on the ''GUI'' tab, enable option ''No GUI on startup''. If ''Show icon'' is also disabled, '''MiamiDx''' won't appear as an icon on the Workbench, but its GUI can be opened using a hotkey, also specified here in the ''Hotkey'' field, or through [[Exchange]].
[[Kép:Miami-14-guisettings.PNG|frame|none|User interface settings]]

If '''MiamiDx''' should put our default interface ''Online'' automatically on start, on the ''Events'' tab, enable option ''auto-online'. If the GUI is not fully disabled in the previous step, it's possible to enable automatic hiding after the interface went ''Online'', by setting the drop-down menu to ''Hide GUI'' in the ''Start'' group.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Operations on start and on shutdown]]

Static DNS settings can be added on the ''Database'' tab. Set the central gadget to ''DNS servers'', then ''Add'' your choice of DNS server. The newly added DNS server can be bound to only one interface, or a system-wide setting. If the DHCP auto-configuration process added temporary DNS servers, these will be marked by "X" in the ''Temp.'' column. ''(Hint: for users with deep networking and Unix knowledge, a lot of very advanced settings and fine-tuning possibilities are available in the various fields of the Database tab)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|Static DNS server settings]]

The following is not really a configuration setting, just a trick: it's possible to hide or fully disable the configuration GUI manually, in the ''Project'' menu using the ''Iconify'' or the ''Kill GUI'' options respectively. '''MiamiDx''' will continue to operate in the background, its configuration GUI will be available through its icon, or using the hotkey specified in the ''GUI'' tab, or via [[Exchange]].
[[Kép:Miami-19-killgui.PNG|frame|none|Hiding the user interface manually]]

== End result ==

Now the [[Amiga]] should be connected to the internet, using '''MiamiDx'''. There are many networking applications available, for example it can connect to IRC using AmIRC allowing a nice chat with other Amiga users, or browse the web via IBrowse.
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx and AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx and IBrowse]]

== License ==

This article and the associated images are published by Károly Balogh under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0].

MiamiDx hálózati beállítások egyszerűen

2020-08-02T09:45:49Z

Chain-Q: interfaces

== Bevezető ==

Ez a leírás a '''Miami Deluxe''' (rövidítve '''MiamiDx''') classic [[AmigaOS]]-re készült [[AmiTCP]] kompatibilis TCP/IP hálózati stack egyszerű beállítását ismerteti. A célja hogy kezdőknek segítsen az elindulásban, classic Amigájuk hálózatra kötésében. Feltételezi, hogy az Amigánkat már egy bejáratott hálózati környezetben szeretnénk használni, ahol ismertek a hálózati beállítások és/vagy van DHCP szerver (vagyis a gépek automatikusan kapják meg a szükséges beállításokat), valamint feltételezi, hogy a hardver tökéletesen működik és megfelelően van csatlakoztatva. Arról is győződjünk meg, hogy a hálózati kártyánkhoz szükséges eszközmeghajtót beszereztük és bemásoltuk a ''DEVS:Networks'' könyvtár alá.

''A leírás classic [[Amiga]] hardver mellett használható [[WinUAE]] emulátorhoz is, amennyiben nem a beépített '''bsdsocket.library''' emulációt, hanem az '''uaenet.device''' emulációt és/vagy a [[Commodore A2065]] emulációt használjuk, valamint [[MorphOS]] 1.4.x-et futtató [[Pegasos]] I/II számítógépekhez is. Az egyes konfigurációkhoz tartozó specifikus beállításokra a cikk nem tér ki.''

== Telepítés ==

A MiamiDx telepítője elérhető az Amineten. A cikkben ismertetett [[GUI]] használatához [[MUI]] előtelepítése szükséges.

* [http://aminet.net/package/comm/tcp/MiamiDx10cmain MiamiDx fő archív]
* [http://aminet.net/package/comm/tcp/MiamiDx10c-MUI MiamiDx MUI GUI]

A két telepítendő archívot tömörítsük ki egyetlen közös könyvtárba, majd futtassuk a telepítő scriptet.

Ha mindent jól csináltunk a '''MiamiDx''' ikonra kattintva a következő képernyőt kell hogy lássuk:
[[Kép:Miami-01-mainwindow.PNG|frame|none|MiamiDx üdvözlő képernyő]]

== A hardver konfigurációja ==

Első lépésként meg kell adnunk melyik hardverünket ill. hozzá tartozó eszközmeghajtót szeretnénk használni. Ennek lépései a következők. Kattintsunk a ''Hardware'' fülre, majd nyomjuk meg a ''New'' gombot. A felugró ablakból válasszuk az ''Ethernet''-et.
[[Kép:Miami-02-newhardware.PNG|frame|none|Új hardver hozzáadása varázsló]]

Első körben el kell neveznünk a kártyánkat. A hardvert nem tudjuk létrehozni, amíg nincs egy azonosító neve, amivel később hivatkozhatunk rá. Célszerű a kártya típusára emlékeztető elnevezést adni, amelyet a ''Name'' mezőbe kell írni. Amennyiben a kártyánkhoz a '''MiamiDx''' rendelkezik beépített (ún. MNI) driverrel, érdemes azt használnunk. Ez esetben a ''Type'' legördülő listából válasszuk az ''MNI driver'' típust, adjuk meg a beviteli mezőben a drivert, majd kattintsunk a ''Find boards...'' gombra. A felugró listában jelöljük ki a kívánt hardvert.
[[Kép:Miami-03-mnidriver-01.PNG|frame|none|Az MNI driver beállítása]]

A hardver működését ellenőrizhetjük a ''MNI Parameters...'' gombra kattintással megjelenő ablakban. Ha a ''Query device''-re kattintva megjelenik a hardverünk MAC címe, akkor az eszköz megfelelően működik.
[[Kép:Miami-04-mnidriver-02.PNG|frame|none|Az MNI driver működésének ellenőrzése]]

Amennyiben a hálózati kártyánkhoz csak SANA-II driverrel rendelkezünk, ugyanebben az ablakban válasszuk a ''SANA-II driver'' lehetőséget és adjuk meg a beviteli mezőben a drivert. A hardver működését itt is a ''SANA-II Parameters...''-re megjelenő ablakban, a ''Query device''-re kattintva ellenőrizhetjük.
[[Kép:Miami-05-sanaiidriver.PNG|frame|none|A SANA-II driver beállítása és ellenőrzése]]

Amennyiben minden rendben működik, az ''OK'' gombra kattintva visszakerülünk a hardver listába, ahol immár megjelent az újonnan létrehozott hardverünk. A '''MiamiDx'''-ben természetesen több hardvert is létrehozhatunk ilyen módon. Pl. ha még soros modemet vagy null-modem kábelt használunk, esetleg [[Amiga 1200]] vagy [[Amiga 600]] esetén használunk WiFi és vezetékes hálózati kártyát is. A korábban létrehozott hardvereket az alul található gombokkal törölhetjük, szerkeszthetjük.
[[Kép:Miami-06-hwdone.PNG|frame|none|A hardver beállítások véglegesítése]]

== A hálózati interfész konfigurációja ==

Ha már van hardverünk, rátérhetünk a hálózati interfész beállítására. Természetesen először itt is egy új interfészt kell létrehoznunk. Ezt az ''Interfaces'' fülön, a ''New'' gombra kattintva tehetjük meg. A felugró ablakból válasszuk az ''Ethernet'' és az ''Internet'' lehetőségeket, majd kattintsunk az ''OK'' gombra.
[[Kép:Miami-07-newinterface.PNG|frame|none|Új interfész hozzáadása]]

Ezután ki kell választanunk a korábban létrehozott hardvereink közül, hogy ez az interfész melyik hardveren akar kommunikálni. Több hardver esetén a későbbiekben válthatunk közöttük, de most ki kell választani egyet. Majd nyomjunk az ''OK'' gombra.
[[Kép:Miami-08-newinterface-hw.PNG|frame|none|Hardver kiválasztása az interfészhez]]

És ezzel végre eljutottunk a lényegi beállításokhoz. Itt megadhatjuk, hogy az interfész milyen beállításokkal csatlakozzon a hálózatra. Amennyiben DHCP szerverrel rendelkező routerünk van, vagyis a gépeink automatikusan kapják meg a hálózati konfigurációjukat induláskor (manapság ez szinte mindig így van), valamennyi mező típusát állítsuk ''static''-ról ''DHCP''-re. Ez a legegyszerűbb. Ugyanitt, ha ismerjük a beállításokat vagy kézi beállításokat szeretnénk, megadhatunk statikus IP-t, alhálózati maszkot és átjárót is. Nagyon fontos, hogy az alapértelmezett interfészünkhöz jelöljük be a ''GUI Default''-ot! Ha itt végeztünk és DHCP-t használunk, kattintsunk a ''TCP/IP settings...'' gombra, ahol további beállításokat fogunk elvégezni. ''(Megjegyzés: amennyiben statikus beállításokat használunk, lásd a [[#További beállítások|További beállítások]] fejezetet a DNS szerver beállításához.)''
[[Kép:Miami-09-interfacedef.PNG|frame|none|A hálózati interfész beállításai]]

A felugró ablakban állítsuk a ''Get dynamic DNS servers'' opciót ''ignore''-ról ''add''-ra. Ezt nagyon sokan elmulasztják, aminek következtében később a névfeloldás nem működik. Az itt található opciók közül mást általában nem kell átállítani. A kilépéshez kattintsunk az ''OK'' gombra.
[[Kép:Miami-10-interface-tcpip.PNG|frame|none|További interfész beállítások]]

Ezután az ''OK'' gombbal zárjuk be az interfész definiáló ablakot is. A listában megjelenik az újonnan létrehozott interfészünk amely csak arra vár, hogy végre ''Online''-ba helyezzük.
[[Kép:Miami-11-interface-done.PNG|frame|none|Az interfész beállítások véglegesítése]]

Amennyiben mindent jól csináltunk, és a hálózatunk is jól működik, a '''MiamiDx''' betölti a hálózati kártya driverét, elküldi a DHCP szervernek az IP kéréseket, ha kapott IP-ket alkalmazza azokat, majd ''Online''-ba helyezi az interfészünk. Hogy a hálózat valóban megfelelően működik-e a legegyszerűbben pl. shell-ből a ''miamiping'' paranccsal tudjuk ellenőrizni. Ha kapunk választ, az interfészünket sikeresen bekonfiguráltuk, az amigánk végre fent van a neten! ''(Tipp: a miamiping parancs végrehajtását a CTRL-C billentyűkombinációval állíthatjuk le.)''
[[Kép:Miami-12-interface-online.PNG|frame|none|Az interfész működésének ellenőrzése]]

== A konfiguráció elmentése ==

A korábbi lépésekben beállított konfigurációt el kell menteni. A '''MiamiDx''' képes különböző eltárolt konfigurációk betöltésére és mentésére, de ha nincsenek extra igényeink legegyszerűbb mindent alapértelmezettként elmenteni. Ez esetben a '''MiamiDx''' következő indításkor a most beállított konfigurációval fog indulni. Ezt a ''Settings'' menüben, a ''Save as default''-ra kattintva tehetjük meg.
[[Kép:Miami-13-savesettings.PNG|frame|none|A konfigurációs beállítások mentése]]

== További beállítások ==

Ebben a szekcióban néhány olyan beállítást ismertetünk, amely kényelmesebbé teszi a '''MiamiDx''' mindennapi használatát. Természetesen ezen opciók beállítása esetén se felejtsük el a konfigurációt menteni.

Amennyiben a '''MiamiDx'''-et automatikusan szeretnénk elindítani a gépünk indulásakor, de nem szeretnénk a GUI-jával szembesülni minden alkalommal, a ''GUI'' fülön kapcsoljuk be a ''No GUI on startup'' opciót. Amennyiben az ikonokat is kikapcsoljuk, a '''MiamiDx''' vagy a szintén itt beállítható gyorsbillentyűvel, vagy az [[Exchange]]-en át lesz elérhető.
[[Kép:Miami-14-guisettings.PNG|frame|none|A felhasználói felület beállításai]]

Amennyiben azt szeretnénk, hogy a '''MiamiDx''' automatikusan helyezze ''Online''-ba az alapértelmezett interfészünk, az ''Events'' fülön kapcsoljuk be az ''auto-online'' opciót. Ha esetleg az előző fülön nem kapcsoltuk ki a GUI-t teljesen, itt beállíthatjuk, hogy az interfész ''Online''-ba kerülése után automatikusan elrejtésre kerüljön.
[[Kép:Miami-15-eventssettings.PNG|frame|none|Műveletek beállítása induláskor és leálláskor]]

Amennyiben kézi DNS beállításokat szeretnénk, azt a ''Database'' fülön, a középső léptető gadgetet ''DNS servers''-re állítva tehetjük meg. Itt tetszőleges - akár interfésztől függően - statikus DNS beállításokat végezhetünk el. Amennyiben automatikusan hozzáadott (pl. DHCP szerver által) DNS szervereink vannak, azokat a ''Temp.'' oszlopban lévő X jelzi. ''(Tipp: Rutinosabbak, Unixot ill. hálózatot jól ismerők ugyanitt a Database fül egyéb szekcióiban sok egyéb, erősen haladóknak szóló, igen fejlett beállítási lehetőséget is találhatnak.)''
[[Kép:Miami-16-dnssettings.PNG|frame|none|A DNS szerverek beállításai]]

Ez nem igazán konfigurációs beállítás, inkább csak trükk: a grafikus felületet kézzel is elrejthetjük vagy teljesen kikapcsolhatjuk, a ''Project'' menüben lévő ''Iconify'' illetve ''Kill GUI'' opciókkal. A '''MiamiDx''' ez esetben a háttérben működik tovább, a GUI-ja az ikonján át, a ''GUI'' fülön beállított gyorsbillentyűvel vagy az [[Exchange]]-en át lesz elérhető.
[[Kép:Miami-19-killgui.PNG|frame|none|A felhasználói felület elrejtése kézzel]]

== Végeredmény ==

Ha mindent jól csináltunk, mostantól a classic [[Amiga|Amigánkon]] is netezhetünk, pl. IRC-zhetünk az [[Amigaspirit|#amigaspirit]] csatornán, vagy böngészhetjük az [http://amigaspirit.hu amigaspirit.hu]-t. :)
[[Kép:Miami-17-amirc.PNG|frame|none|MiamiDx és AmIRC]]
[[Kép:Miami-18-ibrowse.PNG|frame|none|MiamiDx és IBrowse]]

Setting up Lazarus IDE for Amiga Crosscompiling

2019-01-30T14:09:22Z

Chain-Q: added UAE shot

This page provides a brief summary of how to setup the Free Pascal Amiga crosscompiler to be used with Lazarus IDE from macOS, Linux, or Windows. It primarily applies to classic Amiga, but can be used with all Amiga-like systems with minor adaptations and changes.

This article expect that you have already set up Free Pascal Compiler and Lazarus IDE on the host system, and it's functioning perfectly, it can build native binaries for the host. It also assumes that the Amiga crosscompiler archives are is obtained (binary builds are available here) including the required GNU as/ld and/or vlink and vasm binaries, capable of running on the host system, producing binaries for the target system, in this case classic Amiga.

As a first step, make sure, that in the menu ''Tools -> Options...'' the ''Compiler Executable (e.g. fpc)'' option points to the '''fpc''' compiler frontend (e.g. '''/usr/local/bin/fpc'''), and '''NOT''' to a native compiler directly (e.g. ppc386, or ppcx64).

[[Image:Lazarus-amiga-setup-01.png|640px|Compiler frontend setup]]

If this is done, make a new Lazarus project for your Amiga application. The rest of the options will be applied to project specific options.

Go to the ''Project Options'' window, available under the menu ''Project -> Project Options...'' and apply the following settings. First makes sure the Lazarus passes the right CPU target and OS target to the compiler. This is possible under the ''Compiler Options > Config and Target'' tab. For classic Amiga target, set these to '''Amiga''' and '''m68k''' respectively. Other Amiga-like systems use their respective combinations.

[[Image:Lazarus-amiga-setup-02.png|640px|Compiler target setup]]

Then, under the tab ''Compiler Options > Custom Options'', add the following options to the ''Custom Options'' field:

[[Image:Lazarus-amiga-setup-03.png|800px|Compiler custom options]]

* '''-Cp''' option can be used to specify the target m68k CPU type. Note that you will need the runtime library units compiled with the same options.
* '''-Cf''' option is optional, can be used to specify the target m68k FPU type. Note that you will need the runtime library units to be compiled with the same options. By default, FPC compiles without utilizing FPU instructions.
* '''-XV''' enables linking with vlink. Omit this option if you want to use GNU LD.
* '''-Avasm''' enables assembling with vasm. Omit this option if you want to use GNU AS.
* '''-FD''' option should point to the directory, where GNU as/ld or vasm/vlink for Amiga can be found.
* '''-Xp''' option should point to the directory, where the '''ppcross68k''' cross-compiler binary resides.
* '''-Fu''' option should point to the directory, where all the pre-compiled RTL units reside.

Any additional FPC option can be applied here on demand.

And finally, Lazarus enables use of the '''lineinfo''' unit for new projects by default. This is currently not available for classic Amiga, therefore must be disabled, because it would cause build errors. Other Amiga-like systems can skip this step. This can be done under ''Compiler Options -> Debugging'' by disabling the option ''Display line numbers in run-time error backtraces (-gl)''.

[[Image:Lazarus-amiga-setup-04.png|640px|Disabling unwanted option]]

If you have done everything correctly Clicking ''Show Options'' in the bottom of the ''Project Options'' window should show something like this. This window shows the invoked compiler binary and all the options Lazarus will pass to it.

[[Image:Lazarus-amiga-compiler-options.png|640px|Showing compiler options]]

Note: while setting up this option and closing the Project Options window, the following requester might appear. This is caused by a minor issue in Lazarus, and '''it's safe to ignore''', if the settings are otherwise correct.

[[Image:Lazarus-amiga-setup-error-ignore.png|640px|Error to ignore]]

If you have done everything correctly, invoking the menu ''Run -> Build'' will result a successful build for classic Amiga, or your chosen target system.

[[Image:Lazarus-amiga-success.png|640px|Amiga Build Success]]

And the resulting binary runs happily in UAE.

[[Image:Lazarus-amiga-success-02.png|640px|Amiga Build Success Tested]]

Happy compiling!

Fájl:Lazarus-amiga-success-02.png

2019-01-30T14:07:09Z

Chain-Q:

Setting up Lazarus IDE for Amiga Crosscompiling

2019-01-30T13:52:29Z

Chain-Q: linking -> assembling

Setting up Lazarus IDE for Amiga Crosscompiling

2019-01-30T13:45:32Z

Chain-Q: added pics

This page provides a brief summary of how to setup the Free Pascal Amiga crosscompiler to be used with Lazarus IDE from macOS, Linux, or Windows. It primarily applies to classic Amiga, but can be used with all Amiga-like systems with minor adaptations and changes.

This article expect that you have already set up Free Pascal Compiler and Lazarus IDE on the host system, and it's functioning perfectly, it can build native binaries for the host. It also assumes that the Amiga crosscompiler archives are is obtained (binary builds are available here) including the required GNU as/ld and/or vlink and vasm binaries, capable of running on the host system, producing binaries for the target system, in this case classic Amiga.

As a first step, make sure, that in the menu ''Tools -> Options...'' the ''Compiler Executable (e.g. fpc)'' option points to the '''fpc''' compiler frontend (e.g. '''/usr/local/bin/fpc'''), and '''NOT''' to a native compiler directly (e.g. ppc386, or ppcx64).

[[Image:Lazarus-amiga-setup-01.png|640px|Compiler frontend setup]]

If this is done, make a new Lazarus project for your Amiga application. The rest of the options will be applied to project specific options.

Go to the ''Project Options'' window, available under the menu ''Project -> Project Options...'' and apply the following settings. First makes sure the Lazarus passes the right CPU target and OS target to the compiler. This is possible under the ''Compiler Options > Config and Target'' tab. For classic Amiga target, set these to '''Amiga''' and '''m68k''' respectively. Other Amiga-like systems use their respective combinations.

[[Image:Lazarus-amiga-setup-02.png|640px|Compiler target setup]]

Then, under the tab ''Compiler Options > Custom Options'', add the following options to the ''Custom Options'' field:

[[Image:Lazarus-amiga-setup-03.png|800px|Compiler custom options]]

* '''-Cp''' option can be used to specify the target m68k CPU type. Note that you will need the runtime library units compiled with the same options.
* '''-Cf''' option is optional, can be used to specify the target m68k FPU type. Note that you will need the runtime library units to be compiled with the same options. By default, FPC compiles without utilizing FPU instructions.
* '''-XV''' enables linking with vlink. Omit this option if you want to use GNU LD.
* '''-Avasm''' enables linking with vasm. Omit this option if you want to use GNU AS.
* '''-FD''' option should point to the directory, where GNU as/ld or vasm/vlink for Amiga can be found.
* '''-Xp''' option should point to the directory, where the '''ppcross68k''' cross-compiler binary resides.
* '''-Fu''' option should point to the directory, where all the pre-compiled RTL units reside.

Any additional FPC option can be applied here on demand.

And finally, Lazarus enables use of the '''lineinfo''' unit for new projects by default. This is currently not available for classic Amiga, therefore must be disabled, because it would cause build errors. Other Amiga-like systems can skip this step. This can be done under ''Compiler Options -> Debugging'' by disabling the option ''Display line numbers in run-time error backtraces (-gl)''.

[[Image:Lazarus-amiga-setup-04.png|640px|Disabling unwanted option]]

If you have done everything correctly Clicking ''Show Options'' in the bottom of the ''Project Options'' window should show something like this. This window shows the invoked compiler binary and all the options Lazarus will pass to it.

[[Image:Lazarus-amiga-compiler-options.png|640px|Showing compiler options]]

Note: while setting up this option and closing the Project Options window, the following requester might appear. This is caused by a minor issue in Lazarus, and '''it's safe to ignore''', if the settings are otherwise correct.

[[Image:Lazarus-amiga-setup-error-ignore.png|640px|Error to ignore]]

If you have done everything correctly, invoking the menu ''Run -> Build'' will result a successful build for classic Amiga, or your chosen target system.

[[Image:Lazarus-amiga-success.png|640px|Amiga Build Success]]

Fájl:Lazarus-amiga-setup-error-ignore.png

2019-01-30T13:15:35Z

Chain-Q:

Fájl:Lazarus-amiga-success.png

2019-01-30T13:14:54Z

Chain-Q:

Fájl:Lazarus-amiga-compiler-options.png

2019-01-30T13:13:08Z

Chain-Q:

Fájl:Lazarus-amiga-setup-04.png

2019-01-30T13:11:47Z

Chain-Q:

Fájl:Lazarus-amiga-setup-03.png

2019-01-30T13:10:15Z

Chain-Q:

Fájl:Lazarus-amiga-setup-02.png

2019-01-30T13:06:31Z

Chain-Q:

Fájl:Lazarus-amiga-setup-01.png

2019-01-30T13:02:31Z

Chain-Q:

Setting up Lazarus IDE for Amiga Crosscompiling

2019-01-30T12:49:48Z

Chain-Q: initial version

This page provides a brief summary of how to setup the Free Pascal Amiga crosscompiler to be used with Lazarus IDE from macOS, Linux, or Windows. It primarily applies to classic Amiga, but can be used with all Amiga-like systems with minor adaptations and changes.

This article expect that you have already set up Free Pascal Compiler and Lazarus IDE on the host system, and it's functioning perfectly, it can build native binaries for the host. It also assumes that the Amiga crosscompiler archives are is obtained (binary builds are available here) including the required GNU as/ld and/or vlink and vasm binaries, capable of running on the host system, producing binaries for the target system, in this case classic Amiga.

As a first step, make sure, that in the menu ''Tools -> Options...'' the ''Compiler Executable (e.g. fpc)'' option points to the '''fpc''' compiler frontend (e.g. '''/usr/local/bin/fpc'''), and '''NOT''' to a native compiler directly (e.g. ppc386, or ppcx64).

If this is done, make a new Lazarus project for your Amiga application. The rest of the options will be applied to project specific options.

Go to the ''Project Options'' window, available under the menu ''Project -> Project Options...'' and apply the following settings. First makes sure the Lazarus passes the right CPU target and OS target to the compiler. This is possible under the ''Compiler Options > Config and Target'' tab. For classic Amiga target, set these to '''Amiga''' and '''m68k''' respectively. Other Amiga-like systems use their respective combinations.

Second, go to the tab ''Compiler Options > Custom Options'', and add the following options to the ''Custom Options'' field:

* '''-Cp''' option can be used to specify the target m68k CPU type. Note that you will need the runtime library units compiled with the same options.
* '''-Cf''' option is optional, can be used to specify the target m68k FPU type. Note that you will need the runtime library units to be compiled with the same options. By default, FPC compiles without utilizing FPU instructions.
* '''-XV''' enables linking with vlink. Omit this option if you want to use GNU LD.
* '''-Avasm''' enables linking with vasm. Omit this option if you want to use GNU AS.
* '''-FD''' option should point to the directory, where GNU as/ld or vasm/vlink for Amiga can be found.
* '''-Xp''' option should point to the directory, where the '''ppcross68k''' cross-compiler binary resides.
* '''-Fu''' option should point to the directory, where all the pre-compiled RTL units reside.

Any other FPC option can be applied here on demand.

Third, Lazarus enables use of the '''lineinfo''' unit for new projects by default. This is currently not available for classic Amiga, therefore must be disabled, because it would cause build errors. Other Amiga-like systems can skip this step. This can be done under ''Compiler Options -> Debugging'' by disabling the option ''Display line numbers in run-time error backtraces (-gl)''.

If you have done everything correctly Clicking ''Show Options'' in the bottom of the ''Project Options'' window should show something like this. This window shows the invoked compiler binary and all the options Lazarus will pass to it.

Note: while setting up this option and closing the Project Options window, the following requester might appear. This is caused by a minor issue in Lazarus, and '''it's safe to ignore''', if the settings are otherwise correct.

If you have done everything correctly, invoking the menu ''Run -> Build'' will result a successful build for classic Amiga, or your chosen target system.

RDB

2017-12-06T19:55:41Z

Chain-Q: fix fix, lovely fix.

Az RDB vagy '''Rigid Disk Block''' az [[AmigaOS]]-t és [[MorphOS]]-t futtató számítógépek natív merevlemez és [[partíció]] formátuma. Feladata hasonló a [[PC]]-k [[MBR]]-jéhez (vagy újabb gépeken a [[GPT]]-hez), de annál bővebb funkcionalitással bír.

Az RDB támogatása először az [[AmigaOS]] ([[Kickstart]]) 1.2-s verziójában jelent meg. [[Kickstart]] 1.3 óta az RDB formátumú háttértárak bootolhatók. Támogatja tetszőleges számú [[partíció]] létrehozását, továbbá valamennyi [[partíció]]nál beállítható, hogy [[boot]]olható vagy sem, illetve hogy a rendszer induláskor automatikusan [[mount]]olja-e vagy sem. Ha több [[boot]]olható partíciónk van, 7 és -7 között prioritásokat adhatunk a [[partíció]]knak, ezzel meghatározva melyik [[partíció]]ról szeretnénk elsődlegesen [[boot]]olni. Ez igen hasznos, ha több merevlemezünk van, vagy gyakran helyezünk ideiglenesen külső merevlemezeket a gépbe.

Érdekesség, hogy a rendszer támogatja [[filerendszer]]-[[handler]]ek elhelyezését az RDB-be. Ez igen egyszerűvé teszi a különböző [[filerendszer]]ek cseréjét, valamint lehetővé teszi hogy az ezt támogató [[operációs rendszer]] olyan [[filerendszer]]ekkel is mindenféle konfigurálás nélkül megbirkózzon, amelyekkel korábban nem találkozott, hiszen az ismeretlen típusú [[partíció]]hoz tartozó [[driver]] a szükséges paramétereivel együtt megtalálható az RDB-ben.

Ezt a funkcionalitást a [[Commodore]] a direkt merevlemezekhez fejlesztett '''FastFileSystem''' ([[FFS]]) támogatásának megkönnyítéséhez építette be, mivel a korai verziókban az [[FFS]] fájlrendszer kezelését a Kickstart nem tartalmazta. [[Kickstart]] 2.0 óta ugyan az [[FFS]] a ROM része, de a lehetőség később több külsős fejlesztők által készített fájlrendszer elterjedését is lehetővé tette, mint amilyen az [[SFS]] vagy a [[PFS]].

Az RDB-t az [[AmigaOS]]-en és a [[MorphOS]]-en kívül a [[Linux]] valamint a különféle [[BSD]] variánsok is támogatják. Szintén támogatja használatát az [[AmigaOne]] és a [[Pegasos]] gépek [[firmware]]-je.

Merevlemez partícionálása egyszerűen

2017-12-06T19:42:44Z

Chain-Q: wipwipwip

== Bevezető ==

{|
|-
|[[Fájl:Vigyazat.png|96px]]
| '''FIGYELEM! Az ebben a szócikkben bemutatott eljárások nem megfelelő használata adatvesztéshez vezethet! Csak olyan háttértáron kísérletezzünk, amelyről előtte biztonsági mentést készítettünk, vagy biztosak vagyunk benne, hogy a rajta tárolt adatokra már nincs szükségünk!'''
|}

Ez a leírás a merevlemezek és hasonló háttértárak (pl. Compact Flash, vagy SD kártya) használatának előkészítését - azaz partícionálását és formázását - ismerteti az [[AmigaOS]] részét képező '''HDToolBox''' nevű segédprogrammal. A célja, hogy kezdőknek segítsen az elindulásban és megkönnyítse az első lépéseket a rendszer telepítésében. A leírás feltételezi, hogy a hardver megfelelően működik, a csatlakoztatott háttértár pedig kompatibilis az [[AmigaOS]] rendszerrel és a gép hardverével.

* ''A leírás az [[AmigaOS]] 3.1-s verziójára épül és az ahhoz csomagolt '''HDToolBox''' programot ismerteti. Ennek oka, hogy az újabb verziókban a '''HDToolBox''' programot jelentősen átalakították és könnyebben használható lett, viszont az abban szerzett ismeretek nem használhatók a régebbi '''HDToolBox''' verziókkal. Ezen túlmenően a későbbi [[AmigaOS]] verziók nem kompatibilisek valamennyi [[Amiga]] számítógéppel azok gyári, bővítetlen formájában. A leírás csak a legelterjedtebb hardverek ismert problémáira tér ki, nem célja valamennyi lehetséges konfiguráció lefedése.''

* ''Alapvető fogalmak tisztázásához, például hogy mi egy partíció és miért van jelentősége, [https://hu.wikipedia.org/wiki/Part%C3%ADci%C3%B3 lásd a Wikipedia releváns szócikkét].''

* ''A leírás a "merevlemez" kifejezéssel hivatkozik az összes lehetséges háttértár típusra. Bár manapság a háttértárak széles skálája létezik, az [[Amiga]] szempontjából funkcionalitásuk a korabeli merevlemezekével egyezik meg, ezért az egyszerűség és érthetőség kedvéért így hivatkozunk rájuk. A lent részletezett eljárás természetesen működik SSD-vel, vagy pl. Compact Flash vagy SD kártya használatával is.

=== Az Amiga és a merevlemezek ===

Kezdetben az [[Amiga]] csak floppy lemezzel működött, de korán megjelentek az első külső merevlemez bővítések. A különféle korai gyártók kvázi szabványait és merevlemez formátumait a [[Commodore]] a '''Rigid Disk Block''' ([[RDB]]) formátum bevezetésével a [[Kickstart]] 1.2-ben egységesítette. Az [[RDB]] formátum tulajdonságait lásd [[RDB|a vonatkozó szócikknél]].

== Első lépések ==

Amennyiben új háttértárat csatlakoztattunk a géphez, az első lépés az [[AmigaOS]] telepítése. Ehhez az '''Install''' lemezt kell az elsődleges floppy meghajtóba helyezni, majd megvárni amig a Workbench betöltődik.

Amennyiben már meglévő rendszerünkhöz szeretnénk egy további meghajtót csatlakoztatni, a '''HDToolBox''' programot a már feltelepített rendszeren a '''SYS:HDTools''' könyvtárban találjuk meg.

== A megfelelő vezérlő beállítása és a HDToolBox indítása ==

== Merevlemez detektálása és kiválasztása ==

== Partíciók készítése ==

== A fájlrendszerek beállítása ==

== A beállítások mentése ==

== Haladó beállítások ==

=== További fájlrendszerek használata ===

== Hibalehetőségek és megoldásaik ==

=== Driverproblémák ===

Sajnos az [[Amiga]] számítógépekhez készült merevlemez vezérlők meghajtóprogramjainak minősége erősen változó, a gyári [[Commodore]] vezérlőket is beleértve. A legtöbben ezekkel a problémákkal 600-as és 1200-as gépeken találkoznak.

=== Méretproblémák ===

=== HDInstTools ===

Merevlemez partícionálása egyszerűen

2017-12-06T19:29:07Z

Chain-Q: wipwip

== Bevezető ==

{|
|-
|[[Fájl:Vigyazat.png|96px]]
| '''FIGYELEM! Az ebben a szócikkben bemutatott eljárások nem megfelelő használata adatvesztéshez vezethet! Csak olyan háttértáron kísérletezzünk, amelyről előtte biztonsági mentést készítettünk, vagy biztosak vagyunk benne, hogy a rajta tárolt adatokra már nincs szükségünk!'''
|}

Ez a leírás a merevlemezek és hasonló háttértárak (pl. Compact Flash, vagy SD kártya) használatának előkészítését - azaz partícionálását és formázását - ismerteti az [[AmigaOS]] részét képező '''HDToolBox''' nevű segédprogrammal. A célja, hogy kezdőknek segítsen az elindulásban és megkönnyítse az első lépéseket a rendszer telepítésében. A leírás feltételezi, hogy a hardver megfelelően működik, a csatlakoztatott háttértár pedig kompatibilis az [[AmigaOS]] rendszerrel és a gép hardverével.

''A leírás az [[AmigaOS]] 3.1-s verziójára épül és az ahhoz csomagolt '''HDToolBox''' programot ismerteti. Ennek oka, hogy az újabb verziókban a '''HDToolBox''' programot jelentősen átalakították és könnyebben használható lett, viszont az abban szerzett ismeretek nem használhatók a régebbi '''HDToolBox''' verziókkal. Ezen túlmenően a későbbi [[AmigaOS]] verziók nem kompatibilisek valamennyi [[Amiga]] számítógéppel azok gyári, bővítetlen formájában. A leírás csak a legelterjedtebb hardverek ismert problémáira tér ki, nem célja valamennyi lehetséges konfiguráció lefedése.''

''Alapvető fogalmak tisztázásához, például hogy mi egy partíció és miért van jelentősége, [https://hu.wikipedia.org/wiki/Part%C3%ADci%C3%B3 lásd a Wikipedia releváns szócikkét].''

=== Az Amiga és a merevlemezek ===

Kezdetben az [[Amiga]] csak floppy lemezzel működött, de korán megjelentek az első külső merevlemez bővítések. A különféle korai gyártók kvázi szabványait és merevlemez formátumait a [[Commodore]] a '''Rigid Disk Block''' ([[RDB]]) formátum bevezetésével a [[Kickstart]] 1.2-ben egységesítette. Az [[RDB]] formátum tulajdonságait lásd [[RDB|a vonatkozó szócikknél]].

== Első lépések ==

Amennyiben új háttértárat csatlakoztattunk a géphez, az első lépés az [[AmigaOS]] telepítése. Ehhez az '''Install''' lemezt kell az elsődleges floppy meghajtóba helyezni, majd megvárni amig a Workbench betöltődik.

Amennyiben már meglévő rendszerünkhöz szeretnénk egy további meghajtót csatlakoztatni, a '''HDToolBox''' programot a már feltelepített rendszeren a '''SYS:HDTools''' könyvtárban találjuk meg.

== További fájlrendszerek használata ==

== Hibalehetőségek és megoldásaik ==

=== Driverproblémák ===

Sajnos az [[Amiga]] számítógépekhez készült merevlemez vezérlők meghajtóprogramjainak minősége erősen változó, a gyári [[Commodore]] vezérlőket is beleértve. A legtöbben ezekkel a problémákkal 600-as és 1200-as gépeken találkoznak.

=== Méretproblémák ===

=== HDInstTools ===

Fájl:Vigyazat.png

2017-12-06T19:18:12Z

Chain-Q: Vigyázat!

Vigyázat!

Merevlemez partícionálása egyszerűen

2017-12-06T15:56:36Z

Chain-Q: wip

== Bevezető ==

Ez a leírás a merevlemezek és hasonló háttértárak (pl. Compact Flash, vagy SD kártya) használatának előkészítését - azaz partícionálását és formázását - ismerteti az [[AmigaOS]] részét képező '''HDToolBox''' nevű segédprogrammal. A célja, hogy kezdőknek segítsen az elindulásban és megkönnyítse az első lépéseket a rendszer telepítésében. A leírás feltételezi, hogy a hardver megfelelően működik, a csatlakoztatott háttértár pedig kompatibilis az [[AmigaOS]] rendszerrel.

''A leírás az [[AmigaOS]] 3.1-s verziójára épül és az ahhoz csomagolt '''HDToolBox''' programot ismerteti. Ennek oka, hogy az újabb verziókban a '''HDToolBox''' programot jelentősen átalakították és könnyebben használható lett, viszont az abban szerzett ismeretek nem használhatók a régebbi '''HDToolBox''' verziókkal. Ezen túlmenően a későbbi [[AmigaOS]] verziók nem kompatibilisek valamennyi [[Amiga]] számítógéppel azok gyári, bővítetlen formájában. A leírás csak a legelterjedtebb hardverek ismert problémáira tér ki, nem célja valamennyi lehetséges konfiguráció lefedése.''

== Első lépések ==

Amennyiben új háttértárat csatlakoztattunk a géphez, az első lépés az [[AmigaOS]] telepítése. Ehhez az '''Install''' lemezt kell az elsődleges floppy meghajtóba helyezni, majd megvárni amig a Workbench betöltődik.

== További fájlrendszerek használata ==

== Hibalehetőségek és megoldásaik ==

=== Driverproblémák ===

Sajnos az [[Amiga]] számítógépekhez készült merevlemez vezérlők meghajtóprogramjainak minősége erősen változó, a gyári [[Commodore]] vezérlőket is beleértve. A legtöbben ezekkel a problémákkal 600-as és 1200-as gépeken találkoznak.

=== Méretproblémák ===

=== HDInstTools ===

Merevlemez partícionálása egyszerűen

2017-12-06T14:46:49Z

Chain-Q: első verzió, skicc, többisleszmég

== Bevezető ==

Ez a leírás a merevlemezek és hasonló háttértárak (pl. Compact Flash, vagy SD kártya) használatának előkészítését - azaz partícionálását és formázását - ismerteti az [[AmigaOS]] részét képező '''HDToolBox''' nevű segédprogrammal. A célja, hogy kezdőknek segítsen az elindulásban és megkönnyítse az első lépéseket a rendszer telepítésében. A leírás feltételezi, hogy a hardver megfelelően működik, a csatlakoztatott háttértár pedig kompatibilis az [[AmigaOS]] rendszerrel.

A leírás az [[AmigaOS]] 3.1-s verziójára épül és az ahhoz csomagolt '''HDToolBox''' programot ismerteti. Ennek oka, hogy az újabb verziókban a '''HDToolBox''' programot jelentősen átalakították és könnyebben használható lett, viszont az abban szerzett ismeretek nem használhatók a régebbi '''HDToolBox''' verziókkal. Ezen túlmenően a későbbi [[AmigaOS]] verziók nem kompatibilisek valamennyi [[Amiga]] számítógéppel azok gyári, bővítetlen formájában.

== Első lépések ==

Amennyiben új háttértárat csatlakoztattunk a géphez, az első lépés az AmigaOS telepítése. Ehhez az Install lemezt kell az elsődleges floppy meghajtóba helyezni, majd megvárni amig a Workbench betöltődik.

== További fájlrendszerek használata ==

== Hibalehetőségek és megoldásaik ==

=== Driverproblémák ===

Sajnos az [[Amiga]] számítógépekhez készült merevlemez vezérlők meghajtóprogramjainak minősége erősen változó, a gyári [[Commodore]] vezérlőket is beleértve. A legtöbben ezekkel a problémákkal 600-as és 1200-as gépeken találkoznak.

=== Méretproblémák ===

=== HDInstTools ===

Kezdőlap

2017-12-06T13:31:12Z

Chain-Q: MIamiDx hálózati beállítások egyszerűen hozzáadva

Üdvözlünk az [http://amigaspirit.hu amigaspirit.hu] - [http://pegasos.hu pegasos.hu] közös Wiki oldalán!

Ez egy WikiWiki projekt, amelynek célja egy teljes és lehetőség szerint minél pontosabb tartalmú, az [http://amigaspirit.hu amigaspirit.hu] és a [http://pegasos.hu pegasos.hu] témaköreihez kapcsolódó információs tár elkészítése.

== Tartalom ==

'''Klasszikus Amiga hardverek'''

[[Amiga]] - [[PowerUP]] - [[Minimig]] - [[NatAmi]]

'''Újgenerációs hardverek'''

[[AmigaOne]] - [[SAM440EP]] - [[Pegasos]] - [[Efika]]

'''Operációs rendszerek'''

[[AmigaOS]] - [[AmigaOS4]] - [[MorphOS]] - [[AROS]]

'''Cégek'''

[[Commodore]] - [[Amiga Inc]] - [[Hyperion Entertainment]] - [[ACube|ACube Systems]] - [[Genesi]] - [[BPlan|bplan]] - [[Motorola]] - [[Phase5]] - [[Escom|ESCOM]]

'''Személyek'''

[[Jay Miner]] - [[Jeri Ellsworth]] - [[Bill McEwen]]

'''Technológia'''

[[M68K]] - [[PowerPC]] - [[Pre-emptive multitasking]] - [[Exec]] - [[Zorro]] - [[CHRP]] - [[PC]]

'''Kérdések és válaszok'''

[[Faq| Általános Amiga FAQ]] - [[MorphOS PowerUP|MorphOS PowerUP GYIK]]

'''Leírások, Hogyanok'''

[[Amiga programok|AmigaOS programok listája]] - [[MorphOS programok|MorphOS programok listája]] - [[AmigaDOS]] - [[FTPMount|FTP Mount]]

[[ISHAR játékleírás]] - [[ISHAR Végigjátszás]] - [[ISHAR Walkthrough - english]]

[[CD32WB|CD32WB Workbench 3.1 CD32-höz]]

[[MiamiDx hálózati beállítások egyszerűen]]

'''Események, rendezvények'''

[[Amiga Klub]] - [[AmiCon|AmiCon találkozó]] - [http://www.scenecon.hu SceneCON party] - [http://function.hu Function party] - [[Retro video- és kvarcjáték kiállítás]]

'''Kapcsolat'''

[[Amigaspirit|#amigaspirit IRC csatorna]] - [[Banner|amigaspirit.hu és pegasos.hu bannerek]] - [http://forum.amigaspirit.hu amigaspirit.hu fórum] - [http://forum.pegasos.hu pegasos.hu fórum]

PC

2017-09-07T15:27:36Z

Chain-Q: tovabbi szakszeru megnevezesek

[[Image:pcxt.jpg|thumb|150px|Egy Intel alapú szemétbánya]]
Jelentése "Personal Computer", ezt a nevet adta az [[IBM]] az [[Intel]] processzorra és a [[Microsoft]] MS-DOS-ra épülő rendszerének.

Fontos megjegyezni, hogy már a [[Commodore]] 64-en is a "Personal Computer" felirat áll, bár azt inkább "Home Computer"-ként emlegetjük.

Más jelentése esetleg a [[CPU]]-kban "Program Counter", azaz az a regiszter amely megmutatja, hogy éppen melyik memóriaterületen áll a program végrehajtása.

Mivel a széles körben elterjedt "PC" megnevezés nem elég kifejező az ismert számítógépnek látszó tárgy számára, leleményes [[Amiga|Amigások]] jobbnál jobb alternatív neveket találtak ki. Álljon itt egy pár közülük:

* Hajtogatott hullámbádog
* Intel alapú szemétbánya
* Hurkatöltõ
* Pumpa
* Primitiv Calculator
* Fostalicska
* Foskupac
* Fostömlõ
* Fospumpa
* Fosi
* Dzsunkaware
* Trágyadomb
* Szarkompresszor
* Nehézvízgõzerõmûves villanybalalajka
* Veszélyes hulladék
* Bináris abakusz
* Ganalyszivattyú
* Klozet
* Delejroncs
* Retekputtony

Amiga PCMCIA FAQ

2015-01-22T10:04:01Z

Chain-Q: faq v0.0001

===Általános patchek===
* [http://aminet.net/package/util/boot/CardPatch CardPatch]
* [http://aminet.net/package/util/boot/CardReset CardReset]

===CF kártya átalakítóhoz===
* [http://aminet.net/package/disk/misc/cfd compactflash.device]
* [http://aminet.net/package/disk/misc/fat95 FAT95]

===Hálózati kártyákhoz===
* [http://aminet.net/package/driver/net/3c589 3Com Etherlink III]
* [http://www.g-mb.de/cnet/index_e.html NE2000 alapú, "cnet.device"]
* [http://aminet.net/package/driver/net/prism2v2 Prism2 WiFi]

PCMCIA

2015-01-22T09:51:04Z

Chain-Q: bbcode--

PCMCIA a ''Personal Computer Memory Card International Association'' rövidítése. Ez az iparág vezető cégeit tömörítő szervezet készítette el az elsősorban laptopokba szánt bővítőkártya szabványát, amelyet PCMCIA-ként, vagy "PC Card"-ként ismerünk. A szabvány első verziója 16 bites volt, és az [[ISA]] buszon alapult. A PCMCIA kártyák egy 68 tűs foglalatba csatlakoznak.

Az [[Amiga]] 600 és 1200 modellek gyárilag tartalmaznak PCMCIA csatlakozót, a gép bal oldalán. Készült [[Zorro]] buszos PCMCIA kártya is, amellyel más modelleket is felszerelhetünk PCMCIA csatlakozóval.

=== Külső hivatkozások ===
* [http://en.wikipedia.org/wiki/PC_Card PC Card a Wikipedián (angol)]