-
• #2
I answer my own issue... sometimes just writing it out leads me to the answer..
If I supply a usart=1 in the chip section, if compiles. Makes sense, but interesting you can't decline to have a usart.
-
• #3
it worked before, I definitely used it with Magic3, for now you can remove one line in NRF5X.make
diff --git a/make/common/NRF5X.make b/make/common/NRF5X.make index 57205a178..19b06343c 100644 --- a/make/common/NRF5X.make +++ b/make/common/NRF5X.make @@ -184,12 +184,13 @@ $(NRF5X_SDK_PATH)/modules/nrfx/drivers/src/nrfx_uarte.c \ $(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_ppi.c \ $(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_rng.c \ $(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_twi.c \ -$(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_uart.c \ $(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_spi.c \ $(NRF5X_SDK_PATH)/components/libraries/atomic/nrf_atomic.c \ $(NRF5X_SDK_PATH)/components/libraries/atomic_flags/nrf_atflags.c \
-
• #4
Yes, I had a 2v10 version that built fine, just wanted to update it. I'm OK with defining a usart for now, but thanks. You wouldn't even recognize my (first) QY03 now.. i removed the LCD and ran a breakout from the FPC, so it's running an EPD screen now.
-
• #5
Thanks! Interesting this fails now and now before, and it's in the HAL...
I guess somehow we need to disable NRF_UART completely if we're not asking for uart functionality?
-
• #6
I tried
'DEFINES += -DUART_ENABLED=0 -DUART0_ENABLED=0 -DNRFX_UART_ENABLED=0 -DNRFX_UARTE_ENABLED=0',
but it did not help, the $(NRF5X_SDK_PATH)/integration/nrfx/legacy/nrf_drv_uart.c and .h file have no checks in them and always evaluate something, I think typedefs in header file in the
#else
part is the issuetypedef nrf_uarte_baudrate_t nrf_uart_baudrate_t; typedef nrf_uarte_error_mask_t nrf_uart_error_mask_t; typedef nrf_uarte_hwfc_t nrf_uart_hwfc_t; typedef nrf_uarte_parity_t nrf_uart_parity_t; typedef nrf_uarte_task_t nrf_uart_task_t; typedef nrf_uarte_event_t nrf_uart_event_t;
-
• #7
So I guess this is specifically an SDK15 thing? I guess we could hack around it by adding
typedef bool nrf_uart_baudrate_t
/etc if there's no UART? -
• #8
I guess it was working before you added BANGLE2 and uart driver source into SDK15 makefiles (becasue of GPS)?
But OTOH SDK15 builds were there before BANGLE2 including serial - maybe the legacy driver was not there?
I'm getting these errors during my build:
Here is the relevant (Ihope) portion of my build file:
Not sure why it's happening here and not in other builds (like BANGLEJS2)...?
jv