VK_RZ_A1H: fatal error: EthernetInterface.h: No such file or directory

[bulislaw]

Version: mbed-os-5.1.0-rc5
OS: Mac
Toolchain: GCC
Board: VK_RZ_A1H

$ mbed compile -t GCC_ARM -m VK_RZ_A1H
Building project mbed-os-example-client (VK_RZ_A1H, GCC_ARM)
Scan: .
Scan: FEATURE_BLE
Scan: FEATURE_CLIENT
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_UVISOR
Scan: FEATURE_IPV4
Scan: FEATURE_IPV6
Scan: FEATURE_STORAGE
Scan: mbed
Scan: env
Compile: main.cpp
[ERROR] ./main.cpp:38:31: fatal error: EthernetInterface.h: No such file or directory
 #include "EthernetInterface.h"
                               ^
compilation terminated.

[mbed] ERROR: "python" returned error code 1.
[mbed] ERROR: Command "python -u /Users/barsza01/devel/mbed/mbed-os-example-client/mbed-os/tools/make.py -t GCC_ARM -m VK_RZ_A1H --source . --build ./.build/VK_RZ_A1H/GCC_ARM" in "/Users/barsza01/devel/mbed/mbed-os-example-client"

---

[yogpan01]

@bogdanm @sg- This seems to be mbed OS configuration issue for this platform. Can you check this please ?

[ciarmcom]

ARM Internal Ref: IOTCLT-890

[bogdanm]

VK_RZ_A1H is missing "features": ["IPV4"] from the target declaration, which is very likely the cause of the issue. However, I thought we were supposed to test for RZ_A1H, not for VK_RZ_A1H? @bulislaw

[bulislaw]

@bogdanm yes, it was my bad I have wrong board for the OoB. But shouldn't we support the VK_RZ_A1H?

[geky]

Hi @bulislaw, thanks for reporting this.

Looking into it more, it looks like the VK_RZ_A1H support for lwip, which is the stack gaurded by the FEATURE_IPV4.

Adding "features": ["IPV4"] to mbed-os/hal/target.json compiles fine, although I don't have a board to test on. @bulislaw, if you have a chance, would you be able to see if the mbed-os-example-client has any issues on this board? If not, I don't see any reason to not add the feature mainstream.

[bogdanm]

But shouldn't we support the VK_RZ_A1H?.

We should, but not right now. Right now we focus on the boards that we're supposed to test on, according to the OOB specs.

[geky]

@bogdanm's right, this is less of a priority, although I vote to leave this issue open until we get time to validate IPv4 on the VK_RZ_A1H

[geky]

I realized we did have a VK_RZ_A1H and I already had the setup so I went ahead and tried out the VK_RZ_A1H with the lwip tests and the mbed-os-example-client.

Looks like everything was fine, so I went ahead and made the pr to enable this feature: ARMmbed/mbed-os#2361

[sg-]

Awesome - thanks @geky