- Sep 25, 2018
-
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
David Sidrane authored
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing.
-
- Sep 23, 2018
-
-
Daniel Agar authored
- nuttx in PX4/Firmware (f3cbd3c744e9224bd55597fbfae23c56ce296544): https://github.com/PX4-NuttX/nuttx/commit/98a89513060c42215e9cd14f52a7fd7dcc08dacc - nuttx current upstream: https://github.com/PX4-NuttX/nuttx/commit/e31e94f5bd3cf68b9ed0f010724ac9122730dd21 - Changes: https://github.com/PX4-NuttX/nuttx/compare/98a89513060c42215e9cd14f52a7fd7dcc08dacc...e31e94f5bd3cf68b9ed0f010724ac9122730dd21 e31e94f 2018-09-21 David Sidrane - [REJECTED] kinetis:usbdev use CONFIG_KINETIS_USBOTG_PRIO at default
-
- Sep 21, 2018
-
-
mcsauder authored
-
David Sidrane authored
-
- Sep 18, 2018
-
-
Matthias Grob authored
to make it non-blocking and ommit opening the same named pipe multiple times inside the same process which seems to be not supported in cygwin.
-
- Sep 16, 2018
-
-
Lukas Woodtli authored
- Environment variables for building with asan - Docker argument for leak sanitizer - Regex for tests to fail on sanitizer error Signed-off-by:
Lukas Woodtli <woodtli.lukas@gmail.com>
-
- Sep 14, 2018
-
-
David Sidrane authored
Bring UART4 bufffer sizes in alignment with FMUv2 Telem1
-
Roman authored
- if somebody tries to use the shell with insufficient permissions he will be told so Signed-off-by:
Roman <bapstroman@gmail.com>
-
- Sep 13, 2018
-
-
David Sidrane authored
-
- Sep 12, 2018
-
-
Daniel Agar authored
-
- Sep 08, 2018
-
-
Daniel Agar authored
-
- Sep 04, 2018
-
-
Daniel Agar authored
-
- Sep 02, 2018
-
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
- Sep 01, 2018
-
-
Daniel Agar authored
- nuttx in PX4/Firmware (0a1a2025402a387cde88132c6f8d8cc7237d2e6b): https://github.com/PX4-NuttX/nuttx/commit/bf8cce85c3f9310bcff8cdd1d979270419782a6e - nuttx current upstream: https://github.com/PX4-NuttX/nuttx/commit/e3b5b667aee16a699ecd6605f2d2a4adc6e95c17 - Changes: https://github.com/PX4-NuttX/nuttx/compare/bf8cce85c3f9310bcff8cdd1d979270419782a6e...e3b5b667aee16a699ecd6605f2d2a4adc6e95c17 e3b5b66 2018-08-31 Daniel Agar - [BACKPORT] Merged in dagar/nuttx/pr-stm32f7_stackcheck-upstream (pull request #714)
-
- Aug 31, 2018
-
-
David Sidrane authored
Use CONFIG_ARMV7M_STACKCHECK to add the instrumentation for runtime stack checking
-
David Sidrane authored
To enable coherent runtime stack checking use the boards CONFIG_ARMV7M_STACKCHECK setting
-
Beat Küng authored
Not needed anymore
-
Beat Küng authored
Generally exit() should not be used on Posix, because it exits the whole program instead of only the task.
-
- Aug 30, 2018
-
-
Daniel Agar authored
-
Bram Strack van Schijndel authored
-
Bram Strack van Schijndel authored
-