Page 1 of 1

ClickID manifest not recognized for Thermo-30 board?

Posted: 12 Mar 2024 14:14
by spicacality@kelseymountain.org
Hello! I'm trying to use a Thermo-30 click board with my BeaglePlay. When my Beagle boots, I see the following messages in the log:

mikrobus_manifest:mikrobus_manifest_header_validate: manifest version too new (122.103 > 0.3)
mikrobus mikrobus-0: invalid manifest size -22

I've tried two boards, and they behave similarly, except that the shown version numbers are different. In the first case, the version was 84.something instead of 122.103.

After my problem with the first board, I spoke with someone on the BeaglePlay Discord, who suggested that maybe I had a bad board. However, now that the second board behaves similarly, I suspect the problem is something else. I'm hoping someone will have some ideas.

Thanks!

Note that the Thermo-30 board does claim to support ClickID.

Re: ClickID manifest not recognized for Thermo-30 board?

Posted: 17 Mar 2024 20:50
by IvanJeremic
Hi,

For anyone that might encounter a similar issue.

Thermo 30 click has an ID chip on board, but it doesn't have software support yet.

Our compilers do not support BeagplePlay at the moment, but you can still use our example code for Thermo 30 click as a reference:
https://github.com/MikroElektronika/mik ... s/thermo30

Regards,

Ivan.

Re: ClickID manifest not recognized for Thermo-30 board?

Posted: 22 Mar 2024 20:07
by spicacality@kelseymountain.org
Thanks for the information and the link! I appreciate that.

Peter