fix(PeriphDrivers): Fix UART Functional Regression for MAX32670, MAX32672, MAX32675, MAX32657

[Jake-Carter]

Description

Fixes functional regression caused by #1113

Calls to MXC_UART_RevB_SetFrequency weren't updated for these parts after changing the RevB API. As a result, MXC_UART_RevB_GetTXFIFOAvailable would eventually hang as the UART FIFO compeltely fills up and is never emptied due to misconfiguration.

Symptoms were that printfs would eventually infinitely hang. i.e. even Hello_World wouldn't work.

This PR should fix the regressions.

Also removed MXC_UART1 and MXC_UART3 definitions for ME16. These don't exist on the micro.

[Jake-Carter]

/clang-format-run

[sihyung-maxim]

Thanks for catching this - To be honest, I only looked at the SVD files to check what parts were using UART RevB. D:

[sihyung-maxim]

Completely missed this, but the UART RevB drivers are using chip-specific register definitions instead of the generic RevB ones:

msdk/Libraries/PeriphDrivers/Source/UART/uart_revb.c

Lines 286 to 317 in 6b6f2c3

	int MXC_UART_RevB_SetClockSource(mxc_uart_revb_regs_t *uart, uint8_t clock_option)
	{
	MXC_ASSERT(clock_option >= 0 && clock_option <= 3);
	if (g_is_clock_locked[MXC_UART_GET_IDX((mxc_uart_regs_t *)uart)]) {
	return E_NO_ERROR; // Return with no error so Init doesn't error out if clock config is locked
	}
	bool is_bclk_enabled = (uart->ctrl & MXC_F_UART_CTRL_BCLKEN) != 0;
	if (is_bclk_enabled) {
	// Shut down baud rate clock before changing clock source
	uart->ctrl &= ~MXC_F_UART_CTRL_BCLKEN;
	}
	MXC_SETFIELD(uart->ctrl, MXC_F_UART_CTRL_BCLKSRC, clock_option << MXC_F_UART_CTRL_BCLKSRC_POS);
	if (is_bclk_enabled) {
	// Turn the baud rate clock back on
	uart->ctrl |= MXC_F_UART_CTRL_BCLKEN;
	while (!(uart->ctrl & MXC_F_UART_CTRL_BCLKRDY)) {
	continue;
	}
	}
	return E_NO_ERROR;
	}
	unsigned int MXC_UART_RevB_GetClockSource(mxc_uart_revb_regs_t *uart)
	{
	return ((uart->ctrl & MXC_F_UART_CTRL_BCLKSRC) >> MXC_F_UART_CTRL_BCLKSRC_POS);
	}

ME16 builds are complaining due to this.