Other Parts Discussed in Thread: SK-AM64B, TCA6424
Tool/software:
Tool/software:
Hi Prashant,
Building the keywriter.bin is somewhat procedural for us, we did just enough to create and include our keys, certs and enable Vpp. We don't normally use CCS, nor have we developed any application firmware for the R5F.
How do we 'connect' to the R5F core? Is there some additional h/w (e.g. a JTAG debug probe) necessary? Is there a specific document you can point us to that would help us get this up and running?
Thanks,
Lee
Hello,
The keywriter package does not provide the support for the SK-AM64B board. If you are still running the provided keywriter example on this board then the failure is expected for the reasons described in the following response:
Regards,
Prashant
Hi Prashant,
First, note our board does have an eMMC (on MMC0) and we don't use an I2C IO expander for Vpp enable. We are confident that we're controlling Vpp enable using a GPIO.
None-the-less, we'd still like to see the OTP programming steps run on the SK-AM64B eval board.
We implemented the changes suggested in https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1473209/processor-sdk-am64x-flashing-otp-keywriter-per-sd-card/5669823 by removing the references to the EMMC from the example.syscfg file:
Please confirm this is effectively the same change as suggested using the GUI.
We also implemented the changes suggested in https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1198808/faq-how-to-run-otp-keywriter-on-sk-am64b, noting:
the path mentioned in the helper script contained a ‘tifs’ sub-dir, we removed it (as it doesn’t exist) in the build
we set ‘Vpp enable' LOW as we don’t want it to actually write the OTP, just attempt to do so (and see it fail)
Everything compiles.
No difference to the original outcome. Specifically the UART1 (J12) trace output stops at:
0x61C0003D: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 61 Clock ID: 0
and no output on UART0 (J11).
If the trace output stops at '0x61C0003D', does any code from 'sbl_keywriter/am64x-evm/r5fss0-0_nortos/ti-arm-clang/', i.e. main.c or board.c, even run?
Also (an earlier question), how do we 'connect' to the R5F core? Is there some additional h/w (e.g. a JTAG debug probe) necessary? Is there a specific document you can point us to that would help us get this up and running?
Thanks,
Lee
Hello,
Also (an earlier question), how do we 'connect' to the R5F core? Is there some additional h/w (e.g. a JTAG debug probe) necessary? Is there a specific document you can point us to that would help us get this up and running?
Please see if the following guide helps:
Regards,
Prashant
Hi Prashant,
Thanks for your continued support.
Hello,
Can you think of anything we can try to re-assure ourselves that the observed/marginal behavior only occurs when using keywriter.bin and not when we're booting/running our normal application code?
Without knowing the eMMC failure signature, I can't say for sure if the issue won't occur in the normal application code. The keywriter doesn't have any use of eMMC so it should definitely not include the eMMC. As for the application, you may test it continuously. If the issue occurs, please feel free to create a separate thread.
Thanks!