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.
BalenaEtcher is based on NodeJS so it uses a lot of library layers to flash. We have found it to be unreliable on some systems and it has repeatedly caused issues for some users. You are free to try it but if the image exhibit certain bugs, it might be due to the tool. We do not recommend if other options are available due to the field failures.
There is an alternative flash tool called OMAPFlash in which the CSST USB driver was replaced by a WinUSB based driver, so the application can run on Windows7 (32 and 64 bit) platforms. This tool is available on request through your local TI Representative.
Important: This tool is no longer supported by TI however I have attached it for your experiments and regret it comes with discalimer of no support or warranty so use at your own discretion.
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?
The first step to install FlashTool on a Windows PC is to install the flash tool drivers. The drivers are needed for your Windows PC to communicate with your Gemini, the minimum requirement is to have a 64bit Windows operating system.
Once downloaded, unzip the archive. You will find a folder called FlashToolDrivers, open the folder and double click on the Install (install.bat) file. Allow the installation to complete by clicking Yes when asked to make changes.
On Fedora you will have to write the following command to allow applications running with root privileges to access the X server (this will fix the lines above for both the gedit and the flash_tool command):
Before flashing the device with a different firmware it is a good idea to backup the current NVRAM partition. This partition stores key information for your Gemini, including the IMEI number. If it gets lost or damaged, your Gemini will not be able to take or receive calls.
The provided flash tool is already configured for your Gemini. To create a backup of your NVRAM partition, just click on the Readback tab and then on the Add button. A row will appear in the table as in the following screenshot.
If you want to flash the complete firmware to your unit then select Firmware Upgrade from the drop down menu.This will automatically select all the partitions in the table and it will restore your unit to its factory state. Please note that you will loose all your personal data/settings.
To start the flashing process, just click the big Download button, connect your PC to the left end USB-C port on your Gemini and restart the Gemini. Once booting, the flash tool will detect the unit and will start flashing the device with the selected firmware.
If instead you want to manually update your Gemini without loosing your data, you should select the Download Only option from the drop down menu. After that, make sure you select all the partition with the exception of the userdata partition, which contains your data. Your screen should look like this:
There is actually a .deb file for the tool. I really have no idea whether it is official sony or just unofficial linux port. All I know is that there is a .deb file for the tool which installs the flash tool on ubuntu. That actually left me wondering if there is any way out for Suse.
The power supplied to the device is one of the most important elements for both flashing the device and for stable operation. You must ensure that the device receives sufficient power (current AND appropriate voltage level) to properly flash the firmware on the device.
Some adapters can be switched between 3.3V and 5V for the data pins, but still provide 5V on the power pin which will irreparably destroy your device. You MUST make sure the data (RX and TX) and VCC pins are set for 3.3V.
Many serial programmers do not have a voltage regulator on board like the pictured ones. The ESP requires at least 150mA, many 3.3V serial programmers cannot supply this much current as many serial programming tasks do not require a large amount of power.
If you're intimidated by soldering there are 3D printed jigs available for different modules and devices. At worst, you could get away with holding the headers tightly with jumper wires in pin holes during flashing but it is not a foolproof process and flashing might fail.
Tasmota installed from a precompiled binary needs to be configured to work with your Wi-Fi network before you can access the Tasmota web UI. This is usually done by connecting to a Tasmota Wi-Fi Access Point with your smartphone (or tablet or computer with Wi-Fi).
We need to connect to the serial programming interface of the ESP chip. This is done by connecting our serial-to-USB converter TX and RX pins to the ESP RX and TX pins and powering the chip with the 3.3V and GND pins.
In most cases those pins are available on the PCB in the form of pin holes or solder pads but pin headers or jumper wires need to be soldered or otherwise applied. In some cases you will need to solder wires directly on the chip's pins which requires some experience and good soldering equipment.
If you are not careful, your own health will be in danger. Shorting your serial interface with mains AC power will fry your device and serial adapter and will also harm or destroy your computer. It is important to always have all mains power cables disconnected from the device while being connected via serial or even while the case of the device is opened.
Each device has its pins labelled differently. If the labelling isn't visible on the PCB please refer to the devices flashing guide or search the Internet for correct pin locations. Device specific instructions and restrictions are documented in the Tasmota Supported Devices Repository. Pinouts for commonly used Wi-Fi modules are found here
On many devices the installed control button is connected to GPIO0 and GND, making entering Programming Mode easy. On others you will need to bridge the pins on the PCB or directly on the chip with a jumper wire. GPIO0 locations for popular modules can be found in Pinouts!
You can test whether your device is in Programming Mode by attempting to read information from the ESP82xx chip. This requires esptool.py. Instructions on installing and using esptool are provided below. For example (COM5 will be your COM port):
Leave Erase before flashing checked if it is the first time flashing Tasmota on the device or you're experiencing issues with the existing flash and need to do a full erase. If you're upgrading an already flashed Tasmota and wish to keep your settings, uncheck Erase before flashing.
Esptool uses the serial interface to communicate with your device. On Windows these interfaces are named COM1, COM2, etc. and on Linux they are named /dev/ttyUSB0, /dev/ttyUSB1, etc. Before using esptool, make sure you know which serial port your programming adapter is connected to.
Backup the current firmware with the following command: esptool.py --port COM5 read_flash 0x00000 0x100000 fwbackup.bin When the command completes the device is not in programming mode anymore. Repeat the process of putting your device in programming mode.
When it connects to the network, you may get a warning that there is no Internet connection and be prompted to connect to a different network. Do not allow the mobile device to select a different network.
After you have connected to the Tasmota Wi-Fi AP, open in a web browser on the smartphone (or whatever device you used). Depending on the phone, it will take you to the Tasmota configuration page automatically, or you will get a prompt to sign in to Wi-Fi network or authorize. Tapping on the AP name should also open the configuration page.
Click the checkbox if you want to see the password you enter to ensure that it is correct. Click on Save to apply the settings. The device will try to connect to the network entered.
Connect your device to the serial programmer. You should see the initial boot output in Termite. If your screen is empty type status in the bottom command bar and hit enter. If you get a return message from your device similar to the one displayed under purple status you're all set.
c80f0f1006