NA6 ini is not uploaded fix #2649

.github/workflows/readme.md

@@ -25,3 +25,5 @@ This is not a complete diagram of all workflows, nor does it show everything tha
           +              +                       +                 +
 Firmware Push            Gen Config      Unit Tests       Firmware PR
 ```
+
+https://github.com/rusefi/rusefi/wiki/Build-Server-and-Automation

firmware/gen_config_board.sh

@@ -41,7 +41,7 @@ java -DSystemOut.name=gen_config_board \
 # todo: make things consistent by
 # 0) having generated content not in the same folder with the tool generating content?
 # 1) using unique file name for each configuration?
-# 2) leverage consistent caching mechanism so that image is generted only in case of fresh .ini. Laziest approach would be to return exit code from java process above
+# 2) leverage consistent caching mechanism so that image is generated only in case of fresh .ini. Laziest approach would be to return exit code from java process above
 #
 ./hw_layer/mass_storage/create_ini_image.sh ./tunerstudio/generated/rusefi_${SHORT_BOARDNAME}.ini ./hw_layer/mass_storage/ramdisk_image.h
 ./hw_layer/mass_storage/create_ini_image_compressed.sh ./tunerstudio/generated/rusefi_${SHORT_BOARDNAME}.ini ./hw_layer/mass_storage/ramdisk_image_compressed.h

firmware/tunerstudio/upload_ini.sh

@@ -15,7 +15,7 @@ for f in *.ini; do if [[ -f "$f" ]]; then
   sig=$(grep "^ *signature *=" $f | cut -f2 -d "=")
   if [ ! -z "$sig" -a "$sig" != " " ]; then
     echo "* found signature: $sig"
-    if [[ "$sig" =~ rusEFI.*([0-9]{4})\.([0-9]{2})\.([0-9]{2})\.([a-z0-9_]+)\.([0-9]+) ]]; then
+    if [[ "$sig" =~ rusEFI.*([0-9]{4})\.([0-9]{2})\.([0-9]{2})\.([a-zA-Z0-9_]+)\.([0-9]+) ]]; then
       year=${BASH_REMATCH[1]}
       month=${BASH_REMATCH[2]}
       day=${BASH_REMATCH[3]}