debian testing: 2017-03-12

GoogleGroups
1

Howdy!

I just pushed out another round of images for testing, this time we
have a new decicated u-boot overlay image.

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2017-03-12

Big changes...

Windows 7, 8, 8.1, 10.. No external driver required (network interface
thanks to David and Jason)

While 7 needs a usb-cdm driver (built-in 8/8.1/10)

WinXP, sorry, it's EOL...

U-Boot Overlays:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_lxqt_U-Boot_Overlay

Here are the current supported confict capes: (aka they need
hdmi/emmc/etc to be disabled)

/lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo
/lib/firmware/NL-AB-BBCL-00B0.dtbo
/lib/firmware/BB-GREEN-HDMI-00A0.dtbo
/lib/firmware/BB-BONE-LCD7-01-00A3.dtbo
/lib/firmware/BB-BONE-4D5R-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4R-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D5N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D5C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7R-01-00A1.dtbo
/lib/firmware/BB-BONE-LCD4-01-00A1.dtbo

don't see your cape on the conflict list, time to test...

Here is the /boot/uEnv.txt options for U-Boot overlays if your cape
doesn't have an eeprom:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays\

and yes, this image, ssh over root is now disabled, to re-enable see:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#i_take_full_responsibility_for_knowing_my_beagle_is_now_insecure

Regards,

2

Robert,

heh, i like the hash tag for the last link.

Would you say that these images to the best of your knowledge are stable enough to test on a “production” system? e.g. a test system that is looking towards production. I wouldn’t mind testing, but I do have work to complete as well. What we’re using is mostly I2C( perhaps I2C1 or the unused bus ), and the rest would be standard Debian / Linux utilities, with some custom software tossed in. Mostly shell script, with a sprinkling of golang + C.

3

Yeah, we are back to being more stable again.. The Windows Driver
"patch" required lots of changes behind the scenes to now deal with
the "dual" usb-ethernet adapters.

Regards,

4

OK, cool.So what I should be able to test over the next month or hopefully
sooner is:

   - i2c-1 - multiple devices on the bus
   - ds3232 real-time clock.
   - Cape eeprom's
   - D20B18 one-wire temp sensor
   - the beaglebone's ADC, 2 channels.
   - *Maybe* PWM
   - uboot overlays for all of the above.
   - At some point I may need to rewrite, or changed the existing PMIC /
   battery capabilities through acpid - I could use a link to the beaglebone
   source for this package by the way. Which I should be able to contribute
   back.

Various other mechanisms such as systemd services / timers etc. Which I
doubt would have and flaws.

Is the overlay you're loading for all the stock stuff at boot still done
through the generic-overlay service ? I really need to disable all the USB
gadget stuff, as it can conflict with some of our systems which run a 3G/4G
modem over USB.

5

Yeah, just:

sudo systemctl disable generic-board-startup.service

and then the usb gadget won't load.

Regards,

6

Yeah,sorry about that, had overlays on the mind, and couldn’t find my workflow file easily to remember the name of the service.