HAL Diagnostic I/O

This first form is polled mode HAL diagnostic output, intended primarily for use during debug and development. Operations are usually performed with global interrupts disabled, and thus this mode is not usually suitable for deployed systems.

There are several configuration options usually found within a platform HAL which affect the use of this support in the BCM283X processor HAL. The CDL option CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL selects the serial port channel to use as the console at startup time. This will be the channel that receives output from, for example, diag_printf(). The CDL option CYGNUM_HAL_VIRTUAL_VECTOR_DEBUG_CHANNEL selects the serial port channel to use for GDB communication by default. Note that when using RedBoot, these options are usually inactive as it is RedBoot that decides which channels are used. Applications may override RedBoot's selections by enabling the CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS CDL option in the HAL. Baud rates for each channel are set with the CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL_BAUD and CYGNUM_HAL_VIRTUAL_VECTOR_DEBUG_CHANNEL_BAUD options.

Interrupt-driven Serial Driver

The second form of support is an interrupt-driven serial driver, which is integrated into the eCos standard serial I/O infrastructure (CYGPKG_IO_SERIAL).

Note that it is not recommended to share this driver when using the HAL diagnostic I/O on the same port. If the driver is shared with the GDB debugging port, it will prevent Ctrl-C operation when debugging.

The main part of this driver is contained in the generic CYGPKG_IO_SERIAL_GENERIC_16X5X package. The package CYGPKG_IO_SERIAL_ARM_BCM283X contains definitions that configure the generic driver for the BCM283X. That driver package should also be consulted for documentation and configuration options. The driver is not active until the CYGPKG_IO_SERIAL_DEVICES configuration option within the generic serial driver support package CYGPKG_IO_SERIAL is enabled in the configuration.

Support for hardware flow control is present in the driver, but should only be enabled if the RTS and CTS control signals are connected to accessible GPIO lines. The mini UART is also lacking some 16550 functionality, it is only capable of 7 or 8 bit characters, and only supports one stop bit and no parity; attempts to select other settings will be accepted, but will have no effect.