Oopenvela-robotarm_m: merge arm/include/armv6/7/8-m/nvicpri.h into arm_m
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Merge remote-tracking branch 'mirtos/master' into dev-upmerge-nuttx-10.1-0507 Signed-off-by: liuhaitao <liuhaitao@xiaomi.com> | 2 个月前 | |
Add initial support for the QuickLogic EOS S3 The QuickFeather board added as an initial target. These featrues are minimally implemented: * Clock Configuration -- All clocking registers are defined and configuration is used to setup the HSO, M4 Core, and M4 Perif clocks. Additionally some clock debugging is stubbed for bringing out clock paths to IO pins. * UART -- The lowputc as well as the serial driver is implemnted for the single UART device. Currently the configuration is hard coded, but uses the proper interfaces to later fill in. * SysTick -- The system tick timer is implemented and clocking properly. Tickless mode is not yet implemented. * Interrupts -- The interrupt system is implemented and verified using the UART and SysTick systems. * GPIO -- GPIO and IOMUX systems are defined and implemented. This is verified using the UART as well as the Arch LED system. The GPIO interupt system is stubbed out but not implemented. * Arch LEDS -- The blue LED as part of the RGB LED is configured and attached to the Arch LED system. This indicates the device coming online as well as when a hardfault is triggered. Applications and Testing: * There is a nsh configuration implemented that includes debug features as well as the ostest, getprime, and mem test. All of these have been run and verified. Signed-off-by: Brennan Ashton <bashton@brennanashton.com> | 2 个月前 | |
arch/cortex-m/Make.defs: unify arch common source include Signed-off-by: chao.an <anchao@xiaomi.com> | 2 个月前 | |
Add initial support for the QuickLogic EOS S3 The QuickFeather board added as an initial target. These featrues are minimally implemented: * Clock Configuration -- All clocking registers are defined and configuration is used to setup the HSO, M4 Core, and M4 Perif clocks. Additionally some clock debugging is stubbed for bringing out clock paths to IO pins. * UART -- The lowputc as well as the serial driver is implemnted for the single UART device. Currently the configuration is hard coded, but uses the proper interfaces to later fill in. * SysTick -- The system tick timer is implemented and clocking properly. Tickless mode is not yet implemented. * Interrupts -- The interrupt system is implemented and verified using the UART and SysTick systems. * GPIO -- GPIO and IOMUX systems are defined and implemented. This is verified using the UART as well as the Arch LED system. The GPIO interupt system is stubbed out but not implemented. * Arch LEDS -- The blue LED as part of the RGB LED is configured and attached to the Arch LED system. This indicates the device coming online as well as when a hardfault is triggered. Applications and Testing: * There is a nsh configuration implemented that includes debug features as well as the ostest, getprime, and mem test. All of these have been run and verified. Signed-off-by: Brennan Ashton <bashton@brennanashton.com> | 2 个月前 | |
Add initial support for the QuickLogic EOS S3 The QuickFeather board added as an initial target. These featrues are minimally implemented: * Clock Configuration -- All clocking registers are defined and configuration is used to setup the HSO, M4 Core, and M4 Perif clocks. Additionally some clock debugging is stubbed for bringing out clock paths to IO pins. * UART -- The lowputc as well as the serial driver is implemnted for the single UART device. Currently the configuration is hard coded, but uses the proper interfaces to later fill in. * SysTick -- The system tick timer is implemented and clocking properly. Tickless mode is not yet implemented. * Interrupts -- The interrupt system is implemented and verified using the UART and SysTick systems. * GPIO -- GPIO and IOMUX systems are defined and implemented. This is verified using the UART as well as the Arch LED system. The GPIO interupt system is stubbed out but not implemented. * Arch LEDS -- The blue LED as part of the RGB LED is configured and attached to the Arch LED system. This indicates the device coming online as well as when a hardfault is triggered. Applications and Testing: * There is a nsh configuration implemented that includes debug features as well as the ostest, getprime, and mem test. All of these have been run and verified. Signed-off-by: Brennan Ashton <bashton@brennanashton.com> | 2 个月前 | |
dns: fix dns failed when ipv4/6 dual stack enable The ipv6 address filled the cache, and the ipv4 address did not have a place to store it, causing the resolution to fail. so if IPV6 has already filled the buffer, rewrite ipv4 DNS results from half of the buffer. Signed-off-by: zhanghongyu <zhanghongyu@xiaomi.com> | 2 个月前 | |
Merge remote-tracking branch 'mirtos/master' into dev-upmerge-nuttx-10.1-0507 Signed-off-by: liuhaitao <liuhaitao@xiaomi.com> | 2 个月前 | |
gpio: use small lock to protect configgpio reason: We would like to replace the critical section with a small lock. Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
Add initial support for the QuickLogic EOS S3 The QuickFeather board added as an initial target. These featrues are minimally implemented: * Clock Configuration -- All clocking registers are defined and configuration is used to setup the HSO, M4 Core, and M4 Perif clocks. Additionally some clock debugging is stubbed for bringing out clock paths to IO pins. * UART -- The lowputc as well as the serial driver is implemnted for the single UART device. Currently the configuration is hard coded, but uses the proper interfaces to later fill in. * SysTick -- The system tick timer is implemented and clocking properly. Tickless mode is not yet implemented. * Interrupts -- The interrupt system is implemented and verified using the UART and SysTick systems. * GPIO -- GPIO and IOMUX systems are defined and implemented. This is verified using the UART as well as the Arch LED system. The GPIO interupt system is stubbed out but not implemented. * Arch LEDS -- The blue LED as part of the RGB LED is configured and attached to the Arch LED system. This indicates the device coming online as well as when a hardfault is triggered. Applications and Testing: * There is a nsh configuration implemented that includes debug features as well as the ostest, getprime, and mem test. All of these have been run and verified. Signed-off-by: Brennan Ashton <bashton@brennanashton.com> | 2 个月前 | |
Merge remote-tracking branch 'mirtos/master' into dev-upmerge-nuttx-10.1-0507 Signed-off-by: liuhaitao <liuhaitao@xiaomi.com> | 2 个月前 | |
arm_m: merge arm/include/armv6/7/8-m/nvicpri.h into arm_m We should reduce the dup of code Signed-off-by: buxiasen <buxiasen@xiaomi.com> | 2 个月前 | |
arch: Merge up_arch.h into up_internal.h neededby:partner_4262 Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 | |
Add initial support for the QuickLogic EOS S3 The QuickFeather board added as an initial target. These featrues are minimally implemented: * Clock Configuration -- All clocking registers are defined and configuration is used to setup the HSO, M4 Core, and M4 Perif clocks. Additionally some clock debugging is stubbed for bringing out clock paths to IO pins. * UART -- The lowputc as well as the serial driver is implemnted for the single UART device. Currently the configuration is hard coded, but uses the proper interfaces to later fill in. * SysTick -- The system tick timer is implemented and clocking properly. Tickless mode is not yet implemented. * Interrupts -- The interrupt system is implemented and verified using the UART and SysTick systems. * GPIO -- GPIO and IOMUX systems are defined and implemented. This is verified using the UART as well as the Arch LED system. The GPIO interupt system is stubbed out but not implemented. * Arch LEDS -- The blue LED as part of the RGB LED is configured and attached to the Arch LED system. This indicates the device coming online as well as when a hardfault is triggered. Applications and Testing: * There is a nsh configuration implemented that includes debug features as well as the ostest, getprime, and mem test. All of these have been run and verified. Signed-off-by: Brennan Ashton <bashton@brennanashton.com> | 2 个月前 | |
arch/arm: fix compile error. error: implicit declaration of function 'enter_critical_section' [-Werror=implicit-function-declaration] error: implicit declaration of function 'leave_critical_section' [-Werror=implicit-function-declaration] Signed-off-by: v-tangmeng <v-tangmeng@xiaomi.com> | 2 个月前 | |
libc: add instrument api support Add registration function instrumentation API, which can achieve instrumentation of entering and exiting functions through the compiler's functionality. We can use CONFIG_ARCH_INSTRUMENT_ALL to add instrumentation for all source, or add '-finstrument-functions' to CFLAGS for Part of the source. Notice: 1. use CONFIG_ARCH_INSTRUMENT_ALL must mark _start or entry noinstrument_function, becuase bss not set. 2. Make sure your callbacks are not instrumented recursively. use instrument_register to register entry function and exit function. They will be called by the instrumented function Signed-off-by: anjiahao <anjiahao@xiaomi.com> | 2 个月前 | |
Merge remote-tracking branch 'mirtos/master' into dev-upmerge-nuttx-10.1-0507 Signed-off-by: liuhaitao <liuhaitao@xiaomi.com> | 2 个月前 | |
arch: Merge up_arch.h into up_internal.h neededby:partner_4262 Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 |