3D-printing/cc-fw-tools
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Spelling fix

Browse source
This commit is contained in:
AGG2017 2024-02-18 17:15:42 -05:00
parent 313c050ff8
commit 9c3333d15e
9 changed files with 16 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -26,7 +26,7 @@ This [flashforge](https://github.com/FlashforgeOfficial/AD5M_Series_Klipper) is
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 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.
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 formatted USB disk). If your printer already has custom update installed, then you can directly apply the new update by USB update.
### Notes

2
RESOURCES/OPTIONS/startup_script/startup.sh
View file

@ -30,7 +30,7 @@ fi
# Check if ca-certificates is installed with opkg
# opkg list | grep ca-certificates
# check if cetificates are installed
# check if certificates are installed
if ! opkg list-installed | grep -q ca-certificates; then
opkg install ca-certificates
fi

6
RESOURCES/OPTIONS/webcam/webcam.sh
View file

@ -92,21 +92,21 @@ if [ "$app_ver" == "3.0.9" ]; then
if [ "$app_model" == "K2Pro" ]; then
# stop the app to log the message 'cannot open video'
printf "\x00\xf0\x20\xe3" | dd of="$def_target" bs=1 seek=2339112 conv=notrunc
# slow captive portal commmunication
# slow captive portal communication
printf "\xff\x8f\x0f\xe3" | dd of="$def_target" bs=1 seek=63492 conv=notrunc
exit 0
fi
if [ "$app_model" == "K2Plus" ]; then
# stop the app to log the message 'cannot open video'
printf "\x00\xf0\x20\xe3" | dd of="$def_target" bs=1 seek=2339152 conv=notrunc
# slow captive portal commmunication
# slow captive portal communication
printf "\xff\x8f\x0f\xe3" | dd of="$def_target" bs=1 seek=63492 conv=notrunc
exit 0
fi
if [ "$app_model" == "K2Max" ]; then
# stop the app to log the message 'cannot open video'
printf "\x00\xf0\x20\xe3" | dd of="$def_target" bs=1 seek=2339152 conv=notrunc
# slow captive portal commmunication
# slow captive portal communication
printf "\xff\x8f\x0f\xe3" | dd of="$def_target" bs=1 seek=63492 conv=notrunc
exit 0
fi

6
docs/EMMC_BACKUP.md
View file

@ -5,7 +5,7 @@ This procedure is recommended to be performed when your printer is completely se
To perform a backup follow these steps:
1. Use the original app version 2.39 and stop the booting process by holding key 's' (or use any custom firmware update that has the UART enabled)
2. Insert a USB disk (FAT32 formated) with the file [backup.scr](../extra-stuff/emmc/backup.scr) on it for complete emmc backup. If you need to backup just the system partitions use the file [sbackup.scr](../extra-stuff/emmc/sbackup.scr) instead.
2. Insert a USB disk (FAT32 formatted) with the file [backup.scr](../extra-stuff/emmc/backup.scr) on it for complete emmc backup. If you need to backup just the system partitions use the file [sbackup.scr](../extra-stuff/emmc/sbackup.scr) instead.
3. From the uboot shell enter the following:
```sh
@ -36,7 +36,7 @@ fatload usb 0:1 42000000 backup.scr
For a system backup replace the above script name `backup.scr` with the name `sbackup.scr`.
4. Remove the USB disk with the scripts and insert at least 8GB USB disk for a complete backup (or at least 1GB USB disk for a system backup). It can be formated or not and it will be completely rewritten by the contents of the eMMC. NOTE: Do not use a disk with important information! All data on it will be lost!
4. Remove the USB disk with the scripts and insert at least 8GB USB disk for a complete backup (or at least 1GB USB disk for a system backup). It can be formatted or not and it will be completely rewritten by the contents of the eMMC. NOTE: Do not use a disk with important information! All data on it will be lost!
5. Type the following to execute the script:
@ -44,7 +44,7 @@ For a system backup replace the above script name `backup.scr` with the name `sb
source 42000000
```
6. Wait about 15 minutes (or about 2 minutes for a system backup) and the entire emmc (or the system part of it) will be transfered 1:1 to the USB disk
6. Wait about 15 minutes (or about 2 minutes for a system backup) and the entire emmc (or the system part of it) will be transferred 1:1 to the USB disk
If you see an error and the script stopped before showing 100%, insert another type USB disk and enter again:
```sh

2
docs/EMMC_RESTORE.md
View file

@ -7,7 +7,7 @@ To perform a restore follow these steps according to the current printer working
A/ In case your printer is in good working conditions (it can somehow boot) and you are using firmware version that has uboot enabled.
1. Turn on the printer and stop the booting process by holding key 's'
2. Insert a USB disk (FAT32 formated) with the file [restore.scr](../extra-stuff/emmc/restore.scr) on it for complete emmc restore. If you need to restore just the system partitions use the file [srestore.scr](../extra-stuff/emmc/srestore.scr) instead.
2. Insert a USB disk (FAT32 formatted) with the file [restore.scr](../extra-stuff/emmc/restore.scr) on it for complete emmc restore. If you need to restore just the system partitions use the file [srestore.scr](../extra-stuff/emmc/srestore.scr) instead.
3. From the uboot shell enter the following:
```sh

4
docs/ENTER_FEL_MODE.md
View file

@ -1,6 +1,6 @@
# All info about FEL/XFEL
To enter FEL mode, you can either use the xfel tool or short the pads on the mainboard.
To enter FEL mode, you can either use the xfel tool or short the pads on the main board.
The easiest way is to boot it via u-boot with the command:
@ -10,7 +10,7 @@ efex
This will make the printer boot into FEL mode.
Or you can short the pads on the mainboard. The pads are located near the EMMC chip. You need to short the pads like in the picture below and then power on the printer and it will boot into FEL mode due to the shorted pads.
Or you can short the pads on the main board. The pads are located near the EMMC chip. You need to short the pads like in the picture below and then power on the printer and it will boot into FEL mode due to the shorted pads.
![photo_2024-02-05_02-46-45](https://github.com/ultimateshadsform/Anycubic-Kobra-2-Series-Tools/assets/151234273/be75b895-d655-440e-92d7-b9804da16f05)

4
options.cfg
View file

@ -2,7 +2,7 @@
# 'options.cfg' is the default configuration file used by 'patch.sh'
# You can provide another configuration file as a parameter to 'patch.sh'
# All available patching options are listed below
# Disable patching an option by using '#' or ';' as a first caracter in the option line
# Disable patching an option by using '#' or ';' as a first character in the option line
# Use single or double quotes for the option value. Do not use spaces inside the quotes.
# Use list of values separated by a space if needed because duplicated option are not supported
# In square brackets you may place the name(s) of other option(s) required by a given option.
@ -83,6 +83,6 @@ app_net_ready="30s"
# the file 'magic.bin' to the UART availability during booting
#boot_resource="kangaroo"
# Add a script for custom initializations at sturtup
# Add a script for custom initializations at startup
# like starting a custom MQTT server, webcam steaming, etc.
startup_script="startup.sh"

4
patch.sh
View file

@ -90,13 +90,13 @@ for option in $options; do
echo -e "${RED}ERROR: Option '$option' requires option '$req_option' which is missing or not enabled. ${NC}"
exit 5
fi
echo -e "${GREEN}Option '$option' requires option '$req_option'. This requirement was successfuly validated. ${NC}"
echo -e "${GREEN}Option '$option' requires option '$req_option'. This requirement was successfully validated. ${NC}"
fi
done
done
echo ""
echo -e "${GREEN}DONE! The selected options are successfuly processed.${NC}\nYou may do manually more changes in the 'unpacked' folder if needed."
echo -e "${GREEN}DONE! The selected options are successfully processed.${NC}\nYou may do manually more changes in the 'unpacked' folder if needed."
echo ""
exit 0

2
unpack.sh
View file

@ -52,7 +52,7 @@ fi
rm -rf unpacked
mkdir unpacked
# preprocess the update file
# preprocessing the update file
if [ "$UPDATE_FILE_EXT" == "bin" ]; then
# decrypt the update if it is encrypted
$DECRYPT_TOOL -i "$UPDATE_FILE" -o ./unpacked/update.zip