• State Not Answered
  • Replies 8 replies
  • Subscribers 88 subscribers
  • Views 679 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 349438
Options

Thingy:53 doesn't work with NRF7002EB shield

under_pressure

Hello, 

I've recently picked up Thingy 53 and NRF7002EB shield and wanted to play around with it, but I have a problem during project configuration. 

When I add -DSHIELD=nrf7002eb to cmake options during build the project doesn't build - using any sample. 

The error is: 

-- Application: /home/zdun8/ncs/v3.0.2/nrf/samples/nrf5340/empty_net_core
-- CMake version: 3.21.0
-- Found Python3: /home/zdun8/ncs/toolchains/7cbc0036f4/usr/local/bin/python (found suitable version "3.12.4", minimum required is "3.10") found components: Interpreter 
-- Cache files will be written to: /home/zdun8/.cache/zephyr
-- Zephyr version: 4.0.99 (/home/zdun8/ncs/v3.0.2/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
Loading Zephyr default modules (Zephyr base).
-- Board: thingy53, qualifiers: nrf5340/cpunet
-- Shield(s): nrf7002eb
-- Found host-tools: zephyr 0.17.0 (/home/zdun8/ncs/toolchains/7cbc0036f4/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/zdun8/ncs/toolchains/7cbc0036f4/opt/zephyr-sdk)
-- Found Dtc: /home/zdun8/ncs/toolchains/7cbc0036f4/usr/bin/dtc (found suitable version "1.5.0", minimum required is "1.4.6") 
-- Found BOARD.dts: /home/zdun8/ncs/v3.0.2/zephyr/boards/nordic/thingy53/thingy53_nrf5340_cpunet.dts
-- Found devicetree overlay: /home/zdun8/ncs/v3.0.2/zephyr/boards/shields/nrf7002eb/nrf7002eb.overlay
-- Configuring incomplete, errors occurred!
-- Configuring incomplete, errors occurred!
See also "/home/zdun8/projets/hello_world/build/CMakeFiles/CMakeOutput.log".
devicetree error: /home/zdun8/ncs/v3.0.2/zephyr/boards/shields/nrf7002eb/nrf7002eb.overlay:15 (column 1): parse error: undefined node label 'edge_connector_spi'
CMake Error at /home/zdun8/ncs/v3.0.2/zephyr/cmake/modules/dts.cmake:305 (execute_process):
  execute_process failed command indexes:

I debugged it a bit and it seems that for the thingy53 cpunet, there is no edge_connector_spi defined as for cpuapp. 

I know this shield is not supported for other devkits apart from Thingy 53 but it seems even for thingy 53 it's not the case.

I'm using SDK 3.0.2. 

Does anyone has an idea how to fix this?

Thanks!

Parents
  • 0

    Hi under_pressure,

    Could you please try again with -D<application_directory_name>_SHIELD=nrf7002eb instead?

    For example, -Dhello_world_SHIELD=nrf7002eb.

    The basis for my guess is: In the older paren-child multi-image build system, -DSHIELD would be only applied on the main image, which is almost always the application core, what you need. On the new system, Sysbuild, -DSHIELD will apply the shied files to all images. Therefore, the network core image, which shouldn't be involved, will have error because it cannot support what the shield needs.

    If you can confirm that, I will prompt our documentation team to fix the guides.

    Hieu

Reply
  • 0

    Hi under_pressure,

    Could you please try again with -D<application_directory_name>_SHIELD=nrf7002eb instead?

    For example, -Dhello_world_SHIELD=nrf7002eb.

    The basis for my guess is: In the older paren-child multi-image build system, -DSHIELD would be only applied on the main image, which is almost always the application core, what you need. On the new system, Sysbuild, -DSHIELD will apply the shied files to all images. Therefore, the network core image, which shouldn't be involved, will have error because it cannot support what the shield needs.

    If you can confirm that, I will prompt our documentation team to fix the guides.

    Hieu

Children
No Data
Related
Terms of service