Firmware Update - Revision history

Acid at 13:10, 14 December 2023

2023-12-14T13:10:29Z

← Older revision		Revision as of 13:10, 14 December 2023
Line 47:		Line 47:

	In both cases you should see a new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases the medusa firmware update software should work without any problems.		In both cases you should see a new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases the medusa firmware update software should work without any problems.

			== Linux udev ==

			Usually in Linux default permission to /dev/ttyACMn (device file used to communicate with Medusa) is <code>rw-rw---- root uucp</code>. In such case only root and users belong to uucp group have write access to this file. The first solution is to add your user to 'uucp' group. The second is to add specific 'udev' rule for Medusa that will make sure that all users will have rights to Medusa's port. To do that usually you should create file in '/etc/udev/rules.d/' named '##-medusa.rules' (for example '77-medusa.rules') with following content:
			<pre>
			SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", MODE="0666", SYMLINK+="ttyMedusa"
			</pre>
			After that you need to reload rules. Typically run the command: <code>sudo udevadm control --reload</code> and then <code>sudo udevadm trigger</code>.

	== To brick or not to brick ==		== To brick or not to brick ==

Acid: /* Firmware Update */

2023-12-14T12:55:20Z

Firmware Update

← Older revision		Revision as of 12:55, 14 December 2023
Line 3:		Line 3:
	# Check your hardware revision (see [[Description#Hardware_Revisions]]). Beware that firmwares 1.0.18 and older are only compatible with REV A. If you install older firmware on REV B then you may experience some strange behaviour but you won't brick the device and reinstalling correct firmware will be possible and will fix those issues.		# Check your hardware revision (see [[Description#Hardware_Revisions]]). Beware that firmwares 1.0.18 and older are only compatible with REV A. If you install older firmware on REV B then you may experience some strange behaviour but you won't brick the device and reinstalling correct firmware will be possible and will fix those issues.
	# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf] (unsigned file specifically designed for Mesusa) or this file: [//medusa-sc.org/firmware/stmcdc.zip stmcdc.zip] (signed driver for all CDC devices with stm32 chips). See below how to use those files.		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf] (unsigned file specifically designed for Mesusa) or this file: [//medusa-sc.org/firmware/stmcdc.zip stmcdc.zip] (signed driver for all CDC devices with stm32 chips). See below how to use those files. In case of Linux make sure that your user has permissions to write to serial port (see below).
	# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):		# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):
	<pre>		<pre>

Acid: /* Firmware Update */

2023-11-22T13:07:44Z

Firmware Update

← Older revision		Revision as of 13:07, 22 November 2023
Line 1:		Line 1:
	== Firmware Update ==		== Firmware Update ==

			# Check your hardware revision (see [[Description#Hardware_Revisions]]). Beware that firmwares 1.0.18 and older are only compatible with REV A. If you install older firmware on REV B then you may experience some strange behaviour but you won't brick the device and reinstalling correct firmware will be possible and will fix those issues.
	# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf] (unsigned file specifically designed for Mesusa) or this file: [//medusa-sc.org/firmware/stmcdc.zip stmcdc.zip] (signed driver for all CDC devices with stm32 chips). See below how to use those files.		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf] (unsigned file specifically designed for Mesusa) or this file: [//medusa-sc.org/firmware/stmcdc.zip stmcdc.zip] (signed driver for all CDC devices with stm32 chips). See below how to use those files.

Acid: /* Using medusa.inf or stmcdc.zip */

2023-03-02T14:40:42Z

Using medusa.inf or stmcdc.zip

← Older revision		Revision as of 14:40, 2 March 2023
Line 45:		Line 45:
	# Windows will inform you that this driver might not be good for the selected device (because it is a universal driver for all STM32 CDC devices - not specifically for Medusa, but it works perfectly ok) - press the "yes" button.		# Windows will inform you that this driver might not be good for the selected device (because it is a universal driver for all STM32 CDC devices - not specifically for Medusa, but it works perfectly ok) - press the "yes" button.

	In both cases you should see a new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases the medusa firmware update software should ~~now~~ work without any problems.		In both cases you should see a new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases the medusa firmware update software should work without any problems.

	== To brick or not to brick ==		== To brick or not to brick ==

Acid at 14:39, 2 March 2023

2023-03-02T14:39:37Z

Acid at 17:21, 26 February 2023

2023-02-26T17:21:51Z

@@ Line 2: / Line 2: @@
 # Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
-# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf].
+# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf] (unsigned file specifically designed for Mesusa) or this file: [//medusa-sc.org/firmware/stmcdc.zip stmcdc.zip] (signed driver for all CDC devices with stm32 chips). See below how to use those files.
 # Run the application. On the console you should see something like this (typically it takes less than 10 seconds):
 <pre>
@@ Line 21: / Line 21: @@
 Sending fpga core hmac
 </pre>
 == To brick or not to brick ==

Acid: /* Firmware Update */

2023-02-26T16:18:28Z

Firmware Update

← Older revision		Revision as of 16:18, 26 February 2023
Line 2:		Line 2:

	# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and ~~olders~~ you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf].		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and older you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf].
	# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):		# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):
	<pre>		<pre>

Acid: /* Firmware Update */

2023-02-26T16:16:06Z

Firmware Update

← Older revision		Revision as of 16:16, 26 February 2023
Line 2:		Line 2:

	# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux and ~~Macos~~. In case of ~~Windows the needed driver is usually installed, but if it is not, then install it~~. ~~Description is~~ [~~https:~~//~~docs~~.~~microsoft.com/en-us~~/~~windows-hardware~~/~~drivers/usbcon/usb-driver-installation-based-on-compatible-ids here~~]		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux, Macos and Windows 10+. In case of Window 8.1 and olders you need this file: [//medusa-sc.org/firmware/medusa.inf medusa.inf].
	# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):		# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):
	<pre>		<pre>

Acid: /* Firmware Update */

2022-07-07T11:17:39Z

Firmware Update

← Older revision		Revision as of 11:17, 7 July 2022
Line 1:		Line 1:
	== Firmware Update ==		== Firmware Update ==

	# Download firmware from [~~http:~~//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [//medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux and Macos. In case of Windows the needed driver is usually installed, but if it is not, then install it. Description is [https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-driver-installation-based-on-compatible-ids here]		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux and Macos. In case of Windows the needed driver is usually installed, but if it is not, then install it. Description is [https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-driver-installation-based-on-compatible-ids here]
	# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):		# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):

Acid: /* Firmware Update */

2022-07-07T11:16:34Z

Firmware Update

← Older revision		Revision as of 11:16, 7 July 2022
Line 1:		Line 1:
	== Firmware Update ==		== Firmware Update ==

	# Download firmware from [http://~~medusasc~~.org/~~machina~~ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).		# Download firmware from [http://medusa-sc.org/firmware/ Medusa Firmwares Page]. Firmware updater is a binary application that will update the firmware automatically. Binaries are available for Linux (64bit binary for Intel), Max OS X (Intel and ARM binaries) and Windows (32bit and 64bit binaries for Intel).
	# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux and Macos. In case of Windows the needed driver is usually installed, but if it is not, then install it. Description is [https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-driver-installation-based-on-compatible-ids here]		# Make sure that Medusa has been correctly detected by your operating system. Medusa uses standard "virtual serial port" (CDC) protocol on USB, so usually it should work without any drivers on Linux and Macos. In case of Windows the needed driver is usually installed, but if it is not, then install it. Description is [https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-driver-installation-based-on-compatible-ids here]
	# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):		# Run the application. On the console you should see something like this (typically it takes less than 10 seconds):

← Older revision		Revision as of 14:39, 2 March 2023
Line 24:		Line 24:
	== Using medusa.inf or stmcdc.zip ==		== Using medusa.inf or stmcdc.zip ==

	In case of Windows 10 and newer nothing needs to be done and any CDC device is automatically recognized, but in case of older Windows systems user has to manually assign driver (usbser.sys in this case) to specific device (Medusa in this case). By default Medusa in "device manager" ~~is shown~~ as an "unrecognized device". To allow Windows to use usbser.sys you need to:		In case of Windows 10 and newer nothing needs to be done and any CDC device is automatically recognized, but in case of older Windows systems the user has to manually assign a driver (usbser.sys in this case) to a specific device (Medusa in this case). By default Medusa is shown in "device manager" as an "unrecognized device". To allow Windows to use usbser.sys you need to:

	=== Option 1 - using unsigned medusa.inf file ===		=== Option 1 - using unsigned medusa.inf file: ===

	# go to "device manager" and find Medusa under "other devices" ~~with yellow exclamation mark on it.~~		# go to "device manager" and find Medusa under "other devices";
	# right click on it and pick "update driver software..." and then "browse my computer for driver software"		# right click on it and pick "update driver software..." and then "browse my computer for driver software";
	# click "browse" button and select catalog with "medusa.inf" file that you downloaded from this page and then click "next" button		# click the "browse" button and select the catalog with the "medusa.inf" file that you downloaded from this page and then click the "next" button;
	# you see red warning that file you are going to use can be dangerous (because this inf file is not signed) - pick "install this driver software anyway"		# you will see a red warning that the file you are going to use can be dangerous (because this inf file is not signed) - pick "install this driver software anyway".

	=== Option 2 - using signed, universal stmcdc.zip file ===		=== Option 2 - using signed, universal stmcdc.zip file: ===

	# unzip stmcdc.zip file		# unzip the "stmcdc.zip" file;
	# go to "device manager" and find Medusa under "other devices" ~~with yellow exclamation mark on it.~~		# go to "device manager" and find Medusa under "other devices";
	# right click on it and pick "update driver software..." and then "browse my computer for driver software"		# right click on it and pick "update driver software..." and then "browse my computer for driver software";
	# pick option "let me pick from a list of available drivers on my computer"		# pick the option "let me pick from a list of available drivers on my computer";
	# if windows asks you to choose device type - just click "next"		# if windows asks you to choose a device type - just click "next";
	# In next window click on "Have disk..."		# in the next window click on "Have disk...";
	# click "browse" button and select 'stmcdc.inf' in 'stmcdc' folder.		# click the "browse" button and select 'stmcdc.inf' in the 'stmcdc' folder;
	# ~~Then~~ click "ok" and then "next".		# click "ok" and then "next";
	# Windows will inform you that this driver might not be good for ~~given~~ device (because it is universal driver for all ~~STM~~ CDC devices - not specifically for Medusa, but it works perfectly ok) - press "yes" button		# Windows will inform you that this driver might not be good for the selected device (because it is a universal driver for all STM32 CDC devices - not specifically for Medusa, but it works perfectly ok) - press the "yes" button.

	In both cases you should see new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases medusa firmware update software should work ~~now~~ without any problems.		In both cases you should see a new COM port in your system. In case of using medusa.inf you will see "Medusa CDC serial port" and in case of using stmcdc.zip you will see "STMicroelectronics Virtual COM Port" - it doesn't matter. In both cases the medusa firmware update software should now work without any problems.

	== To brick or not to brick ==		== To brick or not to brick ==

	Firmware in Medusa is divided into two parts - simple updater (let's call it part A) and the main program (call it part B).		Firmware in Medusa is divided into two parts - a simple updater (let's call it part A) and the main program (call it part B).

	Part A updates part B (plus FPGA core) and part B updates part A		Part A updates part B (plus FPGA core) and part B updates part A

	~~Boot~~ code in Medusa checks checksums ~~for~~ both parts. If both checksums are correct then it jumps to part B (or part A when "right" button is pressed). If only one of them is correct then it jumps to this part directly. This design prevents device "bricking". Even you loose power during Medusa firmware update, after you turn it back on it will just use the valid part of the firmware. You will only need to run the updater again to complete the procedure.		The boot code in Medusa checks checksums of both parts. If both checksums are correct then it jumps to part B (or part A when the "right" button is pressed). If only one of them is correct then it jumps to this part directly. This design prevents device "bricking". Even if you loose power during Medusa firmware update, after you turn it back on it will just use the valid part of the firmware. You will only need to run the updater again to complete the procedure.