Part Number: AM6548 Other Parts Discussed in Thread: AM68 TI Friends and Family,
Knowing that OpenCL typically requires the GPU support (therefore, no support today for families such as AM62x) does anyone know of an OpenCL Layer or SW offering (third…
Part Number: AM6548
I am trying to configure a custom board using an AM6548 to us USB0 in peripheral mode but am running into issues. It does not appear to initialize properly. . Any assistance would be greatly apprecaited.
Here is the output of the…
Hello Eric,
Ok, it is good that you do NOT have PRU Ethernet running in the same PRU_ICSSG instance as your PWM code. PRU Ethernet uses the IEP timer in the PRU_ICSSG instance that it is running, so that would definitely mess with your PWM signal since…
Part Number: AM6548 Other Parts Discussed in Thread: TMDX654IDKEVM I'm having a very similar issue than: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1136409/am6548-lvds-fading-to-black-after-bootup
In my case I am able…
Part Number: AM6548 Is HSR and PRP supported on AM65xx processor family? Using PRU-ICSS hardware offloading, or just at the linux level?
And for PTP, is there any PRU-ICSS support in HSR to implement a transparent clock (between the two HSR ethernet ports…
Part Number: AM6548 Hi Ti,
Our EE engineering want to do compliance test on Ti83867 on our EVM board but got some problem.
We move to TI AM6548 EVM board with Linux RT inside and try to set the register of Ti83867 according to the document below:
https…
Part Number: AM6548 According to this post to disable trace in boardcfg file.
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1121582/am6548-using-all-uarts-on-linux/4161906
in the board_cfg.c, there is a define ENABLE TRACE…
Part Number: AM6548 Hi,
We are using XAM6548BACDXEAFS1 on our custom board and trying to load system firmware to the DMSC controller.
We have our own application running on the MCU R5 processor. The application is signed with the 'x509CertificateGen.ps1…
Hello Pratap,
Thank you for the answer, this solves our problem!
In the end, it was just a documentation issue.
In uniflash.html#rebuilding-uniflash-flash-programmer it is documented (same for SDK8.2)
# make BOARD=<Board Name> board_utils_uart_flash_p…