I ported a project from VDSP to CCES.
The only things that were modified were
- custom LDF with multiple heaps
- installing IRQ handlers
I use SPORT1 for receiving 8 channels in TMD8 mode.
The internally generated FS signal is routed to MISC_A. Before starting SPORTs and enabling IRQs, I wait for a falling FS edge.
Further, I use two ping pong buffers with a variable indicating which one is to be processed (the familiar int_cntr variable).
It is set to 1 initially.
Now, when the first IRQ is triggered, the first ping pong buffer (idx 0) should have been filled with the first N samples.
int_cntr is switched to 0, then and processing starts.
With VDSP, this works flawlessly.
In my CCES project, however, there are no input samples received when the first IRQ has been triggered.
Only on the second IRQ, the first input buffer has been filled.
When I set int_cntr to 0, initially, it works but that can't be right.
Do I miss anything?
The code is
adi_int_InstallHandler(ADI_CID_SPI1, isr_SPORT, 0, true);
Hi Rainer,Apologies for delayed response.Can you let me know which processor you are referring to?Regards,Anand Selvaraj.
Uh, sorry, that's indeed some important but missing information.
It's the 21489.
any ideas on this?
Hi Rainer,Sorry for getting back late on this issue. I don't find any issues with the way you have modified the interrupt initialization for CCES.However, in order to narrow down the issue, can you please get back on the below?1. How did you port the project from VDSP to CCES? Did you create a new project or used the Project Import Wizard Feature?2. Which version of CCES are you using?3. Can you let me know how you confirmed that data is not filled during the 1st interrupt?4. You mentioned that you have changed the LDF. In case you are using the Project Import Wizard to port from VDSP to CCES, this will add your custom LDF to the newly-created CrossCore Embedded Studio project, but it will not make any changes to the custom LDF itself. You will have to apply any changes yourself.Porting a customized LDF from VisualDSP++ to CrossCore Embedded Studio is not a trivial task. We would recommend first determining whether you still need a customized LDF with CrossCore Embedded Studio. The default LDF may be sufficient for your needs, or you may find that you can obtain a suitable configuration using the Generated LDF. If you really do need to customize your LDF beyond that which can be supported by a Generated LDF, we would recommend that you first generate the closest LDF you can, using the Startup Code/LDF Add-In, then disable the Add-in and customize the LDF further from this point.You can get more information and precautions to be taken care when porting VDSP project to CCES from the below FAQ.FAQ: Importing VisualDSP++ project files to CrossCore Embedded Studioez.analog.com/.../faq-importing-visualdsp-project-files-to-crosscore-embedded-studioHaving said this, can you let me know whether you testing this on a custom board or ADSP-21489 EZ-kit?Regards,Anand Selvaraj.