2045419_en-US

Yes

k32l2b31 writing to LPUART1->STAT |= (1<<25) cause semihost_hardfault

i want to activate LIN Break detection on k32l2b31

bit LKDE must be set in status register

i try LPUART1->STAT |= (1<<25)

but it appear "semihost_hardfault" on debug

who knows why ?

best regards

Re: k32l2b31 writing to LPUART1->STAT |= (1<<25) cause semihost_hardfault

The "semihost_hardfault" when activating LIN break detection on the K32L2B31 most certainly suggests a problem that extends beyond simply setting the 'LKDE' bit. Possible causes include faulty LPUART clock configuration, accessing the peripheral before proper activation, memory access violations caused by an invalid base address, wrongly configured LIN break interrupts without a handler, or problems with the debugger/semihosting configuration. Before enabling LIN break detection, debug the initialization code, validate the base address, step through code with a debugger, check interrupts, simplify your code, and reference the datasheet to guarantee proper peripheral configuration. pa turnpike ez pass login

Re: k32l2b31 writing to LPUART1->STAT |= (1<<25) cause semihost_hardfault

The "semihost_hardfault" when enabling LIN break detection on the K32L2B31 likely indicates a problem beyond just setting the `LKDE` bit. Potential causes include incorrect LPUART clock configuration, accessing the peripheral before proper initialization, memory access violations due to a wrong base address, improperly configured LIN break interrupts without a handler, or issues with the debugger/semihosting setup. Debug by reviewing initialization code, verifying the base address, stepping through code with a debugger, checking interrupts, simplifying your code, and consulting the datasheet to ensure correct peripheral setup before enabling LIN break detection.