Release candidate for mbed-os-5.4.6 #4356
Conversation
emac settings are only available after powered up. Signed-off-by: Tony Wu <[email protected]>
mbed_lwip_set_mac_address calls mbed_mac_address to get hwaddr from device, but device may not be accessible until it is powered up and initialized. This patch delays mbed_lwip_set_mac_address call until device is ready. Signed-off-by: Tony Wu <[email protected]>
The USB ISTR register consists of a mix of bits that are write-zero-to-clear and read only bits. As such, to clear a bit in the ISTR, you should simply write the bitwise-NOT of the bit to clear. Previously, the __HAL_PCD_CLEAR_FLAG() macro would do a bitwise-AND with the ISTR register contents to clear a bit, but this could result in another bit being inadvertently cleared if it is set by hardware between the read and the write of the ISTR register. Similarly, the USB endpoint registers have two bits that are write-zero-to-clear, USB_EP_CTR_RX and USB_EP_CTR_TX, but the PCD_CLEAR_RX_EP_CTR() and PCD_CLEAR_TX_EP_CTR() macros wrote back the last read value for one of these bits when clearing the other bit. This could result in inadvertent clearing of one of these bits if it were set by the hardware between the read and the write. These macros have now both been adjusted to always write one to the bit not being cleared to prevent inadvertent clears.
use Intelhex::write_hex_file instead of IntelHex::tofile
… gnuarmeclipse and makefile exporter.
Change the irq_handler parameter of NVIC_SetVector from a function pointer to a uin32_t so it matches the cmsis specification. This prevents the following problem from occurring in RTX5 when building for IAR: The error: Error[Pe167]: argument of type "void (*)(void)" is incompatible with parameter of type "uint32_t".
…he code for mbed ci shield test -> analogin_api.c, W7500x_adc.c, gpio_irq_api.c, W7500x_gpio.c Modifying the code for fix bug -> W7500x_uart.c(register control driver problem), W7500x_uart.h, pinmap.c(pullup, pulldown problem)
|
/morph test-nightly |
|
/morph mbed2-release |
|
/morph export-build |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputExample Prep failed! |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 36 Exporter Build failed! |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
|
/morph test-nightly |
|
/morph export-build |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 37 Exporter Build failed! |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputExample Build failed! |
|
Still problems with exporters! |
|
Example build also still failing for NRF52_DK @pan- @theotherjimmy (looks like your fix Jimmy didn't quite fix everything ? ) |
|
nordic and iar exporters issue - #4349 so all issues are IAR related? |
|
Yeah all issues seem to be IAR related |
|
@JanneKiiskila The patch release follows the normal published schedule, ie meaning the release is due tomorrow. However we're currently being delayed by some Nordic issues causing CI failures and thus are gating the release candidate. @pan- is looking at them . As soon as we can get them fixed and get the candidate passing the CI tests, then there will be an examples update , followed ~1 day later by the release itself. |
|
/morph test-nightly |
|
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 42 All exports and builds passed! |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
|
retest uvisor |
|
/morph test-nightly |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
@adbridge All green ! |
|
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
No description provided.