There is a non-removed UFS device on our customized carrier board. I added changes blow in devicetree to enable this device.
status = "okay";
After flashing the changed OS, I see messages below in dmesg.
pcp@pcp-desktop:/$ sudo dmesg | grep ufs
[ 2.782220] ufs_tegra 2450000.ufshci: Adding to iommu group 0
[ 2.788143] ufs_tegra 2450000.ufshci: freq-table-hz property not specified
[ 2.794004] ufs_tegra 2450000.ufshci: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[ 2.805045] ufs_tegra 2450000.ufshci: ufshcd_get_vreg: vcc get failed, err=-517
[ 7.858242] ufs_tegra 2450000.ufshci: freq-table-hz property not specified
[ 7.863465] ufs_tegra 2450000.ufshci: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[ 7.874013] ufs_tegra 2450000.ufshci: ufshcd_get_vreg: vcc get failed, err=-517
[ 9.428253] ufs_tegra 2450000.ufshci: freq-table-hz property not specified
[ 9.432650] ufs_tegra 2450000.ufshci: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[ 9.493552] scsi host0: ufshcd
[ 9.524105] ufs_tegra 2450000.ufshci: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
[ 9.524111] ufs_tegra 2450000.ufshci: dme-link-startup Successful
[ 9.541376] ufs_tegra 2450000.ufshci: default ref_clk_freq = 0
[ 9.561309] ufs_tegra 2450000.ufshci: HS Mode RX_Gear:gear_3 TX_Gear:gear_3 RATE_B series
[ 9.570483] ufs_tegra 2450000.ufshci: ufs scrambling feature enabled
[ 9.585677] ufs_tegra 2450000.ufshci: ufshcd_print_pwr_info:[RX, TX]: gear=[3, 3], lane[1, 1], pwr[FAST MODE, FAST MODE], rate = 2
There is no /dev/sd* in /dev and I cannot find any ufs device mounted in system. Did I miss any settings need to be changed to enable ufs device?
Is this based on rel-35 or rel-32? Could you also share full dmesg instead of partial logs?
It is based on rel-35.
dmesg.txt (82.2 KB)
Could you use rel-32 to validate the hardware first?
I tried r32.7.3 today and still can’t find any /dev/sd* in my system.
dmesg.txt (72.7 KB)
I only make changes below in r32.7.2,too.
status = "okay";
Anything also need to be changed to enable ufs !?
Could you share the boot up log from uart and dmesg too?
Here you are.
putty.log (119.5 KB)
Hi, what is your power supply design to UFS? Have you checked the power supply status to your UFS devices? For custom UFS design, you can find the related example in Design Guide. What you need to do is to make sure the power supply to UFS device is correct.
I have measured the VCC and VCCQ2. They are 3.3v and 1.8v repectively. I can find a directory “device_descriptor” created in /sys/devices/platform/2450000.ufshci. Does it mean that jetson AGX Xavier connect to ufs device properly but doesn’t create a device descriptor sd* in /dev !?
Could you share the schematic of your design in ufs part?
OK. But I would like to send it to you privately. Can I send it by e-Mail !?
I just notice you are using GPIO21_SD_POWER_SW_ON as EN pin for your load switch.
Where does this pin go to? Is it GPIO Q01?
It is GPIO21 (GPIO3_PA.00). I have set it as output pin with default high value in pinmux config. Please see the attachment.
pinmux.cfg (29.5 KB)
So did you see the VDD_3V3_UFS gets toggled to 3v3?
Yes, I measured the voltage of C59, C60 and C70. They are all 3.3V.
I am going to buy an UFS card for using on AGX Xavier Developer kit to compare with our customized carrier board. Do you have any recommended UFS card which is tested on AGX Xavier Developer kit!?
We’re using Samsung 256G UFS card for internal test, for you reference.
Also, hotpolug does not support.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.