Sam Firmware Tool 1.3.1

[Gibert Chisholm]

Ithink you have to install the old Edison drivers first. Emlid DOCS seemed to have removed that information which leaves users with older Reach products with no longer supported Emlid chips at a loss.

Hi @Charlie_Robinson, I have just been through the process of flashing my old reach modules to firmware 26 on a win10 machine. To get USB-to-PC connection I needed to disable driver signatures and then install EdisonDriverSetup1.2.1 as per this thread Flashing Reach RS - Win10

The flashing tool then found the module and completed the update without issue.

So I followed the link and downloaded the update tool. But it doesn't boot on my system just freezing in the middle. The only option is to reset the PC, Ctrl+Alt+Del or any other keys don't work. The screen background turns green on the freeze (it's black initially). Photo attached, tried to add pci=nocrs to the kernel boot options as it suggests but no change. My goal is to make the system boot faster, now it takes about 5 seconds while detecting devices in AHCI and then another 5 seconds in the Linux kernel before starting systemd. I'd like to eliminate these delays.

Thank you for answering. Unfortunately, the proposed solution didn't work for me. After selecting the native resolution (which is 1920x1080x32 for me, tried others with the same result) the screen goes black but the system seems to be completely frozen. I waited for 5 minutes and nothing happened, even NumLock LED doesn't react on NumLock key press. I also tried non-graphical resolutions like 80x25, in that case the outcome is exactly like before, the screen becomes green and everything is frozen, only hard reset works. I also tried adding "linux* 3" (without quotes) to the boot command but it also doesn't work with the exact same result, green background with white text. I suspect the issue is much more fundamental than just setting the framebuffer.

Is it possible to extract the tool from the ISO and run it in the existing Linux environment I use (Debian testing amd64)? I boot Debian from the SSD I want to update so it may not be possible directly, but I have other live USBs that boot fine.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

if that doesn't help you can try recovering it with tftp or nmrpflash.

are you on windows? if so, follow this guide

-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

just make sure you enable tftp

-tftp-windows-10

and here's a video walk through using a tftp client. Use the built in one for windows 10 though. the video is more of an example of how its done.

=R9DLrLQrpaw

and if that doesn't work, you can try using nmrpflash

There's a support site with access to manuals, firmware, install guides, etc.

Go to

Type in your model number and from there it'll take you to the above.

Its a great resource to start with.

Neither of them. The Firmware tool in luban is when you crate your won firmware via the github repository. Both packages will be packed into a .bin file which you then put on a USB stick and update the formware from the Printer screen by selecting it.

Is there a way to upgrade the firmware without the display? I can do nearly everything using GCODE commands, I also see M997 in the Marlin documentation. I just put the firmware file to an USB disk, and issue M997? Is there a naming convention I have to keep? What if there are more firmwares on the USB, which will be loaded?

-to-robot/step-3/imaging-your-roborio.html says "roboRIO firmware must be at least v5.0 to work with the 2019 or later image. If your roboRIO is at least version 5.0 (as shown in the bottom left of the imaging tool) you do not need to update"

However when we imaged a RoboRIO2 the firmware doesn't appear to be separately updatable, and the firmware appears to be 22.something. We are having trouble with an ADI16470 gyro on the roboRIO2, it works fine on the roboRIO1. (I'll submit a separate issue about the gyro.)

In case this is useful we are using Windows 10, latest update. We did the offline install of LabVIEW and game tools. The only update that was applied was for Package Manager which is required to load the REVlib for LabVIEW.

1) Documentation be specific on what needs to be done, including indicating that firmware cannot be updated on the roboRIO2. (My apologies if I missed something in the documentation. Stuff happens in the fog of build season...)

It looks like our issue with the gyro (and with CTRE cancoders) may NOT be related to the image but rather related to needing to mass compile the project and related libraries. I'll know more tonight after testing. I had to mass compile twice to get all the issues to disappear.

I setup dual extruder with shared noozle.

When printing from SF-Card instead of octoprint, everything is fine.

I will try to upload more logs, unfortunately I first deleted them to get fresh one, now have

to look to create new

Using a simple two color object (like a 4x4x4mm cube with the top half one color and the bottom half the other color), please post the gcode your slicer generated and the serial.log of the attempt to print that object.

The terminal output you posted doesn't make any sense because you didn't use the button to surround it and the markdown code this forum uses ate some of the characters. There is also no command with T0 as a parameter so its hard to tell exactly what happened.

M104 S200 T1 is rejected by the printer firmware because it knows that there's only one nozzle. This rejection is ignored when printing from the SD card but shows up as a non-fatal error when printing via OctoPrint.

The Veritas Appliance firmware update tool is a replacement for the Manage > Software > Firmware command. Starting with NetBackup Appliance release 3.1.1 and Access release 7.4.2, Flex release 2.0 this tool is the recommended method for firmware updates.

On appliance, install Appliance OS release (e.g. NetBackup Appliance OS 5.0 / Access OS 8.0 ) before installing the firmware update RPM. Attempting to install Firmware Update RPM before updating appliance OS will give installation error and will not allow Firmware Update.

The RPM installs the Veritas Standalone firmware Update and Recovery Environment. This is a standalone operating system which is booted by the appliance to deploy the firmware updates in a controlled and isolated environment. Upon completion of the firmware updates, the appliance automatically reboots back into the primary application operating system.

The firmware update is packaged as a standalone operating system (ISO) till Flex 2.0.x. FLEX product uses ISO form of firmware update tool. Firmware update ISO is currently available for the following appliance platforms and their associated software versions:

After the EEB installation has completed successfully, you must reboot the appliance. The appliance firmware update begins automatically during the reboot. While the firmware update is in progress, users are unable to access or log in to the appliance through the appliance shell menu or the appliance web console. The firmware update process can be viewed by using the IPMI console or a physical console connection on the appliance.

The final stage of the firmware update includes updating the system BIOS. The BIOS update will disconnect all active IPMI console sessions. When the firmware and BIOS update processes have completed, the appliance reboots into the normal appliance application OS.

Note: When installing this EEB on appliance nodes in a High Availability (HA) setup, update one node at a time. Start with the partner node where the MSDP services are offline. After the EEB installation, the firmware update, and the BIOS update have all completed successfully, perform a switchover so that the updated partner node takes over running the MSDP services. Then, update the other compute node. After the EEB installation, the firmware update, and the BIOS update have all completed successfully, perform a switchover to return the HA setup back to its normal operations.

Firmware Upgrade Tool might show failure in case of successful upgrade (If the controller goes down after upgrade). Check firmware versions, if the firmware versions seems upgraded you can skip further steps, if not keep following the steps.

3a8082e126