search

nortd / driveboardapp

Next generation Lasersaur control app.
http://www.lasersaur.com
15 stars 19 forks source link

default to beaglebone when flashing firmware. #6

Closed allartburns closed 7 years ago

allartburns commented 8 years ago

1) some of us have two lasersaurs and change the hostname on the second, so don't set beaglebone based on hostname

2) there is no 'standard' to test against, 'beaglebone' should be the default (INHO).

stefanix commented 7 years ago

I have changed the platform test slightly because it would fail on non-posix systems. Standard is the default because it does not require any initialization of GPIOs. This is the case when DriveboardApp runs on a laptop with a usb-to-serial converter.

As for the beaglebone, we check uname[1] == 'lasersaur' or uname[2] == '3.8.13-bone20' so for BBB systems the hostname check should be irrelevant because the second condition holds true. It's more for BBW systems any custom setups.

Let me know if you want to make this more specific to all the legacy systems. We can plug in some more conditions based on the uname[2] property for example.

allartburns commented 7 years ago

That’s still tying it to a specific linux version for BBB. Some unis are going to have IT departments that want security patches applied or account administration, that’s going to require an upgrade of linux.

for uname = os.uname() print uname

I get:

('Linux', 'laserdev', '3.14.22-ti-r31', '#1 SMP PREEMPT Sat Oct 25 01:30:27 UTC 2014', 'armv7l’)

On Nov 6, 2016, at 06:12, Stefan Hechenberger notifications@github.com wrote:

I have changed the platform test slightly because it would fail on non-posix systems. Standard is the default because it does not require any initialization of GPIOs. This is the case when DriveboardApp runs on a laptop with a usb-to-serial converter.

As for the beaglebone, we check uname[1] == 'lasersaur' or uname[2] == '3.8.13-bone20' so for BBB systems the hostname check should be irrelevant because the second condition holds true. It's more for BBW systems any custom setups.

Let me know if you want to make this more specific to all the legacy systems. We can plug in some more conditions based on the uname[2] property for example.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

J. Eric Townsend, IDSA designer | engineer | fabricator jet@functionalprototype.com PGP 0x9D6F2CB8

stefanix commented 7 years ago

changed it to: if linux, check Rpi, if not and if arm -> beaglebone

allartburns commented 7 years ago

sounds good, thanks.

On Nov 7, 2016, at 05:20, Stefan Hechenberger notifications@github.com wrote:

changed it to: if linux, check Rpi, if not and if arm -> beaglebone

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

J. Eric Townsend, IDSA designer | engineer | fabricator jet@functionalprototype.com PGP 0x9D6F2CB8