Part Number: AM3352
In my custom board, on SPI_0_0, I have 16Mbytes flash, and SPI_1_1 – bus is available on one of the connector. We have small custom board, which has another 16Mbytes flash but this small custom board is like SD-Card and it is not necessary that when system boots, this card will be present.
SPI_0_0 = 16 MBytes flash on board, present all time.
SPI_1_1 = 16 Mbytes flash, most of the time not present on system when Linux is booted, later at some point - customer may plug daughter card which has 16MBytes flash.
As you can see from below log- on spi0.0 flash was found and MTD partition was created, but my external daughter card which has another SPI flash connected to SPI_1_1 was not connected, so it was giving error
m25p80 spi1.1: unrecognized JEDEC id bytes: 00, 00, 00.
I want to know once linux is completely booted, up and running and now user insert this external daughter card – in that case how create and mount partition from this external flash which is on SPI_1_1?
[ 1.549470] loop: module loaded
[ 1.555860] m25p80 spi0.0: found mx25l12805d, expected n25q128a11
[ 1.562007] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
[ 1.567323] 6 ofpart partitions found on MTD device spi0.0
[ 1.572861] Creating 6 MTD partitions on "spi0.0":
[ 1.577684] 0x000000000000-0x000000020000 : "u-boot-spl"
[ 1.584096] 0x000000020000-0x0000000a0000 : "u-boot"
[ 1.589906] 0x0000000a0000-0x0000000c0000 : "nvram0"
[ 1.595771] 0x0000000c0000-0x0000000e0000 : "nvram1"
[ 1.601569] 0x0000000e0000-0x0000000f0000 : "scratch_pad"
[ 1.607871] 0x000000100000-0x000001000000 : "linux"
[ 1.616116] m25p80 spi1.1: unrecognized JEDEC id bytes: 00, 00, 00
root@xyz:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00010000 "u-boot-spl"
mtd1: 00080000 00010000 "u-boot"
mtd2: 00020000 00010000 "nvram0"
mtd3: 00020000 00010000 "nvram1"
mtd4: 00010000 00010000 "scratch_pad"
mtd5: 00f00000 00010000 "linux"
How to create / make visible MTD info of SPI flash #2 which will be hot-plug on SPI_1_1 bus?
I am internally checking with our experts if "hot-plug" feature is supported by our driver and I will keep you posted on any updates. I am wondering if the device is detected if you connect to the SPI_1_1 bus.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Krunal Bhargav34:
if the device is plugged, before Linux boots, it works.
In reply to newuser:
Based on my internal discussion, SPI is not a hot pluggable bus and thus won't recognize hot plugs.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.