Need to burn multiple firmwares for mass production? Just rely on this tool![Copy link]
Flasher Hub is a new generation Flash batch programming controller from SEGGER, used with Flasher. Flasher Hub can control up to 24 Flashers to program the chip in parallel, which is suitable for batch programming and firmware testing on the production line. Flasher Compact has the characteristics of large capacity and high speed, and can save multiple firmware.
Flasher Hub has 4 USB ports, which are then connected to each Flasher Compact through the powered USB Hub. Flasher Hub has built-in web server and FTP server. Users can log in to the web to manage and burn the Flasher Hub and the connected Flasher Compact, such as firmware upload, deletion, burning, etc. The following figure shows that two Flasher Compacts are currently connected. Users can number and name them for easy identification.
When a product is in mass production, it may be necessary to burn multiple firmware at a time. For example, on a test machine, you need to burn the test firmware first, and then burn the official firmware after all aspects of the hardware have been tested. Burning is divided into two steps. Since Flasher Compact has a built-in 128MB storage space, it can actually store multiple firmwares at a time. When burning, you only need to select the corresponding firmware and burn it through the Flasher Hub web page or send the corresponding ASCII command through telnet.
Two firmwares are prepared for demonstration, one named test.hex and the other named release.hex. First, generate the configuration file and data file of Flasher Compact through J-Flash.
1. Create a new project in J-Flash and set the MCU model and interface type (JTAG/SWD). Then set the IP address of Flasher Hub in Project Settings -> General -> connection type -> TCP/IP (static IP must be configured for Flasher Hub in advance). Check the module to be configured (Flasher Compact). The module serial number can be set in the web page.
2. Open the firmware file from File->Open data file…, the format can be Hex/bin/srecord/ELF. Then export the configuration file from File->Save Flasher config file, and export the data file from File->Save Flasher data file. Export the configuration file and data file for the two firmwares twice and name them differently.
The configuration file (*.cfg) and data file (*.dat) corresponding to the firmware must have the same name, and a directory with the same name will be generated, which contains the Flash programming algorithm (Device.pex). The relative organization of the files should be as shown in the following figure, which are the configuration files and data files generated by the test and release firmware respectively:
3. Upload the generated Flasher configuration file to Flasher Compact through Flasher Hub. It is more convenient to upload using FTP, but please note that you must log in with an account (admin:1234), otherwise you will not be able to upload files without write permission. Here you only need to use module 2 to upload the above files to the directory MODULE.002.
4. Burn in the web interface. After uploading the configuration and data files, select the corresponding module and firmware in the Programming of the web, and then click the start programming button to start burning.
5. Telnet control burning. After the Telnet client connects to the Flasher Hub through port 23, it sends the corresponding ASCII commands to control the firmware burning operation. The Telnet client can use the Windows system built-in or Putty.
Use the command again to select the release firmware and burn it again. This way, the burning of the two firmwares is completed one after another.
6. Use scripts to automatically execute commands
In order to facilitate automated control, you can write a vbs script to automatically call Windows' telnet.exe and execute commands one by one according to actual needs.
提升卡
变色卡
千斤顶
京公网安备 11010802033920号
