Re: Suggestion for change in Watchdog Timer Support Menu

2020-12-19 Thread Sara da Cunha Monteiro de Souza
Yes, I can.
=)

Em sáb., 19 de dez. de 2020 às 03:23, Xiang Xiao 
escreveu:

> The concern make sense, could you provide a patch?
>
> On Fri, Dec 18, 2020 at 11:55 AM Sara da Cunha Monteiro de Souza <
> saramonteirosouz...@gmail.com> wrote:
>
>> Hey friends,
>>
>> I have some suggestions for change for the Watchdog Timer Support Menu.
>>
>> 1. The first suggestion is to set the Keep alive interval to depend on
>> the Auto-Monitor choice. Because this interval is only really used by the
>> Timer Callback option or Worker callback option. So it may cause confusion
>> to NuttX users.
>> 2. Although the dev path is not within the Auto-monitor menu, It seems
>> that the Watchdog Device Path is going to determine which WDT will be fed
>> by the auto-monitor, which is not true. Because if the Auto-monitor is
>> enabled, it will feed all WDTs registered as character drivers.
>>
>> I am mainly reporting it because I actually had one customer who got
>> confused regarding this.
>>
>> Let me know your opinions!
>>
>> Regards,
>>
>> Sara
>>
>> [image: image.png]
>>
>>


STM32_SRAM3_BASE 0x3004c000

2020-12-19 Thread ElzPyiV
nuttx-10.0.0/arch/arm/src/stm32h7/hardware/stm32h7x3xx_memorymap.h


#define STM32_SRAM3_BASE

STM32_SRAM3_BASE 0x3004c000

2020-12-19 Thread ElzPyiV
Hello,


nuttx-10.0.1/arch/arm/src/stm32h7/hardware/stm32h7x3xx_memorymap.h


#define STM32_SRAM3_BASE0x3004c000/* 0x3004-0x30047fff: System 
SRAM3 */


Why "0x3004c000" ? Why not "0x3004"


Thanks.