[Sktz]

Thanks for the quick response Neeraj.
We did program the RED board ID.
=> i2c md 0x50 0x00.2 20
0000: aa 55 33 ee 41 33 33 35 42 4e 4c 54 4f 53 30 30 .U3.A335BNLTOS00
0010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …………….
=>

The issue I have with using the same Linux image on both boards is, the hardware is not the same.
Our custom image is based on the RED, with device tree modifications.
We do not use USB0, the pins are NCs.
The image is still looking for USB0.

I would like to clarify something you said, our image does not boot on the RED board.
It partially boots, then hangs.
If we u-boot, we can see the USB PHY.

I will contact Martin.
Thanks.
Steve

• This reply was modified 4 years, 7 months ago by Sktz.

[Sktz]

Hi Neeraj,

I know support will take additional time during our current situation.
I am hoping you’ll have some feedback on this issue.

USB1 is still not working for us and I believe there is info in this log that can help.
We thought we had disabled USB0 since we are not using it but you can see the code looking for USB0.
Trying to figure out on our end too.

Regards,
Steve

[Sktz]

Additional info, when trying our image on Octavo RED vs custom board:
– Octavo RED has internal MMC programmed and we boot from SD card.
– Custom board has unprogrammed internal MMC and we boot from SD card.

See differences in boot log at about 2.96:
Comparing the boot logs I see the RED doing this:
[ 2.849539] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[ 2.859348] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 2.868004] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.875366] usb usb1: Product: MUSB HDRC host driver
[ 2.880454] usb usb1: Manufacturer: Linux 4.19.79 musb-hcd
[ 2.885977] usb usb1: SerialNumber: musb-hdrc.1
[ 2.894349] hub 1-0:1.0: USB hub found
[ 2.898843] hub 1-0:1.0: 1 port detected
[ 2.909327] cpu cpu0: Linked as a consumer to regulator.3
[ 2.915729] cpu cpu0: Dropping the link to regulator.3
[ 2.924043] cpu cpu0: Linked as a consumer to regulator.3
[ 2.934383] PM: Cannot get wkup_m3_ipc handle
[ 2.940497] PM: Cannot get wkup_m3_ipc handle
[ 2.946984] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
[ 2.955828] sr_init: No PMIC hook to init smartreflex
[ 2.966704] Waiting for root device /dev/mmcblk0p2…
[ 3.360223] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[ 3.542744] usb 1-1: New USB device found, idVendor=0424, idProduct=2534, bcdDevice= 1.82
[ 3.551812] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.566591] hub 1-1:1.0: USB hub found
[ 3.571643] hub 1-1:1.0: 4 ports detected
[ 3.597075] PM: Cannot get wkup_m3_ipc handle
[ 3.920430] usb 1-1.4: new high-speed USB device number 3 using musb-hdrc
[ 4.052123] usb 1-1.4: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.00
[ 4.060700] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4.068075] usb 1-1.4: Product: Cruzer Glide
[ 4.072527] usb 1-1.4: Manufacturer: SanDisk
[ 4.076846] usb 1-1.4: SerialNumber: 200548573007B8119C2E
[ 4.085972] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 4.103917] scsi host0: usb-storage 1-1.4:1.0
[ 4.113415] PM: Cannot get wkup_m3_ipc handle
[ 5.128388] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 1.00 PQ: 0 ANSI: 6
[ 5.151464] sd 0:0:0:0: [sda] 30605312 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 5.164600] sd 0:0:0:0: [sda] Write Protect is off
[ 5.174496] PM: Cannot get wkup_m3_ipc handle
[ 5.180874] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 5.213374] sda: sda1
[ 5.225095] sd 0:0:0:0: [sda] Attached SCSI removable disk

While the Nemo2 is doing this:
[ 2.853745] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[ 2.863691] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 2.872356] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.879629] usb usb1: Product: MUSB HDRC host driver
[ 2.884720] usb usb1: Manufacturer: Linux 4.19.79 musb-hcd
[ 2.890243] usb usb1: SerialNumber: musb-hdrc.1
[ 2.898529] hub 1-0:1.0: USB hub found
[ 2.903321] hub 1-0:1.0: 1 port detected
[ 2.913812] cpu cpu0: Linked as a consumer to regulator.3
[ 2.919827] cpu cpu0: Dropping the link to regulator.3
[ 2.928152] cpu cpu0: Linked as a consumer to regulator.3
[ 2.938558] PM: Cannot get wkup_m3_ipc handle
[ 2.944577] PM: Cannot get wkup_m3_ipc handle
[ 2.951349] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
[ 2.960038] sr_init: No PMIC hook to init smartreflex
[ 4.337335] EXT4-fs (mmcblk0p2): recovery complete
[ 4.349194] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.357714] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 4.367506] devtmpfs: mounted
[ 4.372880] Freeing unused kernel memory: 1024K
[ 4.378451] Run /sbin/init as init process
[ 4.532319] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 5.240277] net eth0: initializing cpsw version 1.12 (0)
[ 5.255875] TI DP83822 4a101000.mdio:01: attached PHY driver [TI DP83822] (mii_bus:phy_addr=4a101000.mdio:01, irq=POLL)
[ 5.277573] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.403197] cpsw 4a100000.ethernet eth0: Link is Up – 100Mbps/Full – flow control rx/tx
[ 8.415389] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
#

• This reply was modified 4 years, 7 months ago by Sktz.

[Sktz]

One more piece of info:
If I stop the boot process and use u-boot:
=> usb start
starting USB…
Bus usb@47401800: Port not available.

AND:
No +5V at USB port so u-boot is not enabling USB1_DRVBUS.
Doesn’t look like u-boot is able to configure USB port.

VERIFIED:
U-boot does not configure the USB1 port, does not drive USB1_DRVBUS, does not drive data lines.

Linux does appear to configure the USB1 port, drives USB1_DRVBUS, data lines appear active.
Still does not see flash drive.

• This reply was modified 4 years, 7 months ago by Sktz.
• This reply was modified 4 years, 7 months ago by Sktz.

[Sktz]

Neeraj,

Boot log and dmesg output with USB flash drive inserted attached.
There are several messages about USB and not finding info.
Your review is greatly appreciated.

Regarding other images, I think the software team tried this.
Waiting on more info and will post when I have it.

Regards,
Steve

• This reply was modified 4 years, 7 months ago by Sktz.

Attachments:

1. Board4_Boot_Log_dmesg_USB_Flash_Drive.txt

[Sktz]

Thanks Neeraj.
Additional info:
1. Voltages are good.
The only device we have plugged into the USB1 host port to date is a FLASH drive with minimal current reqs.

2. Given the above and the use of a FLASH drive, what would the appropriate driver be?

And to add: There was no device plugged into USB1 conn during that boot log. Would it be reporting the internal AM3358 USB controller/PHY?

Data integrity is not an issue, controlled dielectric/impedance in place with correct trace W/S geometry.

Just to be sure, VIN_USB connected to GND will not interfere with USB operation?

Regards,
Steve

• This reply was modified 4 years, 7 months ago by Sktz.
• This reply was modified 4 years, 7 months ago by Sktz.

[Sktz]

Thanks Neeraj.
I would like to understand the issue with the MII interface and the PHY reset but it is not a pressing issue at this time.

Thanks for reviewing the log file.

Steve

[Sktz]

While this Ethernet/MII/PHY reset issue is not a priority at the moment and we have a fix, I would like to understand what the poblem is.
The USB port not working is a higher priority and I will create a dedicated post.
Steve

[Sktz]

Neeraj,
Thanks for the response.
I had done all you suggested before posting.
Design and config are correct.

Since posting I have discovered that it is a power-on reset problem between the OSD3358 C-SIP and the TI DP83822 PHY.
It is the same situation as mentioned in this forum poast:

Ethernet does not work without active UART session

See Reply #9276.
For now I have a jumper and will hold the PHY in reset longer and add a GPIO for reset control.
I would like to understand this issue better though and will continue to investigate.

At the moment we are now debugging the USB interface, which also seems to be a config/driver issue.
I have attached the boot log after a successful DHCP session using the PHY reset jumper coming out of power-up.
Can you review to see if there are issues we are missing?

Thanks again.
Steve

• This reply was modified 4 years, 7 months ago by Sktz.

Attachments:

1. Boot_Log_Board4_DHCP_Good_with_Jumper_on_PHYreset.txt

[Sktz]

Thanks for pointing that out. I looked right past that.

[Author]

Posts