Spelling fix

This commit is contained in:
AGG2017 2024-02-14 13:58:16 -05:00
parent 9da52bd7e6
commit 9c1f1dfe3d

View file

@ -21,11 +21,11 @@ This [flashforge](https://github.com/FlashforgeOfficial/AD5M_Series_Klipper) is
1. Clone the repository.
2. Place `.bin`, `.zip` or `.swu` firmware files in the `FW` directory.
If you don't have them, you can use the script `fwdl.sh <model> <version>` to download in the folder `FW` the version for the printer model you need. The supported models are `K2Pro`, `K2Plus` and `K2Max`. The version is given in the format `X.Y.Z` like `3.0.9`.
If you don't have firmware files, you can use the script `fwdl.sh <model> <version>` to download in the folder `FW` the version for the printer model you need. The supported models are `K2Pro`, `K2Plus` and `K2Max`. The version is given in the format `X.Y.Z` like `3.0.9`.
3. Run `unpack.sh <update_file>` to unpack the selected firmware update file. The supported file extensions are `bin`, `zip` and `swu`. The result is in the folder `unpacked`.
4. Modify the options file `options.cfg` to select the options you need and run `patch.sh` to patch the firmware file. The result is still in the folder `unpacked`. You may manually modify the current state of the files if needed. You can also prepare different configuration files for differents needs based on the default file `options.cfg`. The custom configuration file is provided as parameter: `patch.sh <custom_configuration_file>`. If no parameter is provided, the file `options.cfg` will be used.
5. Run `pack.sh` to pack the firmware files from the folder `unpached`. The result is the file `update/update.swu`.
6. If your printer is still with the original firmware, you have to make root access first. Then replace the `/etc/swupdate_public.pem` in the printer with the one in the `RESOURCES` directory or create your own (make a copy first of the original `/etc/swupdate_public.pem` key in case you want to return to the original `ota` updates). Then aply the newly generated custom software `update/update.swu` by USB update (place the file `update.swu` in the folder `update` on the root of a FAT/FAT32 formated USB disk). If your printer already has custom update installed, then you can directly aply the new update by USB update.
4. Modify the options file `options.cfg` to select the options you need and run `patch.sh` to patch the firmware files in the `unpacked` folder. The result is still in the folder `unpacked`. You may manually modify the current state of the files if needed. You can also prepare different configuration files for different needs based on the default file `options.cfg`. The custom configuration file is provided as parameter: `patch.sh <custom_configuration_file>`. If no parameter is provided, the file `options.cfg` will be used.
5. Run `pack.sh` to pack the firmware files from the folder `unpacked`. The result is the file `update/update.swu`.
6. If your printer is still with the original firmware, you have to make root access first. Then replace the `/etc/swupdate_public.pem` in the printer with the one from the `RESOURCES` directory or create your own (make a copy first of the original `/etc/swupdate_public.pem` key in case you want to return to the original `ota` updates). Then apply the newly generated custom software `update/update.swu` by USB update (place the file `update.swu` in the folder `update` on the root of a FAT/FAT32 formated USB disk). If your printer already has custom update installed, then you can directly apply the new update by USB update.
Default password for the root access (UART and SSH) is `toor` but it can be changed in the `options.cfg` file.