adding USTICKER label in C027 device has: #7169
Conversation
|
log.txt |
|
awesome to review logs here as well, IAR and ARMCC tested? |
|
let me add ARM and IAR test log as well log_arm.txt |
|
/morph build |
Build : SUCCESSBuild number : 2306 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1928 |
Test : FAILUREBuild number : 2083 |
|
/morph test |
Test : SUCCESSBuild number : 2086 |
|
/morph mbed2-build |
|
That's a shame. This is going to need a rebase. |
|
This seems to be rebased but for one definition addition 4 commits, can you squash it into one please? |
|
i will try but commits are non-contiguous so would it be possible to squash into one? |
|
@aqib-ublox It should be fine. Imaginge your branch as a set of diffs applied one at a time. A quick way to do the squash would be to do a soft reset to the head of the base commit of the branch, keeping your changes intact but allowing you to gather all of the changes in a single commit. |
|
@cmonr you suggested a solution but again i want to say commits are non-contigous i can only combine last two commits plz see commits.txt |
|
@aqib-ublox Looking at the changes here. they are quite small, 1 line affected, might be easiest to reset your branch (hard one) and create a new commit. (I noticed you also removed EMAC? bad conflict resolution?) Let's just do not spend more time for something that simple. |
Nanostack object constructor didn't actually initialise Nanostack. Nanostack initialisation was deferred until an interface was actually attached to the stack, which generally happened at first interface connect. Not normally a problem, unless you're trying to make direct Nanostack setup calls prior to connect - some applications do this, and were relying on ThreadInterface::initialise to do Nanostack initialisation. Unfortunately in 5.9 ThreadInterface::initialise no longer does initialise Nanostack immediately, because the mesh interfaces were aligned and integrated with the Ethernet interfaces, which did initialisation on connect(). Make the Nanostack object constructor initialise Nanostack (as the LWIP constructor does for lwIP), so calling Nanostack::get_instance() is the 5.9 API for Nanostack initialisation. For future work, APIs like ns_file_system_set_root_path should be exposed as methods of Nanostack, so everything happens with a single Nanostack::get_instance().file_system_set_root_path().
### Description Full paths in the map file are required to have correct memap parsing. This PR adds the option `--show_full_path` to ARMC6 in every profile. This option only affects the map file output, so it's safe to add.
- set ppp_active false if close fails in ppp disconnect. - unset sigio in ppp disconnect - take ownership of filehandle in CellularNetwork::disconnect even in case of failure
Update test configuration file for WicedInterface
The nrf section features has different implementations for each compilers supported by mbed-os. The header guard was ruling out compiler other than GCC by checking if __GNUC__ is defined. This check is not applicable on mbed os as the ARM compiler compile sources with gnu compatibility. This patch makes sure that the right implementation is selected for the right compiler . The previous patch has been reverted as it is not reliable.
Updated EMAC memory manager to use libservice nsdynmemlib for EMAC memory buffers. Located the nsdynmemlib buffer heap to DMA safe memory bank on LPCxx boards. Optimized placement of static variables on EMAC test environment for LPCxx boards to maximize available memory.
Changed RX and TX buffers used in TCP socket tests to global variables to conserve memory.
For details see: http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s130.sds%2Fdita%2Fsoftdevices%2Fs130%2Fmem_usage%2Fmem_resource_reqs.html Set the ram start to 0x20002ef8 to be consistent with ATM_STD and IAR linker scripts
…orm: MCU_NRF51_16K_UNIFIED_S130 Add target definition for Raytac MDBT40 module to use the MCU_NRF51_16K_UNIFIED_S130 target.
Previously get_mac_address on a ThreadInterface returned the EUI-64 reported by the radio driver. This was required for commissioning, but was inconsistent with other interfaces, and the API concept. 5.9.0 inadvertently changed this so that get_mac_address returned the actual MAC address used by the radio, which is a hash result of the EUI-64 for Thread. The original "return the EUI-64" form was somewhat faulty, as get_mac_address would not return the EUI-64 set by set_device_eui64() or another mechanism before connect() was called. Rather than revert to old behaviour, add a new API to get the device EUI-64 to ThreadInterface, alongside the existing set API.
Set correct SYSMPU register for proper USB operation. This bug was introduced when the SYSMPU register names and defines were updated in the commit: "K64F: Updated the SYSMPU SDK driver" 93f8cfe
Share IPv6 conversion code with mbed_trace, Nanostack and mbed client. Output formatting is better, being conformant to RFC 5952.
Two cascading copy-paste errors stopped this working:
* PPPCellularInterface::get_gateway() called
nsapi_ppp_get_ip_address();
* nsapi_ppp_get_gateway() called the interface's get_netmask().
First bug has always been there - second one was introduced in 5.9.
AT_CellularNetwork currently lacks calls to get both netmask and gateway
- this patch would be needed for that when added.
|
#7291 closing PR and open other PR |
Description
Added a label USTICKER for C027 as us_ticker new implemnaation is adopted for LPC176x targets and locally tests are passing with this changeset.
Pull request type