Hi Simon, I enabled the next four variables CONFIG_NVME_PCI=y CONFIG_NVME=y CONFIG_CMD_NVME=y CONFIG_PCI=y
how different is CONFIG_NVME_PCI from NVME_PCI, I took the latter value from several configs files in u-boot repo and from [1] [1] https://github.com/u-boot/u-boot/blob/ef8336e2705fce2502383f25d68188c6b1f94dd0/doc/develop/driver-model/nvme.rst#L44 El mar, 8 ago 2023 a las 22:05, Simon Glass (<s...@google.com>) escribió: > Hi Luis, > > On Tue, 8 Aug 2023 at 17:09, Luis Alfredo da Silva > <luis.adasil...@gmail.com> wrote: > > > > I compiled u-boot version 2023-07 and boot it on a RPi CM4 using a PCIe > M.2 > > NVMe drive, but it doesn't appear to be working. > > > > Once u-boot has started and boot successfully it recognizes the PCIe > device > > giving me the next output > > > > U-Boot> pci > > BusDevFun VendorId DeviceId Device Class Sub-Class > > _____________________________________________________________ > > 00.00.00 0x14e4 0x2711 Bridge device 0x04 > > 01.00.00 0x1c5c 0x174a Mass storage controller 0x08 > > > > but when trying to use the nvme scan and nvme info there is not output. > > > > NVMe drive has two partitions 1st is a FAT partition, and 2nd is a EXT4 > > partition, the RPi firmware recognizes the FAT partition and u-boot boot > > correctly. > > > > I don't know if this worked before, but I saw in the mailing list that > > there could be already support for other ARM64 boards. > > Is NVME_PCI enabled? > > Regards, > SImon >
