Which board A or B

libertypeter · May 14, 2024, 8:43pm

How do you tell the software that a particular board is in slot A or slot B?

hub.martin · May 15, 2024, 7:21am

Hell Peter,

in software you define it by using suffix _a or _b in the CMakeLists.txt, see

hardwario/chester-sdk/blob/main/applications/control/CMakeLists.txt#L10


      
          #
          # Copyright (c) 2023 HARDWARIO a.s.
          #
          # SPDX-License-Identifier: LicenseRef-HARDWARIO-5-Clause
          #
          
          cmake_minimum_required(VERSION 3.20.0)
          
          # Supported shields: ctr_lte_v2 ctr_x0_a ctr_s2 ctr_z ctr_ds18b20 ctr_x4_b
          set(SHIELD ctr_lte_v2 ctr_x0_a ctr_x4_b)
          
          set(ENV{FW_BUNDLE} "com.hardwario.chester.app.control")
          set(ENV{FW_NAME} "CHESTER Control")
          
          find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
          project(control)
          
          target_sources(app PRIVATE src/app_backup.c)
          target_sources(app PRIVATE src/app_cbor.c)
          target_sources(app PRIVATE src/app_config.c)

Then in your code for example for X0 in slot B, you have to use _b:
static const struct device *dev = DEVICE_DT_GET(DT_NODELABEL(ctr_x0_b));

A/B slot selection is important because X modules have different I2C address (if they use I2C) is slot B, usually readdressed by a solder bridge (ADR on silkscreen, see X0). Also CHESTER SDK is using 4 GPIO signals for each X module and this suffix tells driver which wires use.

I2C addresses for slot A/B are explained also in this table. See also the I2C scan command to help troubleshoot if you have configured the model in your slot correctly.

I see this is not explained in the documentation, I will add it soon there.

libertypeter · May 15, 2024, 4:46pm

Hub.Martin, thank you for this detailed description. Iwllgo thought it later today and will probably comment some more. I was having a problem with the ADC in slot B and have now solved the issue ( I will post that later also).