Re: [beagleboard] Re: slots file corrupt upon boot, can't echo to slots or export

well, that was the plan. really appreciate your attention, ciao, Michael On Wed, May 3, 2017 at 8:45 PM Robert Nelson wrote: > > > On May 3, 2017 10:11 PM, "michael c" wrote: > > yes, well that makes a lot of sense. i guess I inherited that from

Re: [beagleboard] Re: slots file corrupt upon boot, can't echo to slots or export

On May 3, 2017 10:11 PM, "michael c" wrote: yes, well that makes a lot of sense. i guess I inherited that from the ubuntu flash image. my BBB dev platform only needed a led and a switch so i hand-rolled my own overlay with my own ubuntu image at the time. but, our hardware is

Re: [beagleboard] Re: slots file corrupt upon boot, can't echo to slots or export

yes, well that makes a lot of sense. i guess I inherited that from the ubuntu flash image. my BBB dev platform only needed a led and a switch so i hand-rolled my own overlay with my own ubuntu image at the time. but, our hardware is coming this week and i have some critical needs i have been

Re: [beagleboard] Re: slots file corrupt upon boot, can't echo to slots or export

On Wed, May 3, 2017 at 7:44 PM, michael c wrote: > yeah, forgot the boot log > > > Press SPACE to abort autoboot in 2 seconds > board_name=[A335BNLT] ... > board_rev=[00C0] ... > switch to partitions #0, OK > mmc0 is current device > SD/MMC found on device 0 > ** Bad device

[beagleboard] Re: slots file corrupt upon boot, can't echo to slots or export

yeah, forgot the boot log Press SPACE to abort autoboot in 2 seconds board_name=[A335BNLT] ... board_rev=[00C0] ... switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 ** Bad device 0:2 0x8200 ** ** Bad device 0:2 0x8200 ** switch to partitions #0, OK mmc0 is

[beagleboard] slots file corrupt upon boot, can't echo to slots or export

Linux arm 4.4.62-ti-r99 #1 SMP Sat Apr 22 15:16:58 UTC 2017 armv7l armv7l armv7l GNU/Linux Ubuntu 16.04 upon booting slots looks like this # cat slots 0: -- -1 1: ---l-- -1 2: ---l-- -1 3: ---l-- -1 i can't write to /gpio/export or to any pin files. i tried replacing the kernel

Re: [beagleboard] RS485 support for BBB

Hello, I would like to get RS485 to work on my BBB which has kernel 3.8.13-bone79. The steps are not clear to me especially since I have little experience with embedded linux. I hit a wall when trying to load a modified version of Robert Nelson's BB-UART4-RS485--00A00

RE: [beagleboard] Drop in replacements for DRAM and eMMC modules

You can use any of the Micron replacements on the DRAM, they work fine. They have several different ones, all different speed grades, but any of those speed grades will work. As to eMMC, same, they just upgraded the controller in the eMMC to 5.1 and it is supported. Gerald From:

Re: [beagleboard] Use PWM and UART at the same time

Theodosis, did you get it to work? I have a small test.sh file containing #!/bin/bash config-pin P9.11 uart I tried both, systemd and rc.local, but in both cases i get "P9_xx pinmux file not found". If I run the script after logging in everything works fine. Am Dienstag, 8. November 2016

Re: [beagleboard] Drop in replacements for DRAM and eMMC modules

Its already being done. Special Computing is building NoLogo versions of BeagleBoneBlack with industrial temp rating for commercial use offering 1GB DRAM and 8GB eMMC on-board. https://specialcomp.com/beaglebone Special Computing also offers a mail-in service to rework an existing BeagleBone and

Re: [beagleboard] Drop in replacements for DRAM and eMMC modules

On Wed, May 3, 2017 at 3:28 PM, wrote: > HI all, > > I am working for a company in upstate NY that has incorporated the > Beaglebone Black into a product design. I posted here about a month ago > regarding the schematics and layout files for the Beaglebone Black (the >

[beagleboard] Drop in replacements for DRAM and eMMC modules

HI all, I am working for a company in upstate NY that has incorporated the Beaglebone Black into a product design. I posted here about a month ago regarding the schematics and layout files for the Beaglebone Black (the thread

[beagleboard] Re: Board fixup for phy: selecting location for phy_register_fixup_for_id

Hello A follow up for anyone with a similar question. I placed the function declaration in "include/linux/phy.h", the function body in "drivers/net/phy/phy-device.c", and registered the fixup in the same file at "__init phy_init()" after the "mdio_bus_init()" call. Two small differences from

Re: [beagleboard] Deep sleep & wake through GPIO and RTC

Hi flyingfred0! Not really; I haven't investigated more about this problem...I'm using rtcwake at the moment but I would be glad if you find a powerful standby mode way. Il giorno mercoledì 3 maggio 2017 17:27:08 UTC+2, flyin...@gmail.com ha scritto: > > The AM335x platform already includes a

Re: [beagleboard] Deep sleep & wake through GPIO and RTC

The AM335x platform already includes a Cortex M3 for exactly this purpose -- a low power MCU that can be used to wake the system on certain interrupts (http://processors.wiki.ti.com/index.php/AM335x_Power_Management_Standby_User%27s_Guide#Linux_Implementation) I don't yet have the wakeup

Re: [beagleboard] FATAL ERROR: Unable to parse input tree,does anyone know how to fix it ?

On Tue, May 2, 2017 at 9:47 PM, Riko Ho wrote: > hehehe, fsck yourself if you don't know how to answer...yes it is the sky > is blue..and don't worry to answer if you don't know..as simple as that. > > Done mate' > Except, I had a really good idea what your problem was,

[beagleboard] pinctrl-single 44e10800.pinmux: could not request pin 28 (44e10870.0) from group EBB_GPIO_Example o

Everyone, I have made it until the overlay loaded, but it's not doing the job properly, It's not changing the pinmux as instructed, what do I miss here ? What information do you need ? === root@beaglebone:/lib/firmware# dmesg | grep EBB [23193.563453] bone_capemgr bone_capemgr: part_number