What interface are you talking to the AES core with?
Basically because it’s somewhat user-defined, it’s a little trickier to make a “nice” API here. If you’ve got an example can possibly try and help out as well.
i.e.: Assume using the register-based interface, if you keep the same address we use in the example AES implementation that you write key/text to it would be easier to make a more generic API. But in theory people can use any interface they want of course between the SAM3U & FPGA.
One caveat I thought of - we’re building the CW305 firmware in Atmel Studio, it didn’t have the nice stand-alone makefile that we added to other projects (like Ballistic Gel). I just pushed a commit for a “should work” Makefile (tested quickly using Ubuntu on Windows), it’s a little hacky right now as you need to run a “make clean” after every time.
If you’re using Atmel Studio the project might just open in that, which gives you debug etc.
Thanks,
-Colin