STM32 EMAC : increase thread size when mbed-trace is enabled

[jeromecoutant]

Summary of changes

Discussion started in #12561

Fix #12566

In case of mbed trace enable, stm32_emac_thread size has to be increased, in particular for GCC.

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[artokin]

Tested on my desk, still get a HardFault:

[ERR ][STE1]: HAL_ETH_Init issue

++ MbedOS Fault Handler ++

FaultType: HardFault

Context:
R0   : 70B002EB
R1   : 00000002
R2   : 00000518
R3   : 0800483F
R4   : 20018778
R5   : FFFFF43C
R6   : 0807189D
R7   : 00000000
R8   : 00000000
R9   : 00000000
R10  : 00000000
R11  : 00000000
R12  : 0806A84D
SP   : 20014E20
LR   : 080691B3
PC   : 08071774
xPSR : 210F0000
PSP  : 20014DB8
MSP  : 2007FFC0
CPUID: 411FC270
HFSR : 40000000
MMFSR: 00000000
BFSR : 00000082
UFSR : 00000000
DFSR : 0000000B
AFSR : 00000000
BFAR : 70B002EB
Mode : Thread
Priv : Privileged
Stack: PSP

-- MbedOS Fault Handler --



++ MbedOS Error Info ++
Error Status: 0x80FF013D Code: 317 Module: 255
Error Message: Fault exception
Location: 0x8071774
Error Value: 0x2005844C
Current Thread: nanostack_event_thread Id: 0x20014E78 Entry: 0x8020135 StackSize: 0x1800 StackMem: 0x20013678 SP: 0x20014E20
For more info, visit: https://mbed.com/s/error?error=0x80FF013D&tgt=DISCO_F769NI
-- MbedOS Error Info --

[artokin]

HardFault moved to another location.

[jeromecoutant]

HardFault moved to another location.

So let's integrate this patch ?

[artokin]

@jeromecoutant , the HardFault is still there. It happens slightly later but it must be fixed.

[artokin]

The new HardFault is caused by nanostack-border-router application as it is not able to handle failure in EthernetInterface creation. It will be fixed in PelionIoT/nanostack-border-router#209

The error mentioned in the log above [ERR ][STE1]: HAL_ETH_Init issue is caused by HAL_ETH_Init returning HAL_TIMEOUT. This error causes EthernetInterface creation failure and must be fixed.

[jeromecoutant]

Thx @artokin
So you have to open an new issue for that with your specific setup (as all netsocket tests are working with all ST boards with Ethernet connectors)

@0xc0170
Can we start CI ?

[artokin]

Thanks @jeromecoutant , the new issue is created: #12577

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

Summary: 1 of 7 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_cloud-client-pytest

[0xc0170]

Client restarted, once passed, will merge