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.

SPI boot mode - C6670 - Chip Select 1

Dear TI,

We seem to observe a strange HW issue and I was wondering if someone could confirm.

When setting the bootstrap for the SPI, 2 bits are allocated to the chip select.

Here is what our HW engineer (using a scope to probe the pins straight from DSP)  is reporting to me about this settings:

00=> CS0 active

01=> No CS active

10=> CS0 active

11 => No CS active

We have been trying to boot from SPI on CS1with no success. Can someone let us know if there is a problem in the RBL?

By the way, this test needs to be done without the IBL/FPGA of the EVM since the FPGA of the EVM samples the bootstrap, force a boot from I2C and then reconfigure the SPI module. The devstat informs that after this has occur, the values were 00.

I would be grateful for an answer.

  • Aymeric,

    I think this is in your custom board. We haven't tried anything but CS0. But it should work for all the Chip Select. I am not sure I understand the probe result. What you mean by CS) active. The boot strap is used to select the chip select that is connected to your flash. In the EVM we have the CS0 connected to the flash and CS1 connected to FPGA. In your setup does CS1 is connected to the flash?

    Thanks,

    Arun.

  • Arun

    You have understood correctly. There are 2 chips select, one is connected to a NOR Flash and another is connected to another device.

    When we use CCS, initialize the board using a gel file and access the flash device using our drivers (platform lib with adaptation), we use CS1. We can Read Write and do all we need.

    Our problem is that on boot, using the settings described above, CS1 is never getting active (low), therefore the C6670 does not read the flash device.

    Aymeric

  • Aymeric,

    What is the pin mode you are selecting? you need to select 4 pin mode.

    Thanks,

    Arun.

  • hello,ArunMani

    I have two questions about BCP .

    firstly , I don't know how to understand the Output Data of RM module in BCP? why it is not match the format of 36.212 in 3GPP?

    Secondly ,I want check the SSL module with the Output data of MOD,Whether it is feasible?

    Thank you

  • Arun,

    Sorry that I have 2 posts in parallel but I see them as 2 different issues. The first one is creating the boot table inside the SPI and the second (this one) is what the HW engineer believes to be a problem in the RBL.Our board uses the same NOR flash as the EVM, it is on CS1 rather than 0 but that is about where the differences stop.

    To answer your question, our bootstrap set up is as follow:

    My devstat = 0x3150D. (we tried also 3140D,3160D and 3170D which are all the combination for CS)

    And here is the description according to section 2.4.2.6 of the data manual SPRS689D p34

    Little endian, SPI parameter table index 0, chip select (0b00 - 0b01 - 0b10 - 0b11) (we need CS1 but the manual is confusing), 24 bit address, 4 pins (0 for bit 10 which according to manual is 4 pin mode used - there is no 5 pin mode with SPI), mode1for the CLK pol/phase.

    Using this setting (whatever CS bits are), CS1 is never active and we do not see any activity on the CLK signal or SPII or SPIO)

    Our HW engineer found the following post:

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/165943/773551.aspx#773551

    I will get back to you after investigating a bit more this new information

    Aymeric

  • Arun,

    I completed the investigation with my colleague and here is what we see:

    On boot (with devstat - 0x3150d where CS=0b01), we can see that the DSP tries to access a device. There is activity on the clock signal and on the data, however we never see the CS being latch.

    We compares the SPI registers from boot (RBL configuration) to what they are when we can read and write the NOR flash. We think the RBL is not configuring the SPI pin control register properly. At boot, we see 0x01010E01 when it should be 0x01010E03 or 02.

    Then SPI default chip select register settings is used to control the CS. This register is configured correctly in the RBL.

    Aymeric

  • Aymeric,

    Can you try 5 pin mode. The devstat should be 0x31D0D.

    Thanks,

    Arun.

  • Aymeric,

    The reason we have 4 pin and 5pin setting as opposed to 3 pin and 4 pin mode, is that we also add the clock as one of the pin. So please try the 5 pin mode and let me know if that works.

    Thanks,

    Arun.

  • Aymeric,

    Any update on this issue?

    Thanks,

    Arun.

  • Arun,

    Sorry for the delay in getting back to you. We are still working on our PCIe issues (if you talked to Jason).

    This specific query is resolved. From the point of view of hardware, changing the spi operation mode configuration to 5 pin mode is behaving as we expected it to.

    I will close this query (validate verify) and keep working on the first post because the boot still does not work (we are debugging using the scope)

    on power on: the dsp enable CS1 (active low) and data are being pulled from Flash to DSP.

    According to what we can see, there is a read operation of 4 bytes from flash address 0, then ~80 bytes from flash address 1.

    After this first read, there is a bit of delay (~10ms) and after this delay, we can see that the DSP is trying to read the flash again (clock and MOSI activity) but AGAIN the CS1 is not active. I will assume that the boot parameter table is wrong...

    So this query is closed and I am moving to the next one.

    Thanks for your help, I wish I could talk to you on the phone.

    Aymeric