I have some assembly code software running on a M5208EVBe board and a Freescale Coldfire processor. I am able to load the code and run it (by setting the pc to the start of the code) in both the BDM debug mode (with GDB debugger), and by using the dBUG terminal program loaded into the ram of the processor during default startup. However, despite running all my QSPI setup commands (which wiggle the pins in simulation), no SPI activity occurs on the pins at all. CSB is stuck low, while the QCLK is also stuck low.
For reference, here is a list of all the registers I set:
0xA102 into QMR
0x0100 into QIR
0x01 into ICR31
0x0400 into QDLYR
0x0020 into QAR
0x8e00 into QDR (5 times, autoinc each time)
0x0000 into QAR
(various data) into QDR
0x1400 into QWR
0x8400 into QDLYR to start!
and nothing happens. The interrupt does work, but it hoses the program because I don't know how to set the interrupt vector table using dBUG.
I have searched the forum and the FAQs for answers to this question and I have not seen one.
Thanks!
Niel
Did you remember to set the QSPI Pin Assignment Register (PAR_QSPI) to set those pins to their primary (QSPI) functions (as opposed to the default GPIO functions)?
-- Rich
PS See reference manual section 13.3.5.5.
Well it looks like I did forget to set the PAR_QSPI bits correctly. I went back and set those bits correctly as well as the PAR_UART bits. However, I still don't see any wiggling of the spi signals on the eval board, except the qspi_clk (labeled QCLK) is now high.
Any more ideas? This has really got me stumped.
Thanks,
Niel