TDA4VM USB boot using DFU

Hi Yutai,

Yes, USB ID pin is required for the OTG mode and to switch between the host and the device mode of operation based on the type of cable connected to the the USB port. But this mostly used by the Linux kernel driver and not supported at the boot level.

Is this a custom board design? Can you detail further on where you added the 10K PD for USB0_ID?  Can you share the schematic showing the change? This info will help us understand your issue and answer your queries.

For USB DFU boot, the USB_ID pin does not play any role. We just need to make sure that the SYSBOOT is correctly set for USB DFU boot.

regards,

Praveen

Hi Praveen

Thanks for your comments. Yes, it is custom board design not TI EVM.

Does DFU boot don't need TDA4VM in USB device mode ? as my design I directly add 10K PD on TDA4VM Pin AC6 (USB0_ID).

From datasheet: 

USB0_ID: L => HOST mode

USB0_ID: Open => Device mode

So my quesiton is that if  I config TDA4VM to USB host mode, does it can also use from USB DFU to booting as you mention USB_ID pin dont play any role for DFU.

Really ?

Thanks

Yutai

Hi Yutai,

Yes, for the the DFU boot, it is required for TDA4VM to be in USB device mode.

But for the TDA4VM USB controller to operate in the host or device mode, USB0_ID pin does not play any role. Instead it is the USB0_VBUS pin  is of importance. For the the device mode, it is expected that the external supplied 5V on the VBUS line of USB port. Similarly for HOST mode, the the VBUS pin on the USB port is expected to have the 5V.

ID pin is used for OTG/DRD support only.

Hope this clarifies your query. Suggest to read up more on the ID and VBUS pin role for better understanding.

regards,

Praveen

Hi Praveen

When we use DFU boot it need TDA4VM is device/slave mode. 

=> That means the USB_ID pin need open from HW side; the TDA4VM is USB device/slave mode to run ROM code for DFU boot.

=> That means if the USB_ID is pull down from or low from HW side; theTDA4VM is HOST mode, in this case we can't use DFU boot. 

Correct?

Thanks

Yutai

Hi Yutai,

I am not sure if I understand your context of asking this query.

As mentioned, for TDA4VM  to do the DFU boot, the requirement is to have the the remove device (ex: HOST PC) connect to it TDA4VM 's USB port via a cable to provide the 5V on the VBUS line.  ID pin is don't-care.

Can you share you schematics?

regards,

Praveen

Hi  Stan

Thanks for your comments. As I mention before my design USB connector don't have ID pin but we also want to use DFU boot feature. 

From your comments :

1. " Because the USB DFU (Device firmware upgrade) requires TDA4 to be in USB Device mode, ROM will configure the controller in always-Device mode          unconditionally (only 5-V is required on VBUS). ROM expects this USB port to be either Device, or OTG on the PCB (B-connector or OTG connector)."

Yutai: As you mention we use DFU to boot TDA4VM, the TDA4VM ROM code will configure USB controller in always-Device mode unconditionally (only                   5-V is required on VBUS).  Do you mean ROM code can configure USB controller to device mode  and don't care the USB ID status is low or high?

         As datasheet mention the TDA4VM DFU USB in device mode. So I dont know the device mode is configure from ROM code or from USB ID pin.

        Can you please give your comments. 

Thanks 

Yutai