My EVM has old revision in it. Hope for a quick response. Jul 26, 2: If you have further questions related to this thread, you may click “Ask a related question” below. Then what is section I don’t have time right know to work on that problem but i can test solutions if anyone have.
|Date Added:||8 April 2018|
|File Size:||65.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
We use a bit addressable SPI flash.
This thread has been locked. I sspi figure out how the SPI boot works. Provided you get drivers for the BGW from Philips and port them to the DM, you should be able to use this as a solution. Feb 8, 6: Then what is section In reply to Veeranna Hanchinal: TI is a global semiconductor design and manufacturing company.
Linux/TMS320DM355: DM355 – SPI Bus Sample Code
Does it send the address LSB first? All content and materials on this site are provided “as is”. If you have further questions related to this thread, you may click “Ask a related question” below.
Aug 3, 7: But more details can be grabbed from SPI Controller driver in kernel or from chip-set datasheet. Feb 8, 9: We are glad that we were able to resolve this issue, and will now proceed to close this thread. Apr 1, 5: This thread has been locked. If you have a related question, please click the ” Ask a related question ” button in the top right corner.
[PATCH 00/49] spi: davinci: re-write existing driver, DM DMA problem
Ask a related question Ask a new question. If it helps i have tested before the spi patch V5 from Brian Niebuhr and the problem was already there.
Ask a related question What is a related question? In reply to David Smith Also, create a valid devnode using “mknod” command.
[3/6] DaVinci: Update for SPI support on DM SOC – Patchwork
We are glad that we were able to resolve this issue, and will now proceed to close this thread. I didn’t dig deep into the driver i just solved the problem quick and dirty by setting tx buffer to zero in the spidev driver. The glitch appears because the code attempts to read the last byte despite the fact that the previous bytes were all correct. I replaced the linux 2.
If only they had that in the datasheet, it would’ve saved me a whole lot of time. Go to Support forums. It appeared that when dm was reading on the spi, it was actually resending received data to our slave device on the spi bus, dm535 didn’t.
Additional info for DM355 SPI Boot
No license, either express or implied, by estoppel or otherwise, spo granted by TI. It appeared that when dm was reading on the spi, it was actually resending received data to our slave device on the spi bus, i didn’t fully checked what i am saying i am just supposing that it’s what occured.
Am I missing something?