xiaoxiang781216 commented on PR #6717:
URL: https://github.com/apache/incubator-nuttx/pull/6717#issuecomment-1198049014

   > ```
   > 1.3.428 CONFIG_BOARD_RESET_ON_ASSERT: Enable Board Reset after assert
   > Type: Integer
   > Default: 0
   > Dependencies: 
[CONFIG_LIB_BOARDCTL](https://cwiki.apache.org/confluence/display/NUTTX/Configuration+Variables#CONFIG_LIB_BOARDCTL),
 
[CONFIG_BOARDCTL_RESET](https://cwiki.apache.org/confluence/display/NUTTX/Configuration+Variables#CONFIG_BOARDCTL_RESET)
   > Kconfig file: ./boards/Kconfig
   > == 0 up_assert never reset the machine >= 1 up_assert from interrupt 
handler or IDLE thread will reset the
   > 
   > machine
   > >= 2 up_assert from user or kernel thread will reset the machine.
   > The default behavior is just to kill the asserting thread.
   > ```
   > 
   > What happens 
[here](https://github.com/apache/incubator-nuttx/pull/6717/files#diff-82074957e68b246b0d7fbfb7c73caa7d8d8af2239dbee25e99f80f5fb5bd2e58R470)
 line for CONFIG_BOARD_RESET_ON_ASSERT
   > 
   > Wouldn't the CPU reset before it tries the lock?
   
   Yes, this is what this patch want, I already high light in the commit 
message.


-- 
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: commits-unsubscr...@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to