Visible to Intel only — GUID: iga1430780032997
Ixiasoft
1.1. Prerequisites for HAL Device Driver Development
1.2. Developing the HAL UART Device Driver
1.3. Debugging the bit_bang_uart Project
1.4. The BitBangUartTransmit() Function
1.5. The BitBangUartReceive() Function
1.6. Creating Device Hardware Access Macros
1.7. Staging the HAL Device Driver Development
1.8. Understanding the Hardware-Specific INSTANCE and INIT Macros
1.9. Integrating a New HAL Device Driver in the BSP
1.10. Understanding HAL Mutual Exclusion Resources
1.11. Overview of Debugging Tools for HAL Device Drivers
1.12. Debugging the HAL UART Device Driver
1.13. Conclusion
1.14. Document Revision History
Visible to Intel only — GUID: iga1430780032997
Ixiasoft
1.2.6. Preview: Customizing the Design
This section describes typical modifications you might make to the software or hardware after you have verified that it works with hard-coded addresses.
Before carrying out these modifications, work through the steps in Debugging the bit_bang_uart Project. Design modifications are described in detail starting in The BitBangUartTransmit() Function.
After you confirm successful communication from the software to the hardware, you can change the hard-coded address to a symbolic name found in system.h. Replacing the hard-coded register address with a symbolic definition enables the Nios II SBT to update the software if the peripheral's register base address changes in the future.
UART1_BASE is a definition provided by system.h. When defining macros in system.h, the Nios II SBT takes the peripheral name as defined in Qsys, and converts it to uppercase. The Nios II SBT creates the peripheral's base address by appending _BASE to the peripheral's name.