Part Number: PROCESSOR-SDK-AM57X
We have migrated our development from SDK 6.02 to SDK 8.02. However, when building our application from a Yocto build instead of building in my local machine I got compilation errors.
The problem is because of the name…
Part Number: PROCESSOR-SDK-AM57X When the newe processor sdk (based on Kirkstone branch of Yocto) gets released, how will the users (e.g. me) be informed? Where can I notice the announcement?
Hello Sebastian,
Yes, this is usually done using CCS Memory browser, see the following thread: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1250542/pru-icss-industrial-sw-hsr-prp-transmit-not-working-for-our-custom-board-with…
Part Number: PROCESSOR-SDK-AM57X Tool/software: Lots of these messages:
The u-boot-ti-staging:do_create_srcipk sig is computed to be 429b7b18db9de85edacc1537f6335305313ded17bb878dcddaab8620aab43149, but the sig is locked to 417c4d2ed011df5142886c59233ee2669b12a44dd2783380102401284e6c22f7…
Part Number: PROCESSOR-SDK-AM57X Target AM57x
I am having a problem running a very simple DSP program on both dsp1 and dsp2. The program being used just creates a main task, starts BIOS, and workspace_dsp_hello.tar.gz the task prints a message and then…
Sebastian,
I am glad you have this fixed. As I mentioned before, both PRU drivers in both SDKs have the same initialization of memory to zero
Josue Zamitiz-Ayala said: both prueth.c from SDK 6.3 and prueth_core.c from SDK 8.2 have the same function that…
Hello again! I ended up using a "fake" or "dummy" GPIO IRQ to inform the A15 about the the change in the buffer. It's a bit strange, but it sure does the trick. In the IPU1 code I used:
#define IPU1_REGS_OFFSET …
Part Number: PROCESSOR-SDK-J784S4 Tool/software: Hi TI Experter,
I would like to uninstall the older version of PROCESSOR-SDK-LINUX-J784S4. Can you show me how to uninstall it? Thanks