```
connectivity
├── netsocket
├── lwipstack
├── nanostack
│ ├── mbed_lib.json // nanostack-interface's mbed_lib.json
│ ├── include
│ │ └── nanostack // headers from features/netsocket/nanostack-interface
│ ├── source // sources from features/netsocket/nanostack-interface
│ ├── coap-service // used by Thread only - deprecate?
│ ├── mbed-mesh-api
│ ├── nanostack-hal-mbed-cmsis-rtos // HAL porting layer for Nanostack on mbed with CMSIS-RTOS
│ ├── sal-stack-nanostack
│ └── sal-stack-nanostack-eventloop
├── cellular // previously in features/cellular/framework/
├── ...
```
This PR is a part of a wider \connectivity refactoring and implements the above new directory structure for \nanostack.
- Public headers moved into mbed-os/connectivity/lwipstack/include/lwipstack folder
- Source moved into mbed-os/connectivity/lwipstack/source folder
- Internal lwip and lwip-sys libraries moved to source folder
Fixes two errors produced on except.S by the IAR assembler (as seen in
issue #13200).
The first: "'ALIGN' is illegal. Use directive ALIGNROM or ALIGNRAM (the
first parameter is raised to the power of 2, the second is a 32-bit fill
value)."
Fixed by changing ALIGN to ALIGNROM 2 to align to a 4-byte boundary
(mirroring what ALIGN does in the ARM except.S).
The second (on THUMB): "Must be placed inside a section"
Fixed by moving THUMB after the SECTION directive so that it affects
that section.
Mbed OS will soon be changing directory structure to the below:
```
[component name]
├── mbed_lib.json
├── CMakeList.txt
├── README.md
├── include
│ └── [component name]
│ └── internal
├── source
└── tests
├── <framework>
│ └── <test suite one>
├── UNITTESTS
│ └── <unit test suite one>
└── TESTS
└── <greentea test suite one>
```
This PR implements the above new directory structure for the current \platform directory.
**NOTE:** This PR does NOT include the refactoring of UNITTESTS as shown in the above directory structure. This will be done in a subsequent PR.
When manually flashing an application binary to the MULTITECH drive, a FAIL.TXT
file is produced with the following info:
“The application file format is unknown and cannot be parsed and/or processed”.