SED&MED 3.5 Test inconclusive[MTD prebuilt lib]

[EIEI]

When we run test case SED&MED 3.5 ,  the following inconclusive result happens:

COM78 command: ot test tmforiginfilter disable
COM78 FUNC __executeCommand failed: Error 35: InvalidCommand
COM78 command: ot test tmforiginfilter disable
COM78 FUNC __executeCommand failed: Error 35: InvalidCommand
COM78 command: ot test tmforiginfilter disable

I see the cli cmd "test" is depends on OPENTHREAD_FTD. But the MTD prebuilt lib is not support OPENTHREAD_FTD.

So How did you solve this problem?

[Marte Myrvold]

Hi,

MTD and FTD are two different Thread device types: Minimal Thread Device (MTD) and Full Thread Device (FTD). If you want features only supported by FTD, then you must configure the device type as FTD in prj.conf. You must also make sure to enable the FTD OpenThread libraries:

CONFIG_OPENTHREAD_FTD=y
CONFIG_OPENTHREAD_NORDIC_LIBRARY_FTD=y

Best regards,
Marte

[EIEI]

HI  Marte Myrvold 

  I still don't know  why send udp need disable tmforiginfilter first, MTD is not support test cmd.

[Marte Myrvold]

Hi,

I assume this is from the test harness? Can you share where/how you found the scripts for the test harness? 
I do not see the "test tmforiginfilter disable" command in the send_udp() function in the THCI in the OpenThread repository:
https://github.com/openthread/openthread/blob/main/tools/harness-thci/OpenThread.py#L3044C9-L3052.

    @API
    def send_udp(self, interface, destination, port, payload='12ABcd'):
        ''' payload hexstring
        '''
        assert payload is not None, 'payload should not be none'
        assert interface == 0, "non-BR must send UDP to Thread interface"
        self.__udpOpen()
        time.sleep(0.5)
        cmd = 'udp send %s %s -x %s' % (destination, port, payload)
        return self.__executeCommand(cmd)[-1] == 'Done'

Best regards,
Marte

[EIEI]

HI, 

I found "test tmforiginfilter " in the THCI/OTNCS.py from the installed Testharness

[Marte Myrvold]

Hi,

The test command you are using is only enabled for golden devices in the Test Harness, i.e., a reference device that is known to behave according to the specification and which acts as a controlled peer in certification cases. The golden device is used alongside the DUT. These are devices with OPENTHREAD_CONFIG_REFERENCE_DEVICE_ENABLE enabled.

You should not use the Thread CLI sample in nRF Connect SDK with MTD libraries as the golden device in Test Harness. There are hex files for the golden device provided with the Test Harness.

Best regards,
Marte