About Brian Khuu

Brian Khuu · 2020-01-18

I am sure I'm overlooking something simple, but I'm trying to figure how to to send 256 bytes or more using the standard uart HAL functions.Source At This Current Point: https://github.com/mofosyne/stm32h7xx-uart/tree/41645cf33e00eb2de8438d5a04264d78...

Brian Khuu · 2019-10-20

Was able to program the board previously, but today after updating my STM32CubeIDE, it refused to run debug until I updated the stlink on my dev board.But upon doing so, it gave these error. Essentially meaning I cannot program my dev board.```STMicr...

Brian Khuu · 2019-09-22

While trying to convert your CubeMXH7 examples to cubemx for testing purpose. I came across some issues in terms of trying to synchronise the settings. I've written a comparison function to check how close I can get the cubemx generated code to the C...

Brian Khuu · 2019-07-09

I found others have similar issue, but they are trying to work around it instead of putting in a bug report: https://community.st.com/s/question/0D50X0000AAIEWbSQP/stm32cubemx-generated-sbrk-in-syscallsc-not-working-with-freertosI was trying to do a ...

Brian Khuu · 2019-07-08

I set TIM2 as the timebase and then enabled full hal assertion via STM32cube. It asserted in ../Drivers/STM32L1xx_HAL_Driver/Src/stm32l1xx_hal_cortex.c:197Stack trace:Thread #1 (Suspended : Signal : SIGINT:Interrupt) assert_failed() at main.c:455 0...

Brian Khuu · 2020-02-15

Problem fixed and traced to the stlink on the dev board. I found that the reason is because stlink-v3 version V3J2M1 has problem handling 256 bytes being sent out. This was fixed when updated to V3J6M2.All code used to prove uart is working is now in...

Brian Khuu · 2020-01-20

> How did you try to send more than 256 bytes? I didn't find a trace in the code. All I saw was 256 byte buffer and receiving "sizeof(buffer)".nBytes in the python script (~/git/stm32h7xx-uart/stm32_impulse_test.py) determine the size of the transmit...

Brian Khuu · 2020-01-19

Hmmm... I'm actually using the VCP of the onboard STLINK of NUCLEO-H743ZI2... is there a limitation to it?Though I'm pretty sure you should be able to load the stm32 via VCP serial. Haven't tested it yet.For context, was trying to use STM32 HAL uart ...

Brian Khuu · 2020-01-19

FYI the inline uart reg dump is done by. The current source at the this point doesn't place it anywhere. But for the description above, I placed it before `HAL_UART_Abort(ghwuart_ptr)` uart_debug_print(); uart_debug_error();Also I got these message...

Brian Khuu · 2019-12-03

Also take note that in Spaced Cowboy's thread, two individuals was able to switch their IDE to use OpenOCD, so you can use that option as well.> Hey, I had the same issue and resolved it by setting Debug Configurations -> Debugger -> Debug probe = ST...

User statistics

User Activity

Can't get HAL_UART_Receive_IT() to receive more than 256 bytes using standard stm32 hal functions.

STM32CubeIDE updated stlink on a stm32H743-EVALv2 board to V3J4M2, but then is unable to program the board.

STM32cubemx is possibly missing parameters and linkers for stm32h743i in FMC, USB and ethernet

CubeMX generated _sbrk() syscall does not work with freeRTOS enabled. Is there a recommended _sbrk that work well with freeRTOS? And if so, what is it and could you include it into CubeMX that is enabled only if freeRTOS is activated.

STMHAL STM32L152RETx - If you use TIM2 as the timebase source, it will assert in HAL_NVIC_SetPriority() due to uwTickPrio not being set in the TIM2 version of HAL_InitTick()

Re: Can't get HAL_UART_Receive_IT() to receive more than 256 bytes using standard stm32 hal functions.

Re: Can't get HAL_UART_Receive_IT() to receive more than 256 bytes using standard stm32 hal functions.

Re: Can't get HAL_UART_Receive_IT() to receive more than 256 bytes using standard stm32 hal functions.

Re: Can't get HAL_UART_Receive_IT() to receive more than 256 bytes using standard stm32 hal functions.

Re: STM32CubeIDE updated stlink on a stm32H743-EVALv2 board to V3J4M2, but then is unable to program the board.