• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 311 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.

AM3359: SPI0 CS0 is not getting asserted and SPI flash access is not happening

ti_user
Expert 1265 points
Part Number: AM3359

Hi,

I'm using a customer hardware designed with AM3359 processor running with Uboot, enabled with SPI0 CS0, CLK, D0, D1 in pin mux configuration.

While accessing using sf utils in Uboot it's observed that CS pin is not getting assert to low to select the SPI flash chip. The SPI flash micron macro is enabled in uboot along with the dts.

Please help is any more configurations to be added. Thanks

  • 0
    TI__Guru**** 168661 points

    Do you use the TI Processor SDK Linux release? Which version?

  • 0 in reply to Bin Liu
    Expert 1265 points

    Yes, TI SDK V6

  • 0 in reply to ti_user
    TI__Guru 68960 points

    Hi Mani,
    Are you working with the SDK v6 released in 2013?
    if yes, it is a bit challenging to support.

    Can we run simple test @u-boot prompt:
    1. SPI0 block access @u-boot to make sure SPI0 clock is enabled:
    => md 0x48030000 80
    2. SPI0 pinmux check-up:
    => md 0x44E10950 4
    For your reference, SPI0 pinmux is set-up as listed below for TI AM335x GP EVM and ICE board.

    \board\ti\am335x\mux.c
static struct module_pin_mux spi0_pin_mux[] = {
	{OFFSET(spi0_sclk), (MODE(0) | RXACTIVE | PULLUDEN)},	/* SPI0_SCLK */		
	{OFFSET(spi0_d0), (MODE(0) | RXACTIVE |										
			PULLUDEN | PULLUP_EN)},			/* SPI0_D0 */
	{OFFSET(spi0_d1), (MODE(0) | RXACTIVE | PULLUDEN)},	/* SPI0_D1 */			
	{OFFSET(spi0_cs0), (MODE(0) | RXACTIVE |									
			PULLUDEN | PULLUP_EN)},			/* SPI0_CS0 */
	{-1}, 
}

    Best,

    -Hong