Can't build hello app

John · April 1, 2025, 8:09pm

Following the lines on User manual 6.1 chapter 2.7

All good until the waf configure, I want to build for ZynqMP, so I use:

./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=aarch64/zymqmp_apu

and I get:

No valid arch/bsps found
(complete log in <path>/app/hello/build/config.log)

Although waf (the one in rtems source folder) shows it:

./waf bsplist
Regenerate build specification cache (needs a couple of seconds)...
aarch64/a53_ilp32_qemu
aarch64/a53_lp64_qemu
aarch64/a72_ilp32_qemu
aarch64/a72_lp64_qemu
aarch64/raspberrypi4b
aarch64/versal_aiedge
aarch64/versal_qemu
aarch64/versal_vck190
aarch64/zynqmp_apu
aarch64/zynqmp_apu_ilp32
aarch64/zynqmp_cfc400x
aarch64/zynqmp_qemu
aarch64/zynqmp_qemu_ilp32

but not waf where the hello source is

opticron · April 1, 2025, 8:19pm

Did you run ./waf install in the RTEMS source directory?

Does config.log provide any further clues?

JoelSherrill · April 2, 2025, 12:10am

If you are running this at the top of the rtems source tree, I wonder if providing a --rtems argument confuses things. It should be using the RTEMS in the current directory.

Also it is --rtems-bsps.

This is a link to the configure command my personal helper command builds up:

github.com/joelsherrill/rtems-cron-helpers

build_bsp

9500ef5be


      
                 sed \
                  -e "s/^RISCV_ENABLE_HTIF_SUPPORT =.*$/RISCV_ENABLE_HTIF_SUPPORT = True/" \
                  -e "s/^RISCV_CONSOLE_MAX_NS16550_DEVICES =.*$/RISCV_CONSOLE_MAX_NS16550_DEVICES = 0/"
                 ;;
               *)
                 cat
                 ;;
             esac >config-${CPU}-${BUILD_BSP}.ini
           check_status $? "generating config-${CPU}-${BUILD_BSP}.ini FAILED"
          
          ./waf configure \
            --rtems-tools=${RTEMS_TOOLS_DIR} \
            --rtems-bsps=${CPU}/${BUILD_BSP} \
            --out=b-${BUILD_BSP} \
            --prefix=${BSP_INSTALL} \
            --rtems-config=config-${CPU}-${BUILD_BSP}.ini >c-${CPU}-${BSP}.log 2>&1
           check_status $? "waf configure of ${CPU}/${BUILD_BSP} FAILED"
          
          time ./waf -j ${jobs} >b-${CPU}-${BSP}.log 2>&1
          status=$?

It certainly specifies arguments that can be defaulted but it gives an idea of one that works.

kiwichris · April 2, 2025, 5:00am

I think --rtems-bsps is redundant because you are supplying a config INI file and that will or should list the BSPs you are building.

I am not sure why we have --rtems-bsps and maybe it should be removed? We should encourage use of INI files.