I have a custom board that is based on the Vybrid Tower. Running U-Boot 2013.07 I have two issues:
1) I need U-boot to shut up. How does one do this?
2) U-boot seems to be fiddling with a device when it's just sitting at the command prompt.
First issue: "1) I need U-boot to shut up. How does one do this?":::::
- Changing CONFIG_SYS_UART_PORT in include/configs/vf610.h from "(1)" to another port (e.g. "(2)" ). No joy, Output still goes to UART1. This #define has no effect.
- Doing the suggestions in README.silent. No joy.
- Changing the "stdout" env var in U-Boot to a random string. I get an error when I do this.
- Setting the "silent" env var. No joy.
I may also need to prevent U-Boot from initializing the UART. How does one do this? Is there a 'hidden' #define that I need to know about?
Second issue "2) U-boot seems to be fiddling with some devices when it's just sitting at the command prompt":::::
It looks like something is changing settings on the port PTA7 (on pin v15) after our MQX/M4 application has been launched and running. We have to set that port back to its correct value every once in a while.
I understand that U-boot does not use interrupts at all, is this true?
If U-boot does indeed have something that runs periodically via an IRQ), then that could be the culprit.