Zackery
Zackery
Hello @madscientist42, thanks for the feedback on our yocto layer. This seems to stem from the README not properly reflecting on how you can use the layer. This is because...
@G-E-N-E Thanks for your comment. I see the issue you are talking about and I am able to reproduce it. Your suggestion of: `EXTRA_OECONF += "${@bb.utils.contains('IMAGE_INSTALL', 'wolfclu', '--enable-wolfclu', '', d)}"`...
Reviewed again and it seems that resulting script that gets created by libtool uses the host system's paths and not the target systems paths. Examples: `relink_command="(cd /home/msi-debian/WolfWork/yocto/kirkstone/build/tmp/work/core2-64-poky-linux/wolftpm/3.2.0-r0/build; { test -z...
Bug with MAA report here for visibility: https://github.com/analogdevicesinc/msdk/issues/1089 I will be looking to file a ticket on Analogs website as well.
I do plan on fixing, max3266x.c and max3266x.h to use proper wolfSSL types. Have had some compile issues when using `byte` instead of `char` type
Jenkins retest this please
Jenkins retest this please
Rebased the PR and added expanded mutexing options
Added in Ability to use Callbacks with ARM ASM AES/SHA along with SHA Callbacks for the Hardware. Also potential fix for SHA Bug when using Callbacks. ARM ASM Settings: ```...
Jenkins retest this please