Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
10 years ago.
is mbed rtos expected to build with the "ethernetinterface" because it doesnt work anymore.
Error: Too few arguments in invocation of macro "BW_MPU_CESR_VLD" in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 44, Col: 22 Error: Expected an expression in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 44, Col: 5 Warning: Function "clock_manager_set_gate" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 49, Col: 9 Error: Identifier "kClockModulePORT" is undefined in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 49, Col: 32 Warning: Function "port_hal_mux_control" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 53, Col: 5 Warning: Function "port_hal_configure_open_drain" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 60, Col: 5 Warning: Function "port_hal_pull_select" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 63, Col: 5 Warning: Function "port_hal_configure_pull" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 64, Col: 5 Warning: Function "clock_manager_set_gate" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 83, Col: 5 Error: Identifier "kClockModuleENET" is undefined in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 83, Col: 28 Warning: Function "clock_hal_set_clock_source" declared implicitly in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 86, Col: 5 Error: Identifier "kSimClockTimeSrc" is undefined in "EthernetInterface/lwip-eth/arch/TARGET_K64F/hardware_init_MK64F12.c", Line: 86, Col: 32
A program that worked perfectly well in august fallsover now.
Question relating to:
3 Answers
9 years, 2 months ago.
Hi guys, just tried to use EthernetInterface with the LPC1768 module + Application Board hardware and I'm at a complete loss. First it wants mbed-rtos, then it can't find error.h or something, and every time I'm adding more libraries with the "fix it" button, until I get a really cryptic "error 0" that I've got no clear way of solving.
This is really bothersome : the LPC1768 module is "the" MBED module, and the application board is most official piece of hardware there is. EthernetInterface is an official MBED library. If this can't be relied on to compile, then what's the point ? Arduino is more reliable than this. I suddenly miss my JTAG probe and my private stash of known-good code that no one can futz-up while I'm not looking...
10 years ago.
you need to update some libraries, like update ethernetinterface, update mbed-rtos, i hope you will fix it. If I am not wrong there is an issue with the latest mbed version. I came across with similar kind of problem, just update your libraries, replace mbed with mbed-src. I hope it will work.
10 years ago.
It is, we need to update EthernetInterface (= all it libraries which are inside).
thanks for reporting
It should be fixed now :-)
posted by mbed official 17 Dec 2014