Re: stm32 external SRAM

2019-06-24 Thread Jython
> > printf("data test return %04x\n", memTestDataBus(0x6802)); > > > printf("addr bus test return %04x\n", memTestAddressBus(0x6800, > 1024*1024)); memtest all passed at application mode, when SRAM init function moves to bsp_start_hook_1 then not work Can i do init_main_osc in bsp_s

Re: stm32f4 __wfi

2019-06-24 Thread Jython
this is the configure: #define CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER #define CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER #define CONFIGURE_APPLICATION_NEEDS_RTC_DRIVER #define CONFIGURE_MAXIMUM_TASKS 5 #define CONFIGURE_MAXIMUM_TIMERS3 #define CONFIGURE_RTEMS_INIT_TASKS_TABLE #

Re: RTEMS 5 Release

2019-06-24 Thread Chris Johns
On 24/6/19 8:23 pm, Heinz Junkes wrote: > Is it foreseeable when RTEMS5 will get a release? I have made some progress however I need to fix the RSB. I completed the change to get all the source tarballs for all host architectures however we have some packages that are git repos I was not aware of

Re: stm32f4 __wfi

2019-06-24 Thread Christian Mauderer
On 24/06/2019 11:36, Jython wrote: > now i have changed to RTC wakeup, my key press can wake up the board, > > //rtems_stack_checker_report_usage(); >         >         PWR_EnterSTOPMode(1, 1); >         >         init_main_osc(); >         usleep(10); >         pri

RTEMS 5 Release

2019-06-24 Thread Heinz Junkes
Is it foreseeable when RTEMS5 will get a release? Danke, Heinz smime.p7s Description: S/MIME cryptographic signature ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users

Re: stm32f4 __wfi

2019-06-24 Thread Jython
now i have changed to RTC wakeup, my key press can wake up the board, //rtems_stack_checker_report_usage(); > > PWR_EnterSTOPMode(1, 1); > > init_main_osc(); > usleep(10); > printf("RCC_CFGR %02x\n", RCC_CFGR & 0xff); > so i think sleep function can't be wake u

Re: stm32f4 __wfi

2019-06-24 Thread Christian Mauderer
On 24/06/2019 02:47, Jython wrote: > that's to say EXTI wakes up from sleep function because interrupt > handler log out > but _CPU_Thread_Idle_body does not exit ?  want to know what is the > sleep/idle exit condition? The idle task is the task with the lowest priority. So it runs if no other hig