HELPDESK_WJ (Waijung)

Could you please share the build status message with the error message?

Thank you.

1. Starting build procedure for: CntrlVelMotor
2. Generating code and artifacts to 'Model specific' folder structure
3. Generating code into build folder: C:\Users\MARINA\Desktop\UNIVERSIDAD\TFG_NO\ProgramasSimulink\Control_Vel_Motor\CntrlVelMotor_esp32
   The model reference sample time inheritance rule for block 'CntrlVelMotor/MCPWM Control' is not set and the model is sample time independent. The generated code from the block might produce incorrect results if it is referenced by a Model block. For S-functions, specify the model reference sample time inheritance rule through the ssSetModelReferenceSampleTimeInheritanceRule macro. You can suppress the diagnostic by setting Unspecified inheritability of sample time to 'none'. [4 similar]
   Component:Simulink | Category:Block warning
4. Invoking Target Language Compiler on CntrlVelMotor.rtw
5. Using System Target File: C:\waijung2_22.2c\waijung2\targets\esp32\esp32.tlc
6. Loading TLC function libraries
7. Generating TLC interface API for custom data
   .
8. Initial pass through model to cache user defined code
   .
9. Caching model source code ### Writing header file CntrlVelMotor_types.h
   . ### Writing header file waijung2_hwdrvlib.h ### Writing source file waijung2_hwdrvlib.c ### Writing header file CntrlVelMotor.h ### Writing header file rtwtypes.h ### Writing source file CntrlVelMotor.c
   . ### Writing header file CntrlVelMotor_private.h ### Writing header file rtmodel.h ### Writing source file ert_main.c
10. TLC code generation complete.
    .
11. Processing Template Makefile: C:\waijung2_22.2c\waijung2\targets\esp32\src\esp32.tmf
    Warning: The following preprocessor macros
    MODEL_HAS_DYNAMICALLY_LOADED_SFCNS
    are specified in the component's build information (RTW.BuildInfo) but the specified template makefile
    C:\waijung2_22.2c\waijung2\targets\esp32\src\esp32.tmf
    does not contain the token |>DEFINES_OTHER<|. [3 similar]
12. Created makefile C:\Users\MARINA\Desktop\UNIVERSIDAD\TFG_NO\ProgramasSimulink\Control_Vel_Motor\CntrlVelMotor_esp32\CntrlVelMotor.mk
13. Building CntrlVelMotor: .\CntrlVelMotor.bat

C:\Users\MARINA\Desktop\UNIVERSIDAD\TFG_NO\ProgramasSimulink\Control_Vel_Motor\CntrlVelMotor_esp32>set MATLAB=C:\Program Files\MATLAB\R2020

1. BUILD_MODE : real_time
2. PRODUCT : CntrlVelMotor.out
3. SHRLIBTARGET : 0
4. MODULES : waijung2_hwdrvlib.c
5. MODELREF_TARGET_TYPE : NONE
6. MAKEFILEBUILDER_TGT : 0
7. STANDALONE_SUPPRESS_EXE : 0
8. Source waijung2_hwdrvlib.c done
9. Source CntrlVelMotor.c done
10. Ending CntrlVelMotor.out real_time
11. Created CntrlVelMotor.out successfully (or it was already up to date)
12. Successful completion of build procedure for: CntrlVelMotor
    Waijung 2: Post processing started.
    Waijung 2: Deleting pre-built src files.
    Waijung 2: Copying required header and source files to the target build directory.
    1. wj2_blockref checked
       Waijung 2: Auto compile and download process started
       [1/11] Performing build step for 'bootloader'
       [1/1] cmd.exe /C "cd /D C:\Users\MARINA\Desktop\UNIVERSIDAD\TFG_NO\ProgramasSimulink\Control_Vel_Motor\CntrlVelMotor_esp32_build_system\build\bootloader\esp-idf\esptool_py && C:\waijung2_22.2c\waijung2\targets\esp32\setup\.espressif\python_env\idf4.4_py3.8_env\Scripts\python.exe C:/waijung2_22.2c/waijung2/targets/esp32/setup/esp_idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x1000 C:/Users/MARINA/Desktop/UNIVERSIDAD/TFG_NO/ProgramasSimulink/Control_Vel_Motor/CntrlVelMotor_esp32_build_system/build/bootloader/bootloader.bin"
       Bootloader binary size 0x62d0 bytes. 0xd30 bytes (12%) free.
       [2/9] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/CntrlVelMotor.c.obj
       [3/9] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/waijung2_hwdrvlib.c.obj
       [4/9] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/ert_main.c.obj
       [5/9] Linking C static library esp-idf\main\libmain.a
       [6/9] Generating ld/sections.ld
       [7/9] Linking CXX executable waijung2_esp32.elf
       [8/9] Generating binary image from built executable
       esptool.py v3.2-dev
       Merged 2 ELF sections
       Generated C:/Users/MARINA/Desktop/UNIVERSIDAD/TFG_NO/ProgramasSimulink/Control_Vel_Motor/CntrlVelMotor_esp32_build_system/build/waijung2_esp32.bin
       [9/9] cmd.exe /C "cd /D C:\Users\MARINA\Desktop\UNIVERSIDAD\TFG_NO\ProgramasSimulink\Control_Vel_Motor\CntrlVelMotor_esp32_build_system\build\esp-idf\esptool_py && C:\waijung2_22.2c\waijung2\targets\esp32\setup\.espressif\python_env\idf4.4_py3.8_env\Scripts\python.exe C:/waijung2_22.2c/waijung2/targets/esp32/setup/esp_idf/components/partition_table/check_sizes.py --offset 0x8000 partition --type app C:/Users/MARINA/Desktop/UNIVERSIDAD/TFG_NO/ProgramasSimulink/Control_Vel_Motor/CntrlVelMotor_esp32_build_system/build/partition_table/partition-table.bin C:/Users/MARINA/Desktop/UNIVERSIDAD/TFG_NO/ProgramasSimulink/Control_Vel_Motor/CntrlVelMotor_esp32_build_system/build/waijung2_esp32.bin"
       waijung2_esp32.bin binary size 0x2b5d0 bytes. Smallest app partition is 0x200000 bytes. 0x1d4a30 bytes (92%) free.
       Executing action: all (aliases: build)
       Running ninja in directory c:\users\marina\desktop\universidad\tfg_no\programassimulink\control_vel_motor\cntrlvelmotor_esp32_build_system\build
       Executing "ninja all"...

1. Build procedure for CntrlVelMotor aborted due to an error.
   Build Summary 1
   Elapsed: 0.17 sec
   Top model targets built:

Model Action Rebuild Reason ========================================================
CntrlVelMotor Failed CntrlVelMotor.c does not exist.

0 of 1 models built (0 models already up to date)
Build duration: 0h 0m 44.049s
The call to esp32_make_rtw_hook, during the exit hook generated the following error:
An error occurred in Auto compile and download process. Please refer the log data above.

The build process will terminate as a result.
Caused by:
An error occurred in Auto compile and download process. Please refer the log data above.
Component:Simulink | Category:Block diagram error

Hello Marina,

Thank you for reaching out and using Waijung 2 block set. There is nothing wrong with your model or the generated code. I was able to compile and download your model to an ESP32 board. However, the ESP32 that I used is from a different manufacturer as we do not have your exact model at the moment.

When looking at your build log, it seems to me that your error occurs while flashing: " A fatal error occurred: MD5 of file does not match data in flash! "

Have you ever managed to flash a program to your ESP32 (LILYGO TTGO T7 v1.3 mini 32 ESP32) using Waijung 2 or even directly using ESP-IDF before? Have you tried the model you have attached with an ESP32 from a different manufacturer?

Best Regards,
Dhanika

Hello
I have managed to flash some programs before that program, and all compiled ok. Even this program compiled ok at the beginning but the error I have asked you appreared another day when i wanted to try again.
I have no tried the model with an ESP32 from a different manufactures because i have only that ESP32 from LILYGO.
Thanks
Marina

Hello Marina,

• Delete all the build folders and do a fresh build.
• Try the Simulink model you attached with an ESP32 from a different manufacturer.

Kind Regards,
Dhanika