Part Number: AM13E23019
Other Parts Discussed in Thread: DRV7167, UNIFLASH,
Hello,
Any advice on the following isssue?
We are in the middle of firmware bring-up on our in-house traction motor board using the AM13E230, and two tooling gaps are starting to affect our schedule. We would appreciate your help and insight on both.
1. BSL host tool with MCAN support
Per the AM13E230x Bootloader guide (SLUUDI8), the BSL supports UART, I2C, and CAN-FD, and we can see the configurable pin defaults (CAN Tx PA12, CAN Rx PA11, BSL Invoke PA6). However, we don't see a host-side BSL tool or script from TI that actually drives the MCAN interface.
CAN is our production programming path — our motor drives sit on a CAN bus inside the robot with no practical JTAG access once assembled, so a working CAN BSL flow is a requirement for us, not a convenience. Specifically:
- Does TI have a BSL host tool or reference script that supports the MCAN interface today? If so, how do we get access to it?
- If it does not exist yet, is this something TI would be willing to build or provide in the near future? We would be glad to be a design partner and test it against our hardware.
- Is there any updated support package, sample application, or NDA-gated release for the BSL protocol that we could get access to in the meantime?
If we need to write our own host implementation against the BSL protocol in SLUUDI8, I'm sure we can do that, but we would rather not duplicate work if TI already has something in the works.
2. J-Link is not a workable fallback. We tried a Segger J-Link and saw instability— suspecting this instability may relate to the pre-production nature of the AM13E230. Is this something the AM13E230 team has studied in detail?
To us, the ability to do bootloader over CAN is high on our priority list since there seem to be power/signal stability issues related to the XDS110 debug line (potentially caused by the DRV7167?)
