stm32f4 i2c problem

2019-04-03 Thread 787562067
HI, i have tried some days to know stm32 i2c, almost make it , but i still can not read the data correctly i think this is the right method, but dont know where i go wrong. please reply me //add i2c pin config in io.h #define STM32F4_PIN_I2C(port, idx, altfunc) \ { \ { \ .pin_fir

Re: RTEMS scheduler bug ?

2019-04-03 Thread groups
This sounds like a problem I had in 2015 on an STM32 that Sebastian helped me get around. At the end of the ordeal I wrote: "A bit of review to begin with; I am working with an STM32F4 ARM Cortex M4F processor’s ADC section. A feature of this ADC is the ability to have conversions triggered by

Re: cant break a stm32 exe

2019-04-03 Thread Gedare Bloom
On Wed, Apr 3, 2019 at 4:30 AM Ian Caddy wrote: > > Normally we would use 'c' instead of 'run'. > > If you have downloaded your code, just use the c for continue for embedded > processors. > You might also step through the boot and RTEMS initialization sequence. A lot happens before "Init" gets

Re: RTEMS scheduler bug ?

2019-04-03 Thread Sebastian Huber
On 03/04/2019 15:41, Catalin Demergian wrote: yes, I realized yesterday evening that gIntrErrs could be incremented in the second if. so I rewrote it like this int gIntrptErrs; int gInsertErrs; RTEMS_INLINE_ROUTINE void _Scheduler_priority_Ready_queue_enqueue(   Chain_Node                     

Re: RTEMS scheduler bug ?

2019-04-03 Thread Catalin Demergian
yes, I realized yesterday evening that gIntrErrs could be incremented in the second if. so I rewrote it like this int gIntrptErrs; int gInsertErrs; RTEMS_INLINE_ROUTINE void _Scheduler_priority_Ready_queue_enqueue( Chain_Node *node, Scheduler_priority_Ready_queue *ready_qu

stm32 i2c read/write

2019-04-03 Thread 787562067
HI, ALL i dont know what i have missed, but the code can not read the data extern stm32f4_i2c_bus_entry *const stm32f4_i2c1; rtems_task Init(rtems_task_argument argument) { puts( "\n\n*** i2c test begin ***\n"); uint8_t buf[20] = {0}; rtems_status_code sc = stm32f4_i2c_init(

Re: cant break a stm32 exe

2019-04-03 Thread Ian Caddy
Normally we would use 'c' instead of 'run'. If you have downloaded your code, just use the c for continue for embedded processors. regards, Ian Caddy On 3/04/2019 3:48 pm, 787562067 wrote: hi, guys, how to debug this case Loading section .init, size 0xc vma 0x125ec Loading section .fini,

cant break a stm32 exe

2019-04-03 Thread 787562067
hi, guys, how to debug this case Loading section .init, size 0xc vma 0x125ec Loading section .fini, size 0xc vma 0x125f8 Loading section .rodata, size 0x16b8 vma 0x12608 Loading section .ARM.exidx, size 0x8 vma 0x13cc0 Loading section .eh_frame, size 0x3c vma 0x13cc8 Loading section .init_arra