09-13-2017 05:09 AM - edited 09-13-2017 05:10 AM
Have you gone to the LINX forums yet? It was very helpful to me to get my setup up and running.
09-13-2017 12:00 PM
My device is a Raspberry Pi 3, should I still do it?
09-13-2017 12:17 PM
Yea I would try it. I’ve done it with a Pi 3, you may just have a slightly newer one and they may have bumped up the CPU. It’s not going to treat it as a RBP 2, all that change will do is allow the example to launch because it will identify you Pi as something other than unknown.
09-18-2017 05:52 AM
Well, I tried it and the problem still persists..
I created another case to recognize the BCM2835 as a Raspberry Pi 2 but it still gives me the same message.. Now what?
09-18-2017 08:46 AM
Raspberry Pi 2 or Raspberry Pi 2 B? It has to be Raspberry Pi 2 B exactly as the original case.
When you try to launch an example, it first checks to make sure that the device type isn't just blank.
Then it checks to make sure it is either Raspberry Pi 2 B or BeagleBone Black, and those are exact, spaces and capitals matter.
The message that pops up and says "...is not a supported LINX target.", does it still say unknown or does it say "Raspberry Pi 2" now? If it still says unknown, then it is either not executing the BCM2835 case or you are returning the wrong device type string. it's probably the former, as you also need to add BCM2835 to the regex array as well. It is likely returning BCM2835 but since it isn't searching for that string, the default case gets called returning a device type of Unknown.
09-18-2017 08:50 AM
To get it to be recognized on a Windows network by name, I believe you have to configure Samba; otherwise, just access it by its IP address. it should come up as RP2.
09-19-2017 12:18 PM
This solved it for me:
Aparently the issue was the version of the raspbian
09-19-2017 03:48 PM
Glad you sorted it out... and THANK YOU for posting your findings and marking your post as the solution. This will enable people that have the same problem to have an easier time solving their issue than you did. (Sorry, someone has to blaze the trail, right?) 😄
09-19-2017 03:50 PM
I’m curious with the older Raspian, does it now identify it as a BCM2709?
11-14-2017 03:24 PM
thank you very much. it worked out for me
@Liepo wrote:
This solved it for me:
Aparently the issue was the version of the raspbian