MCF8315C: Application Note

Hi Michael,

Thanks for reaching out, our application note on I2C recommendations is going to be released within a couple of days. I will update you as soon as it is released.

Regards,

Sachin S

Sachin,

Thank you for the quick response. Do you have an estimated date for when this app note will be released? We are anxious to get started on integrating this device into one of our products, but need more detailed information on the I2C implementation in order to do so.

Thanks again,

Michael Poind

Sachin,

Thank you for the link to the App note. This clarifies a few things, but I still have some questions. Is it possible to get some sample code or functions for reading/writing to this device in C? I figured it would be worth asking if these are available and able to be shared before I spend time potentially reinventing the wheel on that front.

Thanks again,

Michael

Hi Michael,

You could refer to the firmware files which are used on the EVM which maybe of some help to you. This has the I2C code used in our EVM for TI's MSPx MCU.

However, we are also planning to release an example I2C code collateral, but that will take a couple of weeks from now to get published (we are targeting 28-Apr) for the release. Not sure if the timeline is suitable for you.

Regards,
Sachin S

Sachin,

Thank you for your response. I look forward to seeing the example I2C code. Is it still on track for the 28th?

I did have another question on setting the target ID on this device. I am looking at having 2 copies of this device on a single board. With both devices connected, how would one go about changing the target ID on one of them? Or is it a situation where it would be necessary to mount only one device, then change the target ID, then mount the 2nd device?

Regards,

Michael

Hi Michael,

Michael Pond said:

I look forward to seeing the example I2C code. Is it still on track for the 28th?

The appnote is being pushed out by a couple of weeks. Let me see if I can find any similar appnotes for you.

Michael Pond said:

I am looking at having 2 copies of this device on a single board. With both devices connected, how would one go about changing the target ID on one of them?

How do you plan on communicating to 2 devices at the same time? I2C bus allows only one address to be addressed at any given point.

Regards,
Sachin S

Sachin,

You are correct. Only one device can be addressed at any given point, but I would like to be able to drive 2 separate motors at the same time. The devices would be communicated with individually, which is why the target ID of the second device would need to be modified. However, I do not understand how this would be accomplished, since both devices would have the same address, and would be on the same bus initially. Would it be a situation where I would need to isolate the first device from the I2C bus in order to change the address on the second?

Thanks,

Michael

Hi Michael,

We are on holiday on Friday, response will be slow.

For your question, if you have multiple devices on the same bus may be Sleep request for one device and configure the other device before enabling.

Thanks and Best Regards

Venkatadri S

Sachin,

I just wanted to touch base to see if the I2C app note had been completed, or if there was a new estimate for when that would be released. Looking forward to starting development with this chip, but would love to have some example code to work off of.

Thanks,

Michael

Hi Michael,

I will be on business travel the second half of this month, so I unfortunately the appnote may get pushed to mid-June.

Regards,

Sachin S

Sachin,

Thank you for the update. Is there any way I could get some code snippets before then? Mid-June is starting to cut it a little close to our deadline, and I'd like to get started with code testing before then.

Thanks again,

Michael

Could you please drop me an e-mail at sachin-s@ti.com