Hi there,
there is quite some literature regarding the resident bootloader, device-specific activation, BSL-scripter, etc. I got the bootloader working through software activation (jump to 0x202000) and communicating through JTAG pins P1.2 & P1.3 with BSL-scripter running on a PC at 115200 Bd. So far, so good.
However, I'd like to use a different UART than eUSCI_A0. The standard software invocation causes the UART port to be derived from protected TLV information and does allow no change. Is there a way to utilize the boot mailbox with software invocation? What about non-standard pins, such as diverting I/O of the chosen eUSCI to GPIO port 3? If these pins are not eUSCI_Ai's default configuration, will port mapping be applied? And what about faster baudrates? At least 1 Mbps would be nice to have (yes, the PC does not willingly support this baudrate, but native drivers - e.g. FTDI - will do). I do understand that I could write my own bootloader or tweak the existing code - but with the boot override mailbox a mechanism is already in place which I would like to take advantage of.
Suggestions welcome.
Chris
