Dmitry Bursov
/
mbed-os-ethattach-fault
eth.attach() doesn`t work with threads without wait time
Revision 0:074e782ef127, committed 2018-05-25
- Comitter:
- dimavb
- Date:
- Fri May 25 22:12:13 2018 +0000
- Commit message:
- init;
Changed in this revision
diff -r 000000000000 -r 074e782ef127 .gitignore --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/.gitignore Fri May 25 22:12:13 2018 +0000 @@ -0,0 +1,4 @@ +.build +.mbed +projectfiles +*.py*
diff -r 000000000000 -r 074e782ef127 README.md --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.md Fri May 25 22:12:13 2018 +0000 @@ -0,0 +1,57 @@ +# Getting started with Blinky on mbed OS + +This guide reviews the steps required to get Blinky working on an mbed OS platform. + +Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli). + +## Import the example application + +From the command-line, import the example: + +``` +mbed import mbed-os-example-blinky +cd mbed-os-example-blinky +``` + +### Now compile + +Invoke `mbed compile`, and specify the name of your platform and your favorite toolchain (`GCC_ARM`, `ARM`, `IAR`). For example, for the ARM Compiler 5: + +``` +mbed compile -m K64F -t ARM +``` + +Your PC may take a few minutes to compile your code. At the end, you see the following result: + +``` +[snip] ++----------------------------+-------+-------+------+ +| Module | .text | .data | .bss | ++----------------------------+-------+-------+------+ +| Misc | 13939 | 24 | 1372 | +| core/hal | 16993 | 96 | 296 | +| core/rtos | 7384 | 92 | 4204 | +| features/FEATURE_IPV4 | 80 | 0 | 176 | +| frameworks/greentea-client | 1830 | 60 | 44 | +| frameworks/utest | 2392 | 512 | 292 | +| Subtotals | 42618 | 784 | 6384 | ++----------------------------+-------+-------+------+ +Allocated Heap: unknown +Allocated Stack: unknown +Total Static RAM memory (data + bss): 7168 bytes +Total RAM memory (data + bss + heap + stack): 7168 bytes +Total Flash memory (text + data + misc): 43402 bytes +Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin +``` + +### Program your board + +1. Connect your mbed device to the computer over USB. +1. Copy the binary file to the mbed device. +1. Press the reset button to start the program. + +The LED on your platform turns on and off. + +## Troubleshooting + +If you have problems, you can review the [documentation](https://os.mbed.com/docs/latest/tutorials/debugging.html) for suggestions on what could be wrong and how to fix it.
diff -r 000000000000 -r 074e782ef127 main.cpp --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/main.cpp Fri May 25 22:12:13 2018 +0000 @@ -0,0 +1,50 @@ + +#include "EthernetInterface.h" +#include "mbed.h" +#include "nsapi_types.h" + +// Network interface +EthernetInterface eth; + +void status_callback(nsapi_event_t status, intptr_t param) +{ + printf("Connection status changed!\r\n"); + switch(param) { + case NSAPI_STATUS_LOCAL_UP: + printf("Local IP address set!\r\n"); + break; + case NSAPI_STATUS_GLOBAL_UP: + printf("Global IP address set!\r\n"); + break; + case NSAPI_STATUS_DISCONNECTED: + printf("No connection to network!\r\n"); + break; + case NSAPI_STATUS_CONNECTING: + printf("Connecting to network!\r\n"); + break; + default: + printf("Not supported"); + break; + } +} +void onemorethread(void) +{ + while (1) + { + // Thread::wait(10); + } +} + +int main() +{ + printf("Connecting...\n"); + eth.attach(&status_callback); + eth.set_network("192.168.1.200","255.255.255.0","192.168.1.1"); + eth.connect(); + Thread onemore; + onemore.start(onemorethread); + while(1) + { + Thread::wait(10); + } + } \ No newline at end of file
diff -r 000000000000 -r 074e782ef127 mbed-os.lib --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/mbed-os.lib Fri May 25 22:12:13 2018 +0000 @@ -0,0 +1,1 @@ +https://github.com/ARMmbed/mbed-os/#367dbdf5145f4d6aa3e483c147fe7bda1ce23a36