• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 193 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM3352: NOR flash issues in kernel

AM3352: NOR flash issues in kernel

Srinivasa Wunnimani1
Intellectual 600 points
Part Number: AM3352


Hi,

We had a parallel NOR flash discussion in the below link but the thread has been locked now:

http://e2e.ti.com/support/processors/f/791/t/834972#pi320966=7

Cotinuing the same discussion, I am opening a new thread with below question:

Hi Andreas,

Cypress team have tested S70GL02GS on Xilinx Zynq-7000 SoC, they are able to detect two chips (dies) and able to write more than two consecutive sectors.

Please refer to below link dated Mar 18, 2020 12:03 AM

https://community.cypress.com/thread/49446?start=15&tstart=0

With further discussion on this topic,

The flash node in my DTS is parsed in physmap-core.c, physmap_flash_probe() whereas TI's kernel tree will never execute physmap_flash_probe() in physmap-core.c.  Everything happens in “drivers/memory/omap-gpmc.c”.

This we have noticed and raised this question with TI in below link (Oct 4, 2019 9:46 AM)

 

http://e2e.ti.com/support/processors/f/791/t/834972#pi320966=2

From our debugging also, in old TI kernel (V3.2) we have noticed physmap_flash_probe() being used and it is working fine with S70GL02GS.

What is that gpmc driver is doing different than platfrom driver?

Regards

Srinivasa

  • 0
    TI__Guru 70192 points

    Hi Srinivasa,

    let me re-look into this specific aspect and see if anything spikes out and get back to you. It'll probably be later this week before I can get to it.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Guru 70192 points

    Hi Srinivasa,

    have you tried enabling...

    CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_OF=y

    ...in the Kernel?

    The example provided by Cypress has those enabled, and they also contain compatible = "cfi-flash"; in the DTS NOR node file which ties back to the MTD physmap driver. I know you had experimented with PHYSMAP before but if I remember correctly it was only in a MTD_PHYSMAP_COMPAT capacity, not OF (device tree) based. I would expect that driver to get probed under those conditions.

    Regards, Andreas