methodmissing commented on PR #20523: URL: https://github.com/apache/nuttx/pull/20523#issuecomment-6069013357
Repeated the due diligence run on the PX4 PR https://github.com/PX4/PX4-Autopilot/pull/28880 using NuttX 2.12.0 and ✅ ``` NuttShell (NSH) NuttX-12.12.0 nsh> nsh> remote_core status SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xc0de0003 (rpmsg ready), ipsr 0, kicks rx 4, msgs tx 4 cm4 application "basic" nsh> remote_core ping 100 64 INFO [remote_core] 100/100 replies, 64 byte payload INFO [remote_core] rtt min 27 us, avg 67 us, max 1668 us nsh> remote_core stop; remote_core start; remote_core ping 10 64 INFO [remote_core] 10/10 replies, 64 byte payload INFO [remote_core] rtt min 28 us, avg 132 us, max 680 us nsh> remote_core fault hardfault ERROR [remote_core] hardfault: no reply within 500 ms SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xdead0000 (FAULT), ipsr 3, kicks rx 15, msgs tx 14 cm4 application "basic" nsh> remote_core stop; remote_core start; remote_core ping 10 64 INFO [remote_core] 10/10 replies, 64 byte payload INFO [remote_core] rtt min 28 us, avg 31 us, max 45 us nsh> remote_core fault lockup ERROR [remote_core] lockup: no reply within 500 ms SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xdead0000 (FAULT), ipsr 3, kicks rx 15, msgs tx 14 cm4 application "basic" nsh> remote_core stop; remote_core start; remote_core ping 10 64 INFO [remote_core] 10/10 replies, 64 byte payload INFO [remote_core] rtt min 27 us, avg 37 us, max 114 us nsh> remote_core fault hang ERROR [remote_core] hang: no reply within 500 ms SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xc0de0003 (rpmsg ready), ipsr 0, kicks rx 14, msgs tx 14 cm4 application "basic" nsh> remote_core stop; remote_core start; remote_core ping 100 64 INFO [remote_core] 100/100 replies, 64 byte payload INFO [remote_core] rtt min 28 us, avg 51 us, max 661 us nsh> remote_core fault badused; remote_core ping 10 64 INFO [remote_core] cm4: badused: next host TX buffer comes back with used->len 0 SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xc0de0003 (rpmsg ready), ipsr 0, kicks rx 105, msgs tx 105 cm4 application "basic" INFO [remote_core] 10/10 replies, 64 byte payload INFO [remote_core] rtt min 29 us, avg 34 us, max 67 us nsh> remote_core fault badhdr; remote_core hello ERROR [remote_core] badhdr: no reply within 500 ms SRC SRSR 0x08010003 () SRMR 0x000000c0 M4 clock root control 0x00000400 status 0x00000400 (on) CM4 VTOR from LPSR GPR0/1: 0x20200000 (GPR0 0x00000000 GPR1 0x00002020) cm4 slice out of reset, SCR 0x00000001, vectors sp 0x20020000 pc 0x1ffe02ed cm4 state 0xc0de0003 (rpmsg ready), ipsr 0, kicks rx 116, msgs tx 116 cm4 application "basic" INFO [remote_core] cm7 -> cm4: "hello from cm7" INFO [remote_core] cm4 -> cm7: "hello from cm4 #111 (got: "hello from cm7")" ``` The system command API is not stable there yet - but the building blocks and this dependency is solid and I tried to bring some chaos monkey fault APIs and scenarios in first class -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
