Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
Qt for MCUs 1.9
-
Sprint 4.1/2021
Description
the flash_targetname is broken in RH850 D1M1A when using QtCreator.
In the 1.9 version, the eflashload_config.xml and image files are placed as below:
├─Release
│ ├─flash_automotive.run
│ ├─flash_automotive_external_flash.s
│ └─flash_automotive_internal_flash.s
└─ eflashload_config.xml
when building flash_targetname it will give a JOM error.
jom: C:\works\build-Qt_for_MCUs_1_9_RH850_D1M1A_BAREMETAL_32bpp_GHS-Debug\CMakeFiles\flash_automotive.dir\build.make [CMakeFiles\flash_automotive] Error 2 jom: C:\works\build-Qt_for_MCUs_1_9_RH850_D1M1A_BAREMETAL_32bpp_GHS-Debug\CMakeFiles\Makefile2 [CMakeFiles\flash_automotive.dir\all] Error 2 jom: C:\works\build-Qt_for_MCUs_1_9_RH850_D1M1A_BAREMETAL_32bpp_GHS-Debug\CMakeFiles\Makefile2 [CMakeFiles\flash_automotive.dir\rule] Error 2 jom: C:\works\build-Qt_for_MCUs_1_9_RH850_D1M1A_BAREMETAL_32bpp_GHS-Debug\Makefile [flash_automotive] Error 2 14:22:54: The process "C:\Qt\Tools\CMake_64\bin\cmake.exe" exited with code 2. Error while building/deploying project (kit: Qt for MCUs 1.9 - RH850-D1M1A-BAREMETAL 32bpp (GHS)) The kit Qt for MCUs 1.9 - RH850-D1M1A-BAREMETAL 32bpp (GHS) has configuration issues which might be the root cause for this problem.
Move the eflashload_config.xml into the Release folder solved it.
Attachments
Issue Links
- mentioned in
-
Page Loading...