Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

[Robert Nelson]

On Sun, Jan 7, 2018 at 8:19 PM, Robert Nelson  wrote:
>> One useful mitigation:
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-January/552243.html
>
> Okay, that's a lot better..
>
> From ARM's website, it really looked like ARM didn't care about the
> arm32 (A8/A9/A15/A17) family...

PS, it would be nice to see a proof of concept exploit on the A8, then
we can prove
those mitigation actually work.. ;)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjjWUbaGa_xLN3KDjNL7BMAZ1HsQWT-EMzvjsP4msjYAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

[Robert Nelson]

> One useful mitigation:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-January/552243.html

Okay, that's a lot better..

>From ARM's website, it really looked like ARM didn't care about the
arm32 (A8/A9/A15/A17) family...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjUeNbECE7FuR2NUN5QCEKz3%3DheEjtDEkQfXaNuVBz9%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to use PocketBeagle CAN Pins?

[Robert Nelson]

On Sun, Jan 7, 2018 at 5:36 AM,   wrote:
> Hello Folks!
>
> We are currently experimenting with the PocketBeagle CAN Connection but
> haven't got much success yet. The PocketBeagle will be connected to a car.
> To accomplish this we use a CAN Board
> (https://www.waveshare.com/sn65hvd230-can-board.htm) in connection with  a
> step down converter and a OBD2 Male Connector.
>
> Our first thought was that we can use the dcan1 Pins (P2.09 for RX, P2.11
> for TX) to connect the hardware and just test everything with the socketcan
> tool - without success.
>
> We then tried different Tutorials:
> http://www.thomas-wedemeyer.de/beaglebone-canbus-python.html
> http://www.instructables.com/id/DIY-Beaglebone-CAN-Bus-Cape/
> They didn't work either.
>
> Another problem is that there is almost no documentation on how to use the
> PocketBealge CAN or maybe we just can't find it.
>
> Has someone got a good tutorial or hints how to use the CAN Pins correct? Do
> we need the Device Tree Overlays? How can we test that a Device Tree Overlay
> is working properly or something is connected to the CAN pins?
> We are really thankful for any advise or solution!

https://github.com/beagleboard/pocketbeagle/wiki/Peripherals

If you see any mistakes feel free to help improve ^ it..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjXcAXRL8t2uCjAM6q_FRdabuv2%2BMQhcuCy-MxGsh3PfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

[Jason Kridner]

> On Jan 7, 2018, at 7:01 PM, 'Roberts Maria' via BeagleBoard 
>  wrote:
> 
> 
> 
> On Sun, 1/7/18, Jason Kridner  wrote:
> 
> Subject: Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?
> To: beagleboard@googlegroups.com
> Date: Sunday, January 7, 2018, 11:50 PM
> 
> On Sun, Jan
> 7, 2018 at 1:59 PM Robert Nelson 
> wrote:
> On Sun,
> Jan 7, 2018 at 12:52 PM, 'Luther Goh Lu Feng' via
> BeagleBoard
> 
> 
> wrote:
> 
>> I am under the impression that BBB is affected as it
> runs AM335x 1GHz ARM® Cortex-A8. What are the
> mitigations/recommendations to address this, if any?
> 
> 
> 
> Well, according to "ARM":
> 
> 
> 
> https://developer.arm.com/support/security-update
> 
> 
> 
> No :  indicates not affected by the particular variant.
> 
> Yes : indicates affected by the particular variant but has
> a
> 
> mitigation (unless otherwise stated).
> 
> 
> 
> Cortex-A8
> 
> 
> 
> Variant 1:Yes (under review)
> 
> Variant 2: Yes
> 
> Variant 3: No
> 
> Variant 3a: No
> 
> This leaves a lot of questions for
> me. TI is working on a more formal response that better
> summarizes our/their position. There are a number of
> mitigations, but I think more analysis should be performed
> to determine the confidence-level they provide. GKH has some
> thoughtful blog material, but also stops short of being
> conclusive. I've heard some question if VFP or NEON
> provide additional attack vectors.
> Fundamentally, I think those of us
> making embedded systems need to be conscientious of what
> untrusted code we allow to run on our systems and that there
> are likely more interesting attack vectors, depending on how
> we secure our systems.
> For example, do you disable ssh and
> evaluate the security of other network-based servers on the
> system? I just mean that Meltdown and Spectre attacks assume
> some ability to run userspace code on your system and you
> should probably already be preventing that. IoT
> worms/trojans and/or web server overflow bugs are more
> likely to be a security issue in an embedded
> system.
> In yet more
> other words, security requirements should be considered at a
> system-design level and a one-size-fits all solution of
> chasing down the latest issues facing desktop systems
> isn't likely to address your security
> needs.
> Hope this
> didn't come across as deflective or rude, as I do think
> a good analysis of the BeagleBone/BeagleBoard risks related
> to Meltdown/Spectre are necessary. I just don't think
> the analysis or the mitigations are ready to declare at this
> time.

One useful mitigation: 
http://lists.infradead.org/pipermail/linux-arm-kernel/2018-January/552243.html

> In addition to
> Robert's link, you can read 
> http://www.kroah.com/log/blog/2018/01/06/meltdown-status/ as
> well. The ARM recommended mitigations
> look a bit complex at this point, but are worth examining if
> you have concerns about the information that can be
> recovered using these attack methods and your system is
> exposed to them.
> 
> 
> 
> Regards,
> 
> 
> 
> --
> 
> Robert Nelson
> 
> https://rcn-ee.com/
> 
> 
> 
> --
> 
> For more options, visit http://beagleboard.org/discuss
> 
> ---
> 
> You received this message because you are subscribed to the
> Google Groups "BeagleBoard" group.
> 
> To unsubscribe from this group and stop receiving emails
> from it, send an email to beagleboard+unsubscr...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjY%3DG3nEF7eCYi8tmSdRPdxCRbvaRhfOfDt4n-ak%2BqveA%40mail.gmail.com.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> --
> 
> https://beagleboard.org/about
> 
> 
> 
> -- 
> 
> For more options, visit http://beagleboard.org/discuss
> 
> --- 
> 
> You received this message because you are subscribed to the
> Google Groups "BeagleBoard" group.
> 
> To unsubscribe from this group and stop receiving emails
> from it, send an email to beagleboard+unsubscr...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QP%3DixDcmWjOviCTkOPWfq%3D2iUFYsTZ0Jp7YnZ6GeJpLbOA%40mail.gmail.com.
> 
> For more options, visit https://groups.google.com/d/optout.
> n aceste conditii  la 17 august 1867  incepea guvernarea celui de-al doilea 
> 3t liberal'care are la baza intelegerea de la Concordia . Prim-ministru este 
> nnat stefan Golescu  care activase in guvernele revolutionare de Ia 1848 si 
> lase un guvern al tarii Romanesti in 1861.
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/1731300903.2172029.1515369697061%40mail.

[beagleboard] How to use PocketBeagle CAN Pins?

[Igor . shmelev]

Hello Folks!

We are currently experimenting with the *PocketBeagle CAN Connection* but 
haven't got much success yet. The PocketBeagle will be connected to a car. 
To accomplish this we use a CAN Board 
(https://www.waveshare.com/sn65hvd230-can-board.htm) in connection with  a 
step down converter and a OBD2 Male Connector.

Our first thought was that we can use the dcan1 Pins (P2.09 for RX, P2.11 
for TX) to connect the hardware and just test everything with the socketcan 
tool - without success.
 
We then tried different Tutorials:
http://www.thomas-wedemeyer.de/beaglebone-canbus-python.html
http://www.instructables.com/id/DIY-Beaglebone-CAN-Bus-Cape/ 
They didn't work either.

Another problem is that there is almost no documentation on how to use the 
PocketBealge CAN or maybe we just can't find it.

Has someone got a good tutorial or hints how to use the CAN Pins correct? 
Do we need the Device Tree Overlays? How can we test that a Device Tree 
Overlay is working properly or something is connected to the CAN pins? 
We are really thankful for any advise or solution! 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3702f2b3-2207-495f-9c67-54ea506726c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Enable can0, can1, adc and spi0 with dtb-rebuilder (Debian Jessy 8.4, 4.4.9-ti-r25)

[math19_19]

 Hi,
 I´ve installed this image: bone-debian-8.4-iot-armhf-2016-05-13-4gb.img

>  The Kernel Version is: 4.4.9-ti-r25
 I followed your instructions and I don´t get any error or warning 
messages. Everything looks good.

>  On one side is BeagleBone Black, on other side is IXXAT CAN-USB adapter 
and then Notebook(Test with software Mini Mon V3).
 The Can-Transceiver is between.
 When I send a message , I only see something like a one "clock" (no full 
message) on the oscilloscope(but only once at the start).
 A message is not sent. On the oscilloscope(measuered on TX-pin on 
BBB-P9_26 or P9_20) I don´t see message which I have sent.
 *Why can´t the message be created on the pin?*
 If you can, please help me!
 Thank you and best regards,
 Math

> 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cc6c6328-8271-4140-af99-8b6ddb548ef7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

['Roberts Maria' via BeagleBoard]

On Sun, 1/7/18, Jason Kridner  wrote:

 Subject: Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?
 To: beagleboard@googlegroups.com
 Date: Sunday, January 7, 2018, 11:50 PM
 
 On Sun, Jan
 7, 2018 at 1:59 PM Robert Nelson 
 wrote:
 On Sun,
 Jan 7, 2018 at 12:52 PM, 'Luther Goh Lu Feng' via
 BeagleBoard
 
 
 wrote:
 
 > I am under the impression that BBB is affected as it
 runs AM335x 1GHz ARM® Cortex-A8. What are the
 mitigations/recommendations to address this, if any?
 
 
 
 Well, according to "ARM":
 
 
 
 https://developer.arm.com/support/security-update
 
 
 
 No :  indicates not affected by the particular variant.
 
 Yes : indicates affected by the particular variant but has
 a
 
 mitigation (unless otherwise stated).
 
 
 
 Cortex-A8
 
 
 
 Variant 1:Yes (under review)
 
 Variant 2: Yes
 
 Variant 3: No
 
 Variant 3a: No
 
 This leaves a lot of questions for
 me. TI is working on a more formal response that better
 summarizes our/their position. There are a number of
 mitigations, but I think more analysis should be performed
 to determine the confidence-level they provide. GKH has some
 thoughtful blog material, but also stops short of being
 conclusive. I've heard some question if VFP or NEON
 provide additional attack vectors.
 Fundamentally, I think those of us
 making embedded systems need to be conscientious of what
 untrusted code we allow to run on our systems and that there
 are likely more interesting attack vectors, depending on how
 we secure our systems.
 For example, do you disable ssh and
 evaluate the security of other network-based servers on the
 system? I just mean that Meltdown and Spectre attacks assume
 some ability to run userspace code on your system and you
 should probably already be preventing that. IoT
 worms/trojans and/or web server overflow bugs are more
 likely to be a security issue in an embedded
 system.
 In yet more
 other words, security requirements should be considered at a
 system-design level and a one-size-fits all solution of
 chasing down the latest issues facing desktop systems
 isn't likely to address your security
 needs.
 Hope this
 didn't come across as deflective or rude, as I do think
 a good analysis of the BeagleBone/BeagleBoard risks related
 to Meltdown/Spectre are necessary. I just don't think
 the analysis or the mitigations are ready to declare at this
 time.
 In addition to
 Robert's link, you can read 
http://www.kroah.com/log/blog/2018/01/06/meltdown-status/ as
 well. The ARM recommended mitigations
 look a bit complex at this point, but are worth examining if
 you have concerns about the information that can be
 recovered using these attack methods and your system is
 exposed to them.
 
 
 
 Regards,
 
 
 
 --
 
 Robert Nelson
 
 https://rcn-ee.com/
 
 
 
 --
 
 For more options, visit http://beagleboard.org/discuss
 
 ---
 
 You received this message because you are subscribed to the
 Google Groups "BeagleBoard" group.
 
 To unsubscribe from this group and stop receiving emails
 from it, send an email to beagleboard+unsubscr...@googlegroups.com.
 
 To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjY%3DG3nEF7eCYi8tmSdRPdxCRbvaRhfOfDt4n-ak%2BqveA%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
 
 
 
 --
 
 https://beagleboard.org/about
 
 
 
 -- 
 
 For more options, visit http://beagleboard.org/discuss
 
 --- 
 
 You received this message because you are subscribed to the
 Google Groups "BeagleBoard" group.
 
 To unsubscribe from this group and stop receiving emails
 from it, send an email to beagleboard+unsubscr...@googlegroups.com.
 
 To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QP%3DixDcmWjOviCTkOPWfq%3D2iUFYsTZ0Jp7YnZ6GeJpLbOA%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
 n aceste conditii  la 17 august 1867  incepea guvernarea celui de-al doilea 3t 
liberal'care are la baza intelegerea de la Concordia . Prim-ministru este nnat 
stefan Golescu  care activase in guvernele revolutionare de Ia 1848 si lase un 
guvern al tarii Romanesti in 1861.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1731300903.2172029.1515369697061%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] fbdev and ssd1306

[Mark Grosen]

I am trying to get the kernel driver for the ssd1306 working with the
PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
I know it is physically working as I can use it via user-mode I2C. I
believe a small change is needed to support the unusual 64 pixel width of
this board. I have built and loaded a new kernel and have a .dtbo loaded
via u-boot with 4.4.88-ti-r128 kernel. It shows up in /proc/device-tree
correctly (at least as far as I can tell - the entries match the dts
values). I am missing how to get this connected to the framebuffer world -
there is no /dev/fb0 showing up. I see the config options appear to be
enabled (I am using the defconfig). My googling did not turn up anything
other than others stuck in a similar situation on RPi's.

Mark

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAL8ugEdZAp6n6Upwf0%2B%3DSV%3D%2BE35hDRPABM5Dgb21%2B6Dq3eC9GA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

[Jason Kridner]

On Sun, Jan 7, 2018 at 1:59 PM Robert Nelson 
wrote:

> On Sun, Jan 7, 2018 at 12:52 PM, 'Luther Goh Lu Feng' via BeagleBoard
>  wrote:
> > I am under the impression that BBB is affected as it runs AM335x 1GHz
> ARM® Cortex-A8. What are the mitigations/recommendations to address this,
> if any?
>
> Well, according to "ARM":
>
> https://developer.arm.com/support/security-update
>
> No :  indicates not affected by the particular variant.
> Yes : indicates affected by the particular variant but has a
> mitigation (unless otherwise stated).
>
> Cortex-A8
>
> Variant 1:Yes (under review)
> Variant 2: Yes
> Variant 3: No
> Variant 3a: No
>

This leaves a lot of questions for me. TI is working on a more formal
response that better summarizes our/their position. There are a number of
mitigations, but I think more analysis should be performed to determine the
confidence-level they provide. GKH has some thoughtful blog material, but
also stops short of being conclusive. I've heard some question if VFP or
NEON provide additional attack vectors.

Fundamentally, I think those of us making embedded systems need to be
conscientious of what untrusted code we allow to run on our systems and
that there are likely more interesting attack vectors, depending on how we
secure our systems.

For example, do you disable ssh and evaluate the security of other
network-based servers on the system? I just mean that Meltdown and Spectre
attacks assume some ability to run userspace code on your system and you
should probably already be preventing that. IoT worms/trojans and/or web
server overflow bugs are more likely to be a security issue in an embedded
system.

In yet more other words, security requirements should be considered at a
system-design level and a one-size-fits all solution of chasing down the
latest issues facing desktop systems isn't likely to address your security
needs.

Hope this didn't come across as deflective or rude, as I do think a good
analysis of the BeagleBone/BeagleBoard risks related to Meltdown/Spectre
are necessary. I just don't think the analysis or the mitigations are ready
to declare at this time.

In addition to Robert's link, you can read
http://www.kroah.com/log/blog/2018/01/06/meltdown-status/ as well.

The ARM recommended mitigations look a bit complex at this point, but are
worth examining if you have concerns about the information that can be
recovered using these attack methods and your system is exposed to them.


> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjY%3DG3nEF7eCYi8tmSdRPdxCRbvaRhfOfDt4n-ak%2BqveA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
https://beagleboard.org/about

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QP%3DixDcmWjOviCTkOPWfq%3D2iUFYsTZ0Jp7YnZ6GeJpLbOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

[Robert Nelson]

On Sun, Jan 7, 2018 at 12:52 PM, 'Luther Goh Lu Feng' via BeagleBoard
 wrote:
> I am under the impression that BBB is affected as it runs AM335x 1GHz ARM® 
> Cortex-A8. What are the mitigations/recommendations to address this, if any?

Well, according to "ARM":

https://developer.arm.com/support/security-update

No :  indicates not affected by the particular variant.
Yes : indicates affected by the particular variant but has a
mitigation (unless otherwise stated).

Cortex-A8

Variant 1:Yes (under review)
Variant 2: Yes
Variant 3: No
Variant 3a: No

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjY%3DG3nEF7eCYi8tmSdRPdxCRbvaRhfOfDt4n-ak%2BqveA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Does Spectre and Meltdown affect Beaglebone Black?

['Luther Goh Lu Feng' via BeagleBoard]

I am under the impression that BBB is affected as it runs AM335x 1GHz ARM® 
Cortex-A8. What are the mitigations/recommendations to address this, if any?

--Luther

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1066082142.2039753.1515351147352%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.