TMS570LS3137: EMIF Asynchronous Timing unable to Write/Read device properly

Hi David,

1. Please make your pinmux is configured correctly.
2. For memory interface, the EMIF address pin EMIF_A[0] always provides the least significant bit of a 32-bit word address. Therefore, when interfacing to a 16-bit asynchronous device, the EMIF_BA[1] pin provide the least-significant bits of the halfword. EMIF_BA[1] should be connected to Memory A[0] pin.
3. Suggest to try maximum value for SETUP, STROBE, and HOLD fields in CE2FFG register first, make sure your setup work.

Deleting this reply as it was bad hardware. Will update with good hardware in a following reply.

Thanks,

David Cothran

May have a hardware issue, I will let you know when we get it resolved and if we have any more issues!

I apologize for the inconvenience.

Thanks,

David Cothran

Hi David,

Most likely, the problem is caused by the timing. Any special requirements for setup, strobe, and hold for the EMIF device? Can you lower the EMIF clock to 16MHz too?

QJ,

We found out our oscillator was bad for our first chip and replaced it with another. We have verified the oscillator is working and we are seeing much better results! Also is there a way to lower the EMIF clock to 16 MHz? The closest I see are 18MHz,16.364MHz, 15Mhz. Though I believe our oscillator has since resolved many issues. See Below.

The read seems to be working as far as we can tell (pic below), however we are having some issues on the write.

Current Register Settings

    emifREG->CE2CFG = (uint32_t)((uint32_t)1U << 31U) | // Strobe Mode Enable
                      (uint32_t)((uint32_t)1U << 30U) | // Extended Wait Enable
                      (uint32_t)((uint32_t)6U << 26U) | // W_SETUP
                      (uint32_t)((uint32_t)8U << 20U)| // W_STROBE
                      (uint32_t)((uint32_t)1U << 17U) | // W_HOLD
                      (uint32_t)((uint32_t)6U << 13U) | // R_SETUP
                      (uint32_t)((uint32_t)17U << 7U) | // R_STROBE
                      (uint32_t)((uint32_t)1U << 4U)  | // R_HOLD
                      (uint32_t)((uint32_t)3U << 2U)  | // TURN AROUND
                      (uint32_t)((uint32_t)emif_16_bit_port);

Test Code Section

    volatile uint32_t address;
    volatile uint16_t testval;

    /***************************** TEST READ ***************************/
    for(address = (uint32_t)STACK_A_ADDR; address < (uint32_t)RT_CMD_STACK_A_PTR; address++) // EDIT NOTE: THIS SHOULD BE address += 2 as it is 16-bit addressable
    {
        testval = *((volatile uint16_t *)address);
    }

    /***************************** TEST WRITE ***************************/
    testval = 10;
    for(address = (uint32_t)STACK_A_ADDR; address < (uint32_t)RT_CMD_STACK_A_PTR; address++) // EDIT NOTE: THIS SHOULD BE address += 2 as it is 16-bit addressable
    {
        gioPORTB->DOUT ^= 1 << 4U;  /* FLIP GIO Bit 4 */
        *((volatile uint16_t *)address) = ++testval;
        gioPORTB->DOUT ^= 1 << 4U;  /* FLIP GIO Bit 4 */
    }

Read Example

1. EMIF_ADDR[15] does not change even when attempting to OR bits 15 and 16 in the address itself (we attempted 16 because of the BA1 offset). Is this possible to manually operate as a memory/register pin or will we need to use something such as a GIO?

2. During the write, in normal mode, it will attempt to write 3 addresses during one nCS2 [active low] cycle. During the write, in strobe mode, it will attempt to write 3 addresses (while overwriting a previous "good" write). Resulting in data being written correctly and then overwritten incorrectly. Is this an MPU 'device' issue?

Picture below are some exampels of Writes in Strobe Mode, when only executing a single write command in code

Example 2

Thanks,

David Cothran

QJ,

Apologies for the chaos of this thread. The chip I was using is 16-bit addressable so the 8 bit addressing was not working for it and would also explain the overwriting of previous data (my bad). Another issue is possibly the emif_addr15/nREG line not moving (so the external chip thinks im only writing to registers).

I found an MPU example in the halcogen examples for the TMS570LS31x and initialized the MPU in the start of main for JUST region 5 (0x60000000 + 64KB) and that fixed the multiple writes as far as i can tell.

Now that everything looks relatively good, do you know how I can manually toggle the EMIF_ADDR[15] line? ORing bit 15 or 16 in the address (due to BA1 offset) to 1 or 0 seems to have no effect in the line.

Thanks,

David Cothran

QJ,

This answered all my questions but now I have one more.

1. Why is it 0x8000 *4 instead of *2? Should it not be left shift 1? Please explain.

Thanks again for all the help,

David Cothran