I think 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.
UniFlash is a software tool for programming on-chip flash on TI microcontrollers and wireless connectivity devices and on-board flash for TI processors. UniFlash provides both graphical and command-line interfaces.
UniFlash is a standalone tool used to program on-chip and external flash memory on TI MCUs and on-board flash memory for Sitara processors. UniFlash has a GUI, command line, and scripting interface. UniFlash is available free of charge.
I was a bit confused by your details, after reading a few times, I think I understand what you are trying to do. You are using a custom board, not NXP EVB, and it has 2 flash memory devices connected via QSPI. Your board is also setup to use the Serial RCON, which means the configuration comes from the value programmed to EEPROM (as is an option with the NXP EVB). We already have a script for this to change the value, probably you already know of this:
my request is that if the tool is supporting S32G, we should mention it in somewhere. like the user guide in the folder "C:\NXP\S32DS.3.4\S32DS\tools\S32FlashTool\doc", we only mentioned S32S247TV and S32V234, not mentioning S32G at all. though we do have another txt file in the same folder "supported S32G devices" mentioned briefly the S32G rev1.0 rev 2.0 and 4 family members supported. can we include those info into same user guide?
Bonsoir,
I have updated the firmware of my HDSPe AIO card using Windows Flash Update Tool version 2.47.
My card has been upgraded to revision 200, but is now considered as AIO Pro.
It is therefore impossible for me to upgrade it to a previous revision: the tool proposes a revision corresponding to AIO Pro.
a mod for libre redirected me to here from reddit. I for some reason cannot find a single tutorial for using the libre flash tool to flash a operating system (arch arm64 in my case) to a sd card, i am planning to do it through my linux mint vm. if someone can point me in the right place for a walkthrough that would be great. thank you in advance.
im not sure if maybe I explained something wrong or not but, when I made a post to reddit about using arch linux (arm64 image) a dev from the libre account said i could use the libre flash tool with the arm64 image and be able to write it with the tool. Link to my post: Reddit - Dive into anything
Im simply just trying to find a solution.
Recently, well actually two days back when I installed Flashtool on my Windows 8 Laptop in order to flash my cutie pie, Xperia Ray phone ? I ran into a massive issue. After successfully installing Flashtool setup I headed up to installing flashtool drivers. I selected the needed drivers from the list and executed with the process, but then suddenly the driver installation results had failed at the end. I tried running as Admin, restarting the Lap and I even downloaded the whole set up once again, which was pretty much retarded until i realized the issue and reinstalled the whole thingy. But still NO ! -_-
To install all the drivers for the Windows operating system, you download the software Easy Driver Pack for Win8 x64 at download here (Chinese version), after downloading, run the .exe file. For other Windows versions, you accessed at and search by keyword Easy Driver Pack
Long story short, the Asus CUSL2 motherboard got a soldered bios chip so I cant get away with my normal usb bios flasher routine, resulting in me finally having to dig up and test my old floppy that ofc didn't work.. So now Im stuck with having to update the bios of this lovely motherboard from within Windows, the question is what program to use? Ive tried winflash and asus live update (requires internet) so far.
It -might- work to format a spare empty IDE drive with minimal DOS files (as found on a flashing-floppy or flashing USB stick) and use that in place of the floppy. If the utility has any bat files bundled you may need to edit the file paths to C drive.
GRUMPY OLD FART - On Hiatus, sort'a
Mann-Made Global Warming. - We should be more concerned about the Intellectual Climate.
You can teach a man to fish and feed him for life, but if he can't handle sushi you must also teach him to cook.
And about the floppy, Id probably desolder the chip to flash it before ordering a new floppy so might just as well have risked the windows flash first as a bricked chip wouldnt be that bad if it didnt play out as expected.
Floppy drives are cheap or come included with old systems.
I keep some in my toolbox (so to speak) for work bench use.
.
I have a chip programmer too but I went so long without one I completely forget I even have that option.
.
1) More adapters is always beter ? already run the system with an SSD and a SATA to IDE adapter, the IDE to USB adapter came in handy now.
2) Making a bootable DOS hdd within windows was kind of annoying. The get around I succeeded with was to run an old IDE hdd with the IDE to USB adapter to trick Rufus it was a portable hdd. Then switching it to normal IDE connection for the motherboard to be able to boot from it.
We recommend that you disable any antivirus or security software on your computer before installing Reach Firmware Flash Tool. Such programs may delete important files that the tool needs to work correctly.
If your Flash tool version is 1.7.1 or older, to update to the latest version you will need to add the new GPG key. Run sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 90F3927E0416B765 command in the terminal.
Make sure you have enough disk space. Reach Firmware Flash Tool creates 2 folders: one to download the image and another one to unpack it. Once you close the Flasher tool, the folder with the unpacked image will be deleted.
All results were taken from the J-Link Commander output. Tests started with the flash either empty or erased, as flash erase times depend very much on the selected device. Sector sizes may grow for large devices. Please refer to the chip manual of the appropriate device to get information about erase times.
J-Link supports the programming of memory-mapped QSPI NOR flash via the standard methods described above.
In the beginning, SPI NOR flash was usually a custom connection and not standardized, with advanced MCUs and QSPI flash memory-mapped made visible in the MCU address space. However, it eventually became a full replacement and even successor of parallel NOR flash. With J-Link, all features known from internal flash are also available in memory-mapped QSPI flash:
Note: Hardware breakpoints are not usable in QSPI flash on many Cortex-M based devices. This makes J-Link + flash breakpoints the only real option to debug in QSPI flash on these devices.
A customized flash algorithm is needed to program these devices. Customers can do this themselves using J-Link Device Support Kit, or SEGGER can help. Please contact sa...@segger.com to request a quotation.
SEGGER engineers have written, validated, and optimized the flash loaders, making sure they work reliably and deliver the best possible performance. SEGGER has hardware in-house for all supported devices and can re-test and give support to users.
SEGGER's Embedded Experts can add support for new or custom devices by drawing on their extensive experience. In many cases, this is done by SEGGER free of charge. However, in urgent cases, or for devices which are not designed for the mass market, or devices that are highly complex, or for other reasons, there may be a charge.
All tests were performed by placing a 512 KB program into the flash memory of a blank STM32F417IG microcontroller connected via SWD interface. The SWD speed was selected at the maximum possible for each debug probe.
The J-Link also has the option of further software enhancements with the production flash programming utility (J-Flash). The ability to take full advantage of the development environment using the Unlimited Flash Breakpoint module also means you free your development from the hardware breakpoint restriction. In this test, J-Link is the clear winner.
We do not recommend or support the following programming methods via J-Link Commander or J-Flash Lite for production purposes. Regarding production programming, only production grade programming tools should be used.
Production grade programming tools typically feature a more sophisticated, multi-step verification process. Many applications also require customization / patching of variable data such as serial number(s), MAC addresses and similar.
J-Flash Lite is a free, simple graphical user interface which allows downloading into flash memory of target systems. J-Flash Lite is part of the J-Link Software and Documentation package, available for download here.
How to perform downloading into flash via J-Flash Lite:
Flasher is a programming tool for all common devices with internal or external flash memory. For a list of all supported devices click here. Flasher ARM is designed for programming flash targets with the J-Flash software or stand-alone.
d3342ee215