Andrei Chichak commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/515#note_125480 I'm trying to get my head around the code in bsp_start_hook_0 where: ``` if ( stm32u5_init_octospi < stm32u5_memory_octospi_1_begin || stm32u5_init_octospi > stm32u5_memory_octospi_1_end ) { ``` First I wondered if I was being too sensitive with comparing the address of functions to linker section boundary addresses, then I wondered if there was a better way to figure out (??) if we're booting/running from octospi (??). You refer to octospi RAM, are you running from RAM? Perhaps some sort of compile time constant indicating that we intend to run from octospi RAM. Memory section addresses look okay. UART using new style data registers (not like stm32f4 bsp) okay. Not sure what is happening with the null section at 0x0, but I can imagine it has something to do with zero pointer dereferencing. Latest version of the HAL seems to be 1.6.1 or 1.7, I'm not sure that it is worth updating as the u5 is a reasonably new processor and the updates to the HAL are happening quite often currently. Perhaps look at the HAL release notes to see if there is anything important. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/515#note_125480 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
