BP-CC3301: Integrating the module with a custom Linux host

Sharadanand Karanjkar

Part Number: BP-CC3301
Other Parts Discussed in Thread: CC3301

Hello,

We are trying to integrate the BP-CC3301with a custom Linux host, We are getting following error when we connect SDIO interface.

[  203.938400] mmci-pl18x 58005000.mmc: card claims to support voltages below 
defined range
[  203.964374] mmc0: error -84 whilst initialising SDIO card
[  203.969746] mmci-pl18x 58005000.mmc: card claims to support voltages below 
defined range
[  204.031577] mmc0: error -84 whilst initialising MMC card


Do someone have any idea about this?

Warm regards,
Sharadanand Karanjkar

over 2 years ago

0 Corinne Meyers over 2 years ago

TI__Intellectual 2825 points

Hi Sharadanand,

Thank you for reaching out. I am looking into this and will get back to you with before EOD 11/8.

Best,
Corinne

0 Corinne Meyers over 2 years ago

TI__Intellectual 2825 points

Hi Sharadanand,

Could you please clarify which Linux kernel you are using? Additionally, can you reply with your modified DTS and the full log when you try to boot up? Lastly, can you please attach the hardware schematic of the connections between the custom Linux host and the CC3301?

Thank you,
Corinne

0 Sharadanand Karanjkar over 2 years ago

Prodigy 100 points

Hi Corinne,

Link kernel version is the Linux 6.1.28 and board is "STM32mp157f-ev1", I have not modified the device tree.

But as per my understanding the card should be at-least detected by the board, right?

Regards,

Sharadanand

0 Corinne Meyers over 2 years ago in reply to Sharadanand Karanjkar

TI__Intellectual 2825 points

Hi Sharadanand,

I am looking into that for you, but a follow-up question on the Linux kernel. Are you applying the patches from the device SDK to bring up the CC3301? Additionally could you please provide the full log that is shown when you try to boot up?

Best,
Corinne

0 Sharadanand Karanjkar over 2 years ago in reply to Corinne Meyers

Prodigy 100 points

Hi Corinne,

Yes, I have ported the patches from the TI SDK to the STM32 Yocto project.

I am connecting the CC3301 via SD card interface and getting the above log, apart from that I am not getting any other special logs.

Regards,

Sharadanand

0 Corinne Meyers over 1 year ago in reply to Sharadanand Karanjkar

TI__Intellectual 2825 points

Hi Sharadanand,

I tried to replicate your error using a device tree that wasn't modified for the CC33xx and while I didn't receive the same error it did cause numerous errors and I was unable to bring up the device. Please try modifying your device tree and see if that fixes your problem. Let me know if you need me to review it and if this resolves your problem.

Best,
Corinne

0 Sharadanand Karanjkar over 1 year ago in reply to Corinne Meyers

Prodigy 100 points

Hi Corinne,

I am using a non TI based host platform, are there any special things we need to take care for this?

Warm regards,

Sharadanand

0 Corinne Meyers over 1 year ago in reply to Sharadanand Karanjkar

TI__Intellectual 2825 points

Hi Sharadanand,

Can you clarify your question? Special things you need to account for when modifying the device tree? If that is what you were referring to then the answer is no, the device tree reflects the harware configuration and needs to be adusted for that no matter what type of hardware.

Best,
Corinne

0 Sharadanand Karanjkar over 1 year ago in reply to Corinne Meyers

Prodigy 100 points

My doubt is what are the general guidelines when we integrate CC33xx to a non-TI host, Are there any hardware limitations? or busy specific restrictions?

0 Corinne Meyers over 1 year ago in reply to Sharadanand Karanjkar

TI__Intellectual 2825 points

We will release specific considerations closer to the releease data of the device. In the meantime we are available to help with specific questions and/or errors you run into.

Best,
Corinne

0 Sabeeh Khan1 over 1 year ago in reply to Sharadanand Karanjkar

TI__Mastermind 32510 points

Hi Sharadanand,

No, there are no specific hardware limitations for a non-TI host. The CC33xx follows SDIO standard, so there is nothing specific about busy restrictions either. We have a migration guide that you can refer to help you port the driver over. In this case, the mmc driver is not detecting the SDIO device.

Could you please share your current DTS, even if it's unmodified?

However, the limitation I see is that you are using kernel 6.1. Our current CC33x package supports 5.10. Regardless, we can help you port the driver over to k6.1. Sounds like you have already done this, correct?

+1 Sharadanand Karanjkar over 1 year ago

Prodigy 100 points

The problem was that the nRESET pin was left not connected, after pulling up that pin as well as SDIO_D0 to SDIO_D1 pins needed to be pulled up.

Wi-Fi

Wi-Fi forum

BP-CC3301: Integrating the module with a custom Linux host