Followed the instructions precisely, and am getting "unable to determine hardware version. I see hardware BCM2835"
I received this error when i tried earlier on the latest version of raspbian. Used the recommended version specified above and am still seeing the same error. I am using a Rpi 3b. help!
Update: edited config.json and changed simulated data from 'false' to 'true' and it gave the same error.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@mikebergin Thanks for the feedback. We are actively investigating and will get back to you soon.
@rangv The instructions for this tutorial need to be updated.
When I run the sudo nano index.js with my IoT Hub Connection String it only opens the index.js file, it does not start showing sensor data as the instructions say. Any thoughts as to why?
I have the raspberry pi working (messages being sent to my iot hub), when i simulate data. However, when i hook up my sense and change the simulate to false, i get this error:
{ [Error: , Remote I/O error] errno: 121, code: '', syscall: 'writeByte' }
How can i resolve this error?
Hi! Anyone who has resolved the { [Error: , Remote I/O error] errno: 121, code: '', syscall: 'writeByte' } error?
I too am getting the error : "unable to determine hardware version. I see hardware BCM2835". I have tried several different Raspberry Pi devices. Is there an updated sample which looks for the correct HW for RPI3B?
I too am getting the error : "unable to determine hardware version. I see hardware BCM2835". Do someone have a solution?
I am also facing this error "Unable to determine hardware version. I see: Hardware : BCM2835
This problem is caused by the wiringpi library cannot work on new version of system.
As this issue mentions, for a quick workaround, you can install wiringpi-node instead of wiring-pi.
1.Open the project with vs code
2.Run the command:
npm install wiringpi-node
3.Use require('wiringpi-node') instead of require('wiring-pi')
See Feedback article ''Unable to determine hardware version' error when running sample application' where a Kernel downgrade fixed this for me.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Why is this closed? What was the resolution?
Sent from my iPhone
On Dec 3, 2018, at 8:14 AM, António Sérgio Azevedo <[email protected]notifications@github.com> wrote:
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F7392%23issuecomment-443705806&data=02%7C01%7C%7Cdf3a47d07f0240a7c9ae08d6592151e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636794396967544905&sdata=ntLRx28uEkWqdOKCUxkcsa12IfpqYxl1wM3RuLGQ8lU%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAkuXIEgWeJMJGipUHZ8pd4jBHUvw-Q55ks5u1SPPgaJpZM4TaoeP&data=02%7C01%7C%7Cdf3a47d07f0240a7c9ae08d6592151e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636794396967544905&sdata=ELKwZrV%2F6bEv%2FQ4Ov1IrTmEDSmXrLMbz8kYOBlNBAeM%3D&reserved=0.
Hello @mikebergin , a PR was submitted to address this issue. Are you still facing the same issue?
Thank you.
Most helpful comment
@mikebergin Thanks for the feedback. We are actively investigating and will get back to you soon.