The compilation of the mm-iot-zephyr porting_assistant program has failed.

Software
1

Compilation of m2m_u575 has failed.
1.Execute the command as follows：

west build -p auto -b m2m_u575 modules/lib/morsemicro/samples/porting_assistant

2.Error log：

-- Found GnuLd: /home/jonathan/.local/zephyr-sdk-0.16.9/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version “2.38”)

-- The C compiler identification is GNU 12.2.0

-- The CXX compiler identification is GNU 12.2.0

-- The ASM compiler identification is GNU

-- Found assembler: /home/jonathan/.local/zephyr-sdk-0.16.9/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc

-- Using ccache: /usr/bin/ccache

-- Configuring done

CMake Error in /home/jonathan/mm-iot-zephyr-workspace/modules/lib/morsemicro/components/morse_fs/libmorse/CMakeLists.txt:

IMPORTED_LOCATION not set for imported target “libmorse”.

CMake Error in /home/jonathan/mm-iot-zephyr-workspace/modules/lib/morsemicro/components/morse_fs/libmorse/CMakeLists.txt:

IMPORTED_LOCATION not set for imported target “libmorse”.

CMake Error in /home/jonathan/mm-iot-zephyr-workspace/modules/lib/morsemicro/components/morse_fs/libmorse/CMakeLists.txt:

IMPORTED_LOCATION not set for imported target “libmorse”.

Does anyone know what the reason is?

2

Hi @Jonathan

Our porting assistant application is designed to check that the bus and abstraction layer implementations (shims) are functioning correctly for the morse_sm driver. Running the porting_assistant application on the morse_fs driver is a combination that won’t work.

We will update the porting assistant to be more aggressive on forcing the use of the morse_sm driver, so the m2m_u575 build fails here.

I’m interested to know more about what you’re doing if you’re using the m2m_u575, are you able to share more information?

3

I am currently running the FGH100M Halow module on the STM32U575. Thank you！

4

Is this a custom board, or is it a nucleo-u575 and a shield provided by Quectel?

If a nucleo-u575 and a shield, you’ll need to define the shield in the boards directory of modules/lib/morsemicro/boards and then build with west build -b nucleo_u575zi_q --shield <shield name> modules/lib/morsemicro/samples/porting_assistant
For a reference shield definition, have a look at morse_mmech08 :slight_smile:

If it is a custom board, you will need to define the board target with device tree in modules/lib/morsemicro/boards and then build with that board name.
Have a look at how our EKH05 board is defined for reference :slight_smile:

For more information, take a look at Zephyr’s board porting guide, available here: https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html
and for more information about shields, have a look at this: Shields — Zephyr Project Documentation

Let me know if you have any issues!