1978130_en-US

[#1]

How to use the USB port on MPC5748G?

Dear community members:

    I used ENET1 on MPC5748G, and used FreeRTOS, and called the socket API to send and receive data. At this time, I also wanted to use USB interface as another way of communication besides the network cable, but after I added the USB module, The Network Interfaces of the tcpip module used by ENET1 have changed from the original tcpip module to usb. Does this mean that the tcpip module of ENET1 cannot be used with the Host CDC (TCPIP) mode of USB? If not, please kindly give me a solution. How do you use USB Device CDC (UART) on MPC5748G if you really can't use both? This approach doesn't seem to see the sample program.

MPC5748G-GW-RDB 

Re: How to use the USB port on MPC5748G?Thanks for your kindly anwser!Re: How to use the USB port on MPC5748G?

If you will program the USB by yourself, there should be no problem with this.

Regards,

Lukas

Re: How to use the USB port on MPC5748G?Thank you very much for your answer. So now I will use pure USB protocol on the board of MPC5748G chip as a Device to communicate with the host, and at the same time use TCPIP ENET1 to communicate. Since the configurator is not suitable, I will not use the Configurator and write the initialization code by myself. Even if the board uses only one core, it's still feasible, right?Re: How to use the USB port on MPC5748G?

Hi @H-chips 

The stack supports this:

 And the configurator strongly requires fatfs or tcpip:

Regards,

Lukas

Re: How to use the USB port on MPC5748G?Hi Lukas

Thank you very much for your answer, but I still have a question. If I do not use tcpip or fatfs, can the chip use pure USB protocol to communicate with the Host as a Device? Is it possible to use USB and ENET at the same time?

Regards,

H-chipsRe: How to use the USB port on MPC5748G?

Hi @H-chips 

I can see that USB requires either fatfs or tcpip component to work. It correspond to this picture:

If tcpip with ENET is already used, it can't be obviously used for the USB at the same time (or vice versa, it doesn't matter). 

One solution I can see - use second core and second instance of SDK to have two independent tcpip components - one for USB, one for ENET.

Regards,

Lukas