-
Notifications
You must be signed in to change notification settings - Fork 56
Conversation
UBLOX_EVK_ODIN_W2 over ethernet will not work as Mbed OS 5.9 changed the way EMAC works. We have to use a different way to do the switch to ethernet with that board with Mbed OS 5.9 and onwards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now correct for 5.9.
Odin WiFi is now failing, in compilation phase.
That's not related to this PR, that's now the hidden dependency they've added with Mbed OS 5.9. Ref. Mbed OS PR #6963 |
This was already known and fixed in PAL: https://github.com/ARMmbed/mbed-client-pal/pull/490 |
Yes, unfortunately that fix does not work as-is here, since we are using a different PAL implementation. But, this should be trivial to fix. |
This is already legacy application so probably dropping those lines away from the TLS config is justified, it adds about 20 kB flash usage, but those example boards are not small. |
UBLOX_EVK_ODIN_W2 needs the RSA with Mbed OS 5.9 onwards, there is some internal dependency which failed the linking (due to Client optimizing the RSA out). Ref. Mbed OS PR #6963
One more commit, similar fix as in mbed-client-pal (but only slightly similar, as there is no |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ublox + WIFI + IAR causes hardfault:
14:57:21.199 | D1 <<< DutThread: ++ MbedOS Fault Handler ++
14:57:21.200 | D1 <<< DutThread: FaultType: HardFault
14:57:21.200 | D1 <<< DutThread: Context:
14:57:21.200 | D1 <<< DutThread: R0 : FFFFFFFF
14:57:21.201 | D1 <<< DutThread: R1 : 2002A33C
14:57:21.201 | D1 <<< DutThread: R2 : 00000000
14:57:21.202 | D1 <<< DutThread: R3 : 080E844C
14:57:21.203 | D1 <<< DutThread: R4 : 00000000
14:57:21.203 | D1 <<< DutThread: R5 : 080D0599
14:57:21.203 | D1 <<< DutThread: R6 : 00000000
14:57:21.204 | D1 <<< DutThread: R7 : 00000004
14:57:21.204 | D1 <<< DutThread: R8 : 00000000
14:57:21.204 | D1 <<< DutThread: R9 : 20008860
14:57:21.205 | D1 <<< DutThread: R10 : 00000000
14:57:21.205 | D1 <<< DutThread: R11 : 00000000
14:57:21.205 | D1 <<< DutThread: R12 : 080BFCA1
14:57:21.206 | D1 <<< DutThread: SP : 2000BEA0
14:57:21.206 | D1 <<< DutThread: LR : 080B6C1D
14:57:21.206 | D1 <<< DutThread: PC : 080D05A4
14:57:21.206 | D1 <<< DutThread: xPSR : 61000000
14:57:21.207 | D1 <<< DutThread: PSP : 2000BE80
14:57:21.207 | D1 <<< DutThread: MSP : 20006DE8
14:57:21.207 | D1 <<< DutThread: CPUID: 410FC241
14:57:21.207 | D1 <<< DutThread: HFSR : 80000000
14:57:21.207 | D1 <<< DutThread: MMFSR: 00000000
14:57:21.208 | D1 <<< DutThread: BFSR : 00000000
14:57:21.208 | D1 <<< DutThread: UFSR : 00000000
14:57:21.208 | D1 <<< DutThread: DFSR : 0000000A
14:57:21.208 | D1 <<< DutThread: AFSR : 00000000
14:57:21.209 | D1 <<< DutThread: SHCSR: 00000000
14:57:21.209 | D1 <<< DutThread: Mode : Thread
14:57:21.210 | D1 <<< DutThread: Priv : Privileged
14:57:21.210 | D1 <<< DutThread: Stack: PSP
14:57:21.210 | D1 <<< DutThread: Threads Info:
14:57:21.210 | D1 <<< DutThread: Current:
14:57:21.211 | D1 <<< DutThread: State: 0x00000002 Entry: 0x080BCD41 Stack Size: 0x00001000 Mem: 0x2000AF48 SP: 0x2000BED8
14:57:21.211 | D1 <<< DutThread: Next:
14:57:21.212 | D1 <<< DutThread: State: 0x00000002 Entry: 0x080BCD41 Stack Size: 0x00001000 Mem: 0x2000AF48 SP: 0x2000BED8
14:57:21.212 | D1 <<< DutThread: Wait:
14:57:21.212 | D1 <<< DutThread: State: 0x00000083 Entry: 0x08130139 Stack Size: 0x00000300 Mem: 0x20026BF0 SP: 0x20026E88
14:57:21.213 | D1 <<< DutThread: Delay:
14:57:21.303 | D1 <<< DutThread: State: 0x00000043 Entry: 0x080BCD41 Stack Size: 0x00000200 Mem: 0x200082A8 SP: 0x20008410
14:57:21.303 | D1 <<< DutThread: Idle:
14:57:21.304 | D1 <<< DutThread: State: 0x00000001 Entry: 0x080C20C1 Stack Size: 0x00000200 Mem: 0x20027C80 SP: 0x20027E30
14:57:21.304 | D1 <<< DutThread: -- MbedOS Fault Handler --
14:57:21.304 | D1 <<< DutThread: ++ MbedOS Error Info ++
14:57:21.304 | D1 <<< DutThread: Error Status: 0x80ff013d Code: 317 Entity: 255
14:57:21.305 | D1 <<< DutThread: Error Message: System encountered an unrecoverable fault excaption, halting system.
14:57:21.305 | D1 <<< DutThread: Location: 0x80d05a4
Oh darn. I would list it as a known issue. Wonder if the increased memory consumption is now causing some issues, out of stack or heap? |
Compilation job output.
Problem doesn't seem to be (on a quick glance) the size, as it's smaller than GCC binary (both RAM and ROM). |
@teetak01 Please create Jira ticket to ONME project, we have already one hard fault on Ublox, so this might be related. |
CC: @KariHaapalehto is this the same IAR crash? |
ONME-3692 |
Add link to the Mbed OS case for UBLOX_EVK_ODIN_W2 & IAR crash.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look fine to me @JanneKiiskila .. what about the hard fault with IAR + 5.9? Will it be fixed in time or add to known issues?
cc @adbridge @MarceloSalazar
@ashok-rao - there's an accompanying commit for the |
@adbridge : could we add this to the known issues list please. Thanks! |
@ashok-rao Known issues that are example based are listed in the example README, which from what @JanneKiiskila has said is already there (unless it is fixed before release). |
@adbridge @ashok-rao I am quite sure this is Mbed OS regression, which happens to appear as part of this example. It should be listed as Mbed OS regression also. |
UBLOX_EVK_ODIN_W2 over ethernet will not work as Mbed OS 5.9 changed
the way EMAC works. We have to use a different way to do the switch
to ethernet with that board with Mbed OS 5.9 and onwards.