AWRL6432: MCAN transmit failed.

Hi,

What do you mean by "configuration is adopted from SDK and example demo?"

Also, there is no difference in each of the tests you've mentioned besides the specific cable being used? As in software and all other hardware is the same?

Best Regards,

Kevin

Hi,

What do you mean by "configuration is adopted from SDK and example demo?"

Also, there is no difference in each of the tests you've mentioned besides the specific cable being used? As in software and all other hardware is the same?

Best Regards,

Kevin

Dear Kevin Ortiz

sorry for my English being poor.

"configuration is adopted from SDK and example demo" means as follow.

MCAN driver which is in "ti\MMWAVE_L_SDK_05_01_00_04\source\drivers\mcan" is used.

Do I make myself clear?

Best regards

Choi

Hi Choi,

No worries at all! I just want to make sure I properly understand. Thank you for the clarification.

To confirm, when using AWRL6432, the only difference between passing case and failing case is the cable itself? The software is the exact same?

Best Regards,
Kevin

Dear Kevin Ortz

You asked "EXACT SAME", answer is slightly different.

I 'v changed Bit Rate only chage is as below.

 Bit rate configuration function (e.g. MCAN_initSetBitTimeParams() ) is re-defined. please refer below source code

TI original source code.

Modified and Tested code

Test results are same to my previous mention.

with short length cable, it works fine.

with long length cable, it does not work properly.

Check this please

Best regards

Choi

Hi Choi,

Quick 2 follow up questions,

1) What bit-rate are you attempting to send messages at? 

2) What kind of cables are you using? 

Best Regards,

Kevin

Dear Kevin Ortiz

1. Bit rate depens on OEM and vehicle, bit rate from 1M/500k to 5M/1M should be ready. 

2. unshielded 120ohm cable is used, According to TI's guide which is linked below, Belden cable 3105A will be test.

For your previous mention "when using AWRL6432, the only difference between passing case and failing case is the cable itself?"

MY answer is that difference between passing case and failing case is EVM, not cable.

Please review my mention carefully,

My Question is "With AWR6843AOP EVM, there is no MCAN issue, but WHY there is ISSUE with AWRL6432 EVM"

Best regards

Choi

link is 

Controller Area Network Physical Layer Requirements (ti.com)

Hi Choi,

We are looking into these details internally. Will update shortly, feel free to ping thread if no response is given by early next week.

Best Regards,

Kevin

Dear Kevin Ortiz

Thanks for reply, and please check this issue seriously.

Best regards

Choi

Hi Choi,

Of course! We are looking to see if there is hardware limitations in CAN device on board. Quick question, have you verified 1Mbps bitrate works with the 5m cable?

Best Regards,

Kevin

Dear Kevin Ortiz

I attached screen capture which was test already 13days ago

I tested 500k/1M configure 1m cable and 5m cable.

As described with 1m cable, it worked properly but with 5m calbe it did not.

Best regards

Choi