# Meta-resin announcemet **URL:** \ **Category:** Product support\ **Created:** [July 15, 2015, 11:44pm UTC](https://forums.balena.io/t/meta-resin-announcemet/82 "2015-07-15T23:44:33Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![heater](https://avatars.discourse-cdn.com/v4/letter/h/858c86/32.png) [@heater](https://forums.balena.io/u/heater)\ **Post date:** [July 15, 2015, 11:44pm UTC](https://forums.balena.io/t/meta-resin-announcemet/82/1 "2015-07-15T23:44:33Z")
It’s great to hear the announcement of the open sourcing of meta-resin. Unfortunately I can’t access the instructions linked to in the blog post. Chrome is complaining “Your connection is not private…When Chrome tried to connect to [docs.resin.io](http://docs.resin.io) this time, the website sent back unusual and incorrect credentials.” Firefox also complains “This Connection is Untrusted…” ---
**Author:** ![anon22468611](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@anon22468611](https://forums.balena.io/u/anon22468611)\ **Post date:** [July 16, 2015, 2:38pm UTC](https://forums.balena.io/t/meta-resin-announcemet/82/2 "2015-07-16T14:38:12Z")
Hey, We’re investigating an issue where the link is being automatically converted to https on some occasions, in fact the link _is_ valid - [http://docs.resin.io/#/pages/hardware/meta-resin.md](http://docs.resin.io/#/pages/hardware/meta-resin.md) - hopefully this gives you the information you need and we’ll look into fixing this issue! Best, Lorenzo ---
**Author:** ![anon22468611](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@anon22468611](https://forums.balena.io/u/anon22468611)\ **Post date:** [July 16, 2015, 3:26pm UTC](https://forums.balena.io/t/meta-resin-announcemet/82/3 "2015-07-16T15:26:46Z")
Ok I’m glad to say we have fixed this and this shouldn’t recur! ---
**Author:** ![heater](https://avatars.discourse-cdn.com/v4/letter/h/858c86/32.png) [@heater](https://forums.balena.io/u/heater)\ **Post date:** [July 16, 2015, 4:29pm UTC](https://forums.balena.io/t/meta-resin-announcemet/82/4 "2015-07-16T16:29:08Z")
Great, now I can get in. Thanks. Only one problem. I’m lost at the first paragraph "Pre-requisites: yocto BSP layer for your particular board. Should be compatible to yocto fido " Do what? So I have a bunch of ISEE IGEP v2 ARM boards, currently running Debian Wheezy from SD card. The boot loader can boot into an image on on board FLASH. I seem to recall it is something from Linaro. What to do to get resin on there? Sounds like I need to dedicate some time to researching this Yocto thing and it’s BSP’s ---
**Author:** ![agherzan](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@agherzan](https://forums.balena.io/u/agherzan)\ **Post date:** [July 20, 2015, 9:46am UTC](https://forums.balena.io/t/meta-resin-announcemet/82/5 "2015-07-20T09:46:56Z")
Hello, First of all thank you for your shown interest in meta-resin and devices support. Sorry for the confusion related to yocto version “fido”. Yocto releases twice per year and you can see [here](https://wiki.yoctoproject.org/wiki/Releases "here") the ones that were already done and the next to be released. Our current yocto layers are developed for the fido version which means that all the dependencies of these layers need (or is recommended) to be based on fido (obviously, this includes poky itself). In order to add resin support for a board, the first step is to search or develop a BSP layer. Generally a BSP layer includes kernel, bootloader, gl libraries, all being specific for that board. I searched the internet and the yocto support for the ISEE IGEP board seems to be already done but only for older releases of yocto ([see here](http://git.isee.biz/?p=pub/scm/meta-isee.git "see here")) which means there could be some time needed to be invested in order to make it work with out code or upgrade it to yocto fido. The above mentioned support is not officially recorded as yocto layer ([oe layers](http://layers.openembedded.org/)) so this means that is either work in progress or is just not known to yocto community (oe). As soon as you get through these basic requirements, following the document should get you to a new supported board. Be aware though that this document is still in early beta stages so feel free to ask questions and we will support you through this new board adoption process as much as we can. Regards, Andrei