In my 21489 hardware platform similar with 21489 EZ-BOARD, the example project “SigmaStudio For SHARC Demo Application for ADSP-21489 processor” in CCES 2.8 could run properly. Booting from SPI flash(master mode) and controlling SigmaStudio schematic parameter(SigmaStudio schematic running on PC and a USB cable with USBi emulator is connected to the USBi interface on my hardware) share the same DPI pins(DPI01: SPI_MOSI / USBI_MOSI, DPI02: SPI_MISO/USBI_MISO, DPI03: SPI_CLK/USBI_SCLK). Generally, the USB cable with USBi emulator is connected to the USBi interface on my hardware after the booting operation. There may be a conflict when these two operations are going at the same time.
My question is that whether it is possible that controlling SigmaStudio schematic parameter through SPIB and different DPI pins(DPI09, DPI10, DPI11, DPI12) and booting from an SPI flash also through SPI and DPI pins(DPI01, DPI02, DPI03, DPI04). The USBi hardware has been reconnected to DPI pins(DPI09, DPI10, DPI11, DPI12).
I try modifying the example project, but parameter control does not work. I mainly modify three locations in the example project.
The main function in the “app.c” file.
oCommConfig.nSelectSPI = SELECT_SPI1; / SELECT_SPI0-> SELECT_SPI1/
The ConfigSPISRU function in the “initSPISRU.c” file
SRU (DPI_PB11_O, SPIB_CLK_I); / DPI_PB03_O -> DPI_PB11_O /
SRU (DPI_PB09_O, SPIB_MOSI_I); / DPI_PB01_O -> DPI_PB09_O /
SRU (DPI_PB12_O, SPIB_DS_I); / DPI_PB04_O -> DPI_PB12_O /
The SendBackChannelData function in the “backchannel.c” file