Re: [beagleboard] Re: Cape EEROMs in uboot systems

[Robert Nelson]

On Sat, Mar 2, 2019 at 3:05 PM  wrote:


> BeagleBone: cape eeprom: i2c_probe: 0x56:
> debug: process_cape_part_number:[BB-W1-P8.11]
> debug: process_cape_part_number:[42422D57312D50382E3131]
> BeagleBone: cape eeprom: i2c_probe: 0x57: /lib/firmware/BB-W1-P8.11-00A0.dtbo 
> [0x956174f]


> uboot_overlays: [fdt_buffer=0x6] ...
> uboot_overlays: loading /lib/firmware/BB-W1-P8.11-00A0.dtbo ...


> debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait 
> uboot_detected_capes=BB-W1-P8.11, coherent_pool=1M net.ifnames=0 quiet] ...


So it detected your cape and properly loaded the overlay, what's your
problem again?

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/CAOCHtYiQNewifAUUT2JOfX4Mq_Yekqg4BxshjodFMzLw4OCSqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Pins and Port configuration in the Beagleboard xM

[Robert Nelson]

On Sat, Mar 2, 2019 at 3:05 PM  wrote:
>
>
> Hi everyone,
>
> I´m just starting a project where I´m going to do some tests with a 
> Beagleboard xM that needs to control an external board through a UART 
> channel, some PWM pins, and some GPIOs.
>
> I´ve just prepare my SD Card with the last Debian Image from this link:
>
> https://debian.beagleboard.org/images/bbxm-debian-9.5-lxqt-xm-armhf-2018-10-07-4gb.img.xz
>
>Boot the system and seems everything looks good:
>
> U-Boot SPL 2018.09-1-ge10814359b (Sep 10 2018 - 19:52:59 -0500)
> Trying to boot from MMC1
> spl_load_image_fat_os: error reading image args, err - -2
>
>
> U-Boot 2018.09-1-ge10814359b (Sep 10 2018 - 19:52:59 -0500), Build: 
> jenkins-github_Bootloader-Builder-65
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> Model: TI OMAP3 BeagleBoard
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  256 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> Loading Environment from NAND... *** Warning - readenv() failed, using 
> default environment
>
> Beagle xM Rev C
> No EEPROM on expansion board
> No EEPROM on expansion board
> OMAP die ID: 6c0a00029ff801578ca01101202e
> Net:   usb_ether
> starting USB...
> USB0:   USB EHCI 1.00
> scanning bus 0 for devices... 3 USB Device(s) found
>scanning usb for storage devices... 0 Storage Device(s) found
>scanning usb for ethernet devices... 1 Ethernet Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> 432 bytes read in 27 ms (15.6 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> loading /boot/vmlinuz-4.18.11-armv7-x11 ...
> 6550016 bytes read in 520 ms (12 MiB/s)
> loading /boot/dtbs/4.18.11-armv7-x11/omap3-beagle-xm.dtb ...
> 94492 bytes read in 786 ms (117.2 KiB/s)
> loading /boot/initrd.img-4.18.11-armv7-x11 ...
> 4745973 bytes read in 390 ms (11.6 MiB/s)
> debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
> rootwait coherent_pool=1M net.ifnames=0 quiet] ...
> debug: [bootz 0x8200 0x8808:486af5 0x8800] ...
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Loading Ramdisk to 89b79000, end 89fffaf5 ... OK
>Loading Device Tree to 89b5e000, end 89b7811b ... OK
>
> Starting kernel ...
>
> [4.520965] Error: Driver 'tfp410' is already registered, aborting...
> [5.108215] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
> [5.115936] omap2_set_init_voltage: unable to set vdd_core
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> [DEPEND] Dependency failed for robotcontrol.
> [  OK  ] Started Create list of required sta…vice nodes for the current 
> kernel.
> [  OK  ] Started File System Check Daemon to report status.
>  Starting Create Static Device Nodes in /dev...
>  Mounting Configuration File System...
>  Mounting FUSE Control File System...
>  Starting Apply Kernel Variables...
> [  OK  ] Mounted Configuration File System.
> [  OK  ] Mounted FUSE Control File System.
> [  OK  ] Started File System Check on Root Device.
> [  OK  ] Started Create Static Device Nodes in /dev.
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Started Journal Service.
>  Starting udev Kernel Device Manager...
>  Starting Remount Root and Kernel File Systems...
> [  OK  ] Started Remount Root and Kernel File Systems.
>  Starting Load/Save Random Seed...
>  Starting Flush Journal to Persistent Storage...
>  Starting udev Coldplug all Devices...
> [  OK  ] Started Load/Save Random Seed.
> [  OK  ] Started udev Kernel Device Manager.
> [  OK  ] Started Flush Journal to Persistent Storage.
> [  OK  ] Started Set the console keyboard layout.
> [  OK  ] Reached target Local File Systems (Pre).
> [  OK  ] Reached target Local File Systems.
>  Starting Create Volatile Files and Directories...
>  Starting Set console font and keymap...
>  Starting Raise network interfaces...
> [  OK  ] Started Set console font and keymap.
> [  OK  ] Started Create Volatile Files and Directories.
>  Starting Network Time Synchronization...
> [  OK  ] Started Entropy daemon using the HAVEGE algorithm.
>  Starting Update UTMP about System Boot/Shutdown...
> [  OK  ] Started Update UTMP about System Boot/Shutdown.
> [  OK  ] Started Network Time Synchronization.
> [  OK  ] Reached target System Time Synchronized.
> [  OK  ] Started Raise network interfaces.
> [  OK  ] Started udev Coldplug all Devices.
> [  OK  ] Reached target System Initialization.
> [  OK  ] Listening on bonescript.socket.
> [  OK  ] Listening on clo

[beagleboard] Re: Cape EEROMs in uboot systems

[oringutana]

Thanks Robert,

I am not using cryptsetup.

I received my second edition of Derek Molloy's Exploring Beaglebone and 
decided to start over from scratch.  New MicroSD and latest rev.  Work 
through the chapters from the start setting up as if I was a brand new 
novice user.  Even to setting the device name to 'ebb'.  

debian@ebb:~$ uname -a
Linux ebb 4.14.94-ti-r94 #1 SMP PREEMPT Thu Feb 21 23:29:48 UTC 2019 armv7l 
GNU/Linux
debian@ebb:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2018-10-07

I was disappointed when I reached page 272 "Flattened Device Tree..." Where 
his first revision book went into more detail on how to look at devices 
this revision is just a superficial overview.  Net research for the most 
part, except what I posted below, is all for the old slots approach.  Even 
Derek's blog on this is from 2016 and hasn't been touched.

Without a $SLOTS for example, how does one look to see if the cape has been 
recognized.  
You mention uboot serial log?  Which one is that and where is it?  For the 
tutorial I am writing I'd like to include what to type and why.

One of the things I'm trying to achieve for this 2GB Beaglebone (and may 
well be possible) is the ability to power it down and plug in say the Logic 
Supply CBB-Serial Cape and have it recognize that the CAN bus now uses the 
pins that were general I/O.  
Power down and plug in a different cape like the Logic Supply CBB-Proto 
which has an EEROM and perhaps a combination of Dallas One Wire(DS1822), 
SPI (small LCD display) and CAN drivers/devices and that it automatically 
can capture those pins.
All without having to recompile or rebuild anything.
And my tutorial will take a new user through the process including how to 
create the information in the EEROM on the cape.
Regards
John Dammeyer



On Saturday, March 2, 2019 at 6:23:19 AM UTC-8, oring...@gmail.com wrote:
>
> I have a prototype cape with the EEROM programmed as follows:
>
> root@beaglebone2GB:/home/john/One-Wire# cat 
> /sys/bus/i2c/devices/1-0057/eeprom | hexdump -C
>   aa 55 33 ee 41 30 4f 6e  65 57 69 72 65 20 70 6c  |.U3.A0OneWire 
> pl|
> 0010  75 73 20 43 41 4e 62 75  73 00 00 00 00 00 00 00  |us 
> CANbus...|
> 0020  00 00 00 00 00 00 30 30  41 30 41 75 74 6f 41 72  
> |..00A0AutoAr|
> 0030  74 69 73 61 6e 73 20 49  6e 63 42 42 2d 57 31 2d  |tisans 
> IncBB-W1-|
> 0040  50 38 2e 31 31 00 00 00  00 00 00 00 00 00 00 00  
> |P8.11...|
> 0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
> ||
> *
> 0130  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  
> ||
> *
> 8000
> r
>
> Needless to say with the demise of the $SLOTS concept this tutorial is no 
> longer valid so I'd like to rewrite it so it is valid.
>
> https://www.cs.sfu.ca/CourseCentral/433/bfraser/other/2016-student-howtos/DS18B20Thermometer.pdf
>
> Using this dts as a guide
>
> https://github.com/beagleboard/bb.org-overlays/blob/5741f63c1ee922333dca02d9763edae03d477c96/src/arm/BB-CAN0-00A0.dts
>
> I've modified the BB-W1-P9.12-00A0.dts to become BB-W1-P8.11-00A0.dts 
> shown below.
>
> debian@ebb:~/bb.org-overlays/src/arm$ cat BB-W1-P8.11*
> /*
>  * Copyright (C) 2015 Robert Nelson 
>  *
>  * Virtual cape for onewire on connector pin P8.11
>  * derived from BB-W1-P9.12-00A0.dts
>  *  by John Dammeyer MAR2019
>  *
>  * This program is free software; you can redistribute it and/or modify
>  * it under the terms of the GNU General Public License version 2 as
>  * published by the Free Software Foundation.
>  */
>
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
> #include 
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
>
> /* identification */
> part-number = "BB-W1-P8.11";
> version = "00A0";
>
> /* state the resources this cape uses */
> exclusive-use =
> /* the pin header uses */
> "P8.11";
>
> /*
>  * Free up the pins used by the cape from the pinmux helpers.
>  */
> fragment@0 {
> target = <&ocp>;
> __overlay__ {
> P8_11_pinmux { status = "disabled"; };
> };
> };
>
> fragment@1 {
> target = <&am33xx_pinmux>;
> __overlay__ {
>
> dallas_w1_pins: pinmux_dallas_w1_pins {
> pinctrl-single,pins = <
> BONE_P8_11 0x37
> >;
> };
> };
> };
>
> fragment@2 {
> target-path="/";
> __overlay__ {
>
> onewire {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&dallas_w1_pins>;
>
> compati

[beagleboard] Re: Cape EEROMs in uboot systems

[oringutana]

[image: DS1822-Python.jpg]


So after the ./install.sh and installation of the cape and then power up I 
do now have access to my DS1822 via a Python app.  But another vanishing 
act, possibly due to the change from the SLOTs approach, is the hex dump 
below isn't possible anymore.

debian@ebb:~$ cat /sys/bus/i2c/devices/1-0057/eeprom | hexdump -C
cat: /sys/bus/i2c/devices/1-0057/eeprom: No such file or directory

So where did the i2c eeprom go?  Does the /boot/uEnv.txt need to have i2c 
explicitly set to access the cape eeproms?

debian@ebb:/sys/devices$ ls
armv7_cortex_a8  platform  software  tracepoint  w1_bus_master1
breakpoint   soc0  systemvirtual




On Saturday, March 2, 2019 at 6:23:19 AM UTC-8, oring...@gmail.com wrote:
>
> I have a prototype cape with the EEROM programmed as follows:
>
> root@beaglebone2GB:/home/john/One-Wire# cat 
> /sys/bus/i2c/devices/1-0057/eeprom | hexdump -C
>   aa 55 33 ee 41 30 4f 6e  65 57 69 72 65 20 70 6c  |.U3.A0OneWire 
> pl|
> 0010  75 73 20 43 41 4e 62 75  73 00 00 00 00 00 00 00  |us 
> CANbus...|
> 0020  00 00 00 00 00 00 30 30  41 30 41 75 74 6f 41 72  
> |..00A0AutoAr|
> 0030  74 69 73 61 6e 73 20 49  6e 63 42 42 2d 57 31 2d  |tisans 
> IncBB-W1-|
> 0040  50 38 2e 31 31 00 00 00  00 00 00 00 00 00 00 00  
> |P8.11...|
> 0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
> ||
> *
> 0130  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  
> ||
> *
> 8000
> r
>
>
>

-- 
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/898b3c4f-66b4-4936-9e4f-da50cb6888cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Pins and Port configuration in the Beagleboard xM

[montaltipablo]

Hi everyone,

I´m just starting a project where I´m going to do some tests with a 
Beagleboard xM that needs to control an external board through a UART 
channel, some PWM pins, and some GPIOs.

I´ve just prepare my SD Card with the last Debian Image from this link:

https://debian.beagleboard.org/images/bbxm-debian-9.5-lxqt-xm-armhf-2018-10-07-4gb.img.xz

   Boot the system and seems everything looks good:

U-Boot SPL 2018.09-1-ge10814359b (Sep 10 2018 - 19:52:59 -0500)
Trying to boot from MMC1
spl_load_image_fat_os: error reading image args, err - -2


U-Boot 2018.09-1-ge10814359b (Sep 10 2018 - 19:52:59 -0500), Build: 
jenkins-github_Bootloader-Builder-65

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
Model: TI OMAP3 BeagleBoard
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
Loading Environment from NAND... *** Warning - readenv() failed, using 
default environment

Beagle xM Rev C
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 6c0a00029ff801578ca01101202e
Net:   usb_ether
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
   scanning usb for ethernet devices... 1 Ethernet Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
432 bytes read in 27 ms (15.6 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-4.18.11-armv7-x11 ...
6550016 bytes read in 520 ms (12 MiB/s)
loading /boot/dtbs/4.18.11-armv7-x11/omap3-beagle-xm.dtb ...
94492 bytes read in 786 ms (117.2 KiB/s)
loading /boot/initrd.img-4.18.11-armv7-x11 ...
4745973 bytes read in 390 ms (11.6 MiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0 quiet] ...
debug: [bootz 0x8200 0x8808:486af5 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 89b79000, end 89fffaf5 ... OK
   Loading Device Tree to 89b5e000, end 89b7811b ... OK

Starting kernel ...

[4.520965] Error: Driver 'tfp410' is already registered, aborting...
[5.108215] omap2_set_init_voltage: unable to find boot up OPP for 
vdd_core
[5.115936] omap2_set_init_voltage: unable to set vdd_core
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[DEPEND] Dependency failed for robotcontrol.
[  OK  ] Started Create list of required sta…vice nodes for the current 
kernel.
[  OK  ] Started File System Check Daemon to report status.
 Starting Create Static Device Nodes in /dev...
 Mounting Configuration File System...
 Mounting FUSE Control File System...
 Starting Apply Kernel Variables...
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started File System Check on Root Device.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Journal Service.
 Starting udev Kernel Device Manager...
 Starting Remount Root and Kernel File Systems...
[  OK  ] Started Remount Root and Kernel File Systems.
 Starting Load/Save Random Seed...
 Starting Flush Journal to Persistent Storage...
 Starting udev Coldplug all Devices...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
 Starting Create Volatile Files and Directories...
 Starting Set console font and keymap...
 Starting Raise network interfaces...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Create Volatile Files and Directories.
 Starting Network Time Synchronization...
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
 Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Raise network interfaces.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on bonescript.socket.
[  OK  ] Listening on cloud9.socket.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on node-red.socket.
[  OK  ] Listenin

[beagleboard] Re: Cape EEROMs in uboot systems

[oringutana]

A follow up to the request by Robert for the uboot power up information 
from a terminal connection.  It finds the cape.  Should I be concerned 
about the 

** Unable to read "/boot/uboot.env" from mmc0:1 **

Or is that just because I'm using the SD card to boot?

Also I'm playing with the little TFT display:
https://learn.adafruit.com/user-space-spi-tft-python-library-ili9341-2-8/wiring

My SLOTs BBB OS version has in the uEnv.txt file
cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0
while the tutorial above has
optargs=capemgr.enable_partno=BB-SPIDEV0
and then says to check /dev/ for the spi ports.
"*Reboot your device and you should see the files /dev/spidev1.0 and 
/dev/spidev1.1 now exist."*


This slotless version already has them.
debian@ebb:~$ ls /dev/spi*
/dev/spidev1.0  /dev/spidev1.1  /dev/spidev2.0  /dev/spidev2.1

Is anything else needed then?  The Adafruit Tutorial is then also quite 
dated and will need to have an addendum or be rewritten. 

Thanks
John Dammeyer

Here's the boot up log:

[  OK  ] Reached target Shutdown.
[ 4071.826261] watchdog: watchdog0: watchdog did not stop!
[ 4072.180409] reboot: Restarting system

U-Boot SPL 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **


U-Boot 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: 
jenkins-github_Bootloader-Builder-65

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **
Board: BeagleBone Black
 not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
debug: process_cape_part_number:[BB-W1-P8.11]
debug: process_cape_part_number:[42422D57312D50382E3131]
BeagleBone: cape eeprom: i2c_probe: 0x57: 
/lib/firmware/BB-W1-P8.11-00A0.dtbo [0x956174f]
Net:   eth0: MII MODE
cpsw, usb_ether
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
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
2148 bytes read in 15 ms (139.6 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-4.14.94-ti-r94 ...
9724416 bytes read in 628 ms (14.8 MiB/s)
debug: [enable_uboot_overlays=1] ...
debug: [enable_uboot_cape_universal=1] ...
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...
loading /boot/dtbs/4.14.94-ti-r94/am335x-boneblack-uboot-univ.dtb ...
162727 bytes read in 38 ms (4.1 MiB/s)
uboot_overlays: [fdt_buffer=0x6] ...
uboot_overlays: loading /lib/firmware/BB-W1-P8.11-00A0.dtbo ...
1118 bytes read in 318 ms (2.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1440 bytes read in 371 ms (2.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4896 bytes read in 43 ms (110.4 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
711 bytes read in 288 ms (2 KiB/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo ...
3513 bytes read in 53 ms (64.5 KiB/s)
uboot_overlays: [uboot_detected_capes=BB-W1-P8.11,] ...
loading /boot/initrd.img-4.14.94-ti-r94 ...
5248133 bytes read in 347 ms (14.4 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait 
uboot_detected_capes=BB-W1-P8.11, coherent_pool=1M net.ifnames=0 quiet] ...
debug: [bootz 0x8200 0x8808:501485 8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8fafe000, end 8485 ... OK
   reserving fdt memory region: addr=8800 size=89000
   Loading Device Tree to 8fa72000, end 8fafdfff ... OK

Starting kernel ...

[0.002135] timer_probe: no matching timers found
[1.012982] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[1.310968] 

Re: [beagleboard] changing the port in BBB

[Robert Nelson]

On Sat, Mar 2, 2019 at 8:23 AM  wrote:
>
> Hello
>
> I have an internet connection and I need to share that service among 3 BBBs 
> that are operating on the same site.
>
> At any time, I will need to review (or change) remotely the configuration of 
> each one. To do this, the ISP will assign a public IP to your router. I will 
> connect the 3 BBB to a switch to share the internet service and configure the 
> router with Network address translation (NAT), that is, to each BBB I will 
> assign a different IP address and port. That way when I'm anywhere from the 
> browser (Google chrome or firefox) of my lap top, I will write the public IP 
> and the port assigned to each BBB to access each device.
> I know how to assign a static IP to each BBB, but not how to change the 
> default port (3000). Is it possible to program different ports to each BBB?

You don't need to change anything on the BBB, just do it in your
firewall.. (Port Forwarding: incoming port W redirected in network to
device X at port Y)

Or you can do it at first server, using nginix port foward based on path..

Tons of different ways..

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/CAOCHtYjzZHXpxAAX1NEfnR48AUXjnud_g-FcJQ5Dv0Uqu69SQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cape EEROMs in uboot systems

[Robert Nelson]

On Sat, Mar 2, 2019 at 8:23 AM  wrote:
>
> I have a prototype cape with the EEROM programmed as follows:
>
> root@beaglebone2GB:/home/john/One-Wire# cat 
> /sys/bus/i2c/devices/1-0057/eeprom | hexdump -C
>   aa 55 33 ee 41 30 4f 6e  65 57 69 72 65 20 70 6c  |.U3.A0OneWire pl|
> 0010  75 73 20 43 41 4e 62 75  73 00 00 00 00 00 00 00  |us CANbus...|
> 0020  00 00 00 00 00 00 30 30  41 30 41 75 74 6f 41 72  |..00A0AutoAr|
> 0030  74 69 73 61 6e 73 20 49  6e 63 42 42 2d 57 31 2d  |tisans IncBB-W1-|
> 0040  50 38 2e 31 31 00 00 00  00 00 00 00 00 00 00 00  |P8.11...|
> 0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
> *
> 0130  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  ||
> *
> 8000
> r
>
> Needless to say with the demise of the $SLOTS concept this tutorial is no 
> longer valid so I'd like to rewrite it so it is valid.
> https://www.cs.sfu.ca/CourseCentral/433/bfraser/other/2016-student-howtos/DS18B20Thermometer.pdf
>
> Using this dts as a guide
> https://github.com/beagleboard/bb.org-overlays/blob/5741f63c1ee922333dca02d9763edae03d477c96/src/arm/BB-CAN0-00A0.dts
>
> I've modified the BB-W1-P9.12-00A0.dts to become BB-W1-P8.11-00A0.dts shown 
> below.
>
> debian@ebb:~/bb.org-overlays/src/arm$ cat BB-W1-P8.11*
> /*
>  * Copyright (C) 2015 Robert Nelson 
>  *
>  * Virtual cape for onewire on connector pin P8.11
>  * derived from BB-W1-P9.12-00A0.dts
>  *  by John Dammeyer MAR2019
>  *
>  * This program is free software; you can redistribute it and/or modify
>  * it under the terms of the GNU General Public License version 2 as
>  * published by the Free Software Foundation.
>  */
>
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
> #include 
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
>
> /* identification */
> part-number = "BB-W1-P8.11";
> version = "00A0";
>
> /* state the resources this cape uses */
> exclusive-use =
> /* the pin header uses */
> "P8.11";
>
> /*
>  * Free up the pins used by the cape from the pinmux helpers.
>  */
> fragment@0 {
> target = <&ocp>;
> __overlay__ {
> P8_11_pinmux { status = "disabled"; };
> };
> };
>
> fragment@1 {
> target = <&am33xx_pinmux>;
> __overlay__ {
>
> dallas_w1_pins: pinmux_dallas_w1_pins {
> pinctrl-single,pins = <
> BONE_P8_11 0x37
> >;
> };
> };
> };
>
> fragment@2 {
> target-path="/";
> __overlay__ {
>
> onewire {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&dallas_w1_pins>;
>
> compatible = "w1-gpio";
> gpios = <&gpio1 13 GPIO_ACTIVE_HIGH>;
> };
> };
> };
> };
>
> Next, following the document I ran ./install.sh from the 
> debian@ebb:~/bb.org-overlays$ folder which ran DTS on each of the files and 
> then copied them to /lib/firmware and then created a new initramfs.  With a 
> few warnings.
>
> update-initramfs: Generating /boot/initrd.img-4.14.94-ti-94
> WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
> deprecated and will stop working in the future. Use 
> /etc/cryptsetup-initramfs/conf-hook instead.
> cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk0p1
> cryptsetup: WARNING: could not determine root device from /etc/fstab
> './tools/beaglebone-universal-io/config-pin' -> 
> '/usr/local/bin/config-pin'cape overlays have been built and added to 
> /lib/firmware & /boot/initrd.img-4.14.94-ti-r94, please reboot
>
> Not sure about those errors.

Well it's a warning for cryptsetup, are you using cryptsetup??

>  At this point I'm guessing the echo > $SLOTS isn't needed since the new dtbo 
> is now part of the initramfs image has it as part of the boot process.

Actually this is for the old "slots" too..

> Plugging in the cape and starting up the beagle should theoretically then 
> make a One Wire device available on pin P8.11?

Plug in a debug cable into J1 and dump the U-Boot serial log and we
can find out..

> If the DTS file included the definitions from the example  BB-CAN0-00A0.dts 
> and the prototype board contained a CAN bus bus driver connected to P9.19, 
> P9.20 would, on power up those pins then be used by the One Wire code and the 
> CAN bus code?

Yes,

> Is the difference then that a rebuilding of the initrd image is required for 
> creating custom capes?  Is there a short

[beagleboard] how to change the port in a BBB

[casalnico2002]

Hello

I have an internet connection and I need to share that service among 3 BBBs 
that are operating on the same site.

At any time, I will need to review (or change) remotely the configuration 
of each one. To do this, the ISP will assign a public IP to your router. I 
will connect the 3 BBB to a switch to share the internet service and 
configure the router with Network address translation (NAT), that is, to 
each BBB I will assign a different IP address and port. That way when I'm 
anywhere, from the browser (Google chrome or firefox) of my lap top, I'll 
write the public IP and the port assigned to each BBB to be able to access 
each device.
I know how to assign a static IP to each BBB, but not how to change the 
default port (3000). Is it possible to program different ports to each BBB?


Thanks

-- 
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/524531d8-f144-43f0-97d0-e16e0b10f320%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cape EEROMs in uboot systems

[oringutana]

I have a prototype cape with the EEROM programmed as follows:

root@beaglebone2GB:/home/john/One-Wire# cat 
/sys/bus/i2c/devices/1-0057/eeprom | hexdump -C
  aa 55 33 ee 41 30 4f 6e  65 57 69 72 65 20 70 6c  |.U3.A0OneWire 
pl|
0010  75 73 20 43 41 4e 62 75  73 00 00 00 00 00 00 00  |us 
CANbus...|
0020  00 00 00 00 00 00 30 30  41 30 41 75 74 6f 41 72  
|..00A0AutoAr|
0030  74 69 73 61 6e 73 20 49  6e 63 42 42 2d 57 31 2d  |tisans 
IncBB-W1-|
0040  50 38 2e 31 31 00 00 00  00 00 00 00 00 00 00 00  
|P8.11...|
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
||
*
0130  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  
||
*
8000
r

Needless to say with the demise of the $SLOTS concept this tutorial is no 
longer valid so I'd like to rewrite it so it is valid.
https://www.cs.sfu.ca/CourseCentral/433/bfraser/other/2016-student-howtos/DS18B20Thermometer.pdf

Using this dts as a guide
https://github.com/beagleboard/bb.org-overlays/blob/5741f63c1ee922333dca02d9763edae03d477c96/src/arm/BB-CAN0-00A0.dts

I've modified the BB-W1-P9.12-00A0.dts to become BB-W1-P8.11-00A0.dts shown 
below.

debian@ebb:~/bb.org-overlays/src/arm$ cat BB-W1-P8.11*
/*
 * Copyright (C) 2015 Robert Nelson 
 *
 * Virtual cape for onewire on connector pin P8.11
 * derived from BB-W1-P9.12-00A0.dts
 *  by John Dammeyer MAR2019
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 2 as
 * published by the Free Software Foundation.
 */

/dts-v1/;
/plugin/;

#include 
#include 
#include 

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", 
"ti,beaglebone-green";

/* identification */
part-number = "BB-W1-P8.11";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P8.11";

/*
 * Free up the pins used by the cape from the pinmux helpers.
 */
fragment@0 {
target = <&ocp>;
__overlay__ {
P8_11_pinmux { status = "disabled"; };
};
};

fragment@1 {
target = <&am33xx_pinmux>;
__overlay__ {

dallas_w1_pins: pinmux_dallas_w1_pins {
pinctrl-single,pins = <
BONE_P8_11 0x37
>;
};
};
};

fragment@2 {
target-path="/";
__overlay__ {

onewire {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&dallas_w1_pins>;

compatible = "w1-gpio";
gpios = <&gpio1 13 GPIO_ACTIVE_HIGH>;
};
};
};
};

Next, following the document I ran ./install.sh from the 
debian@ebb:~/bb.org-overlays$ folder which ran DTS on each of the files and 
then copied them to /lib/firmware and then created a new initramfs.  With a 
few warnings.

update-initramfs: Generating /boot/initrd.img-4.14.94-ti-94
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.
cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk0p1
cryptsetup: WARNING: could not determine root device from /etc/fstab
'./tools/beaglebone-universal-io/config-pin' -> 
'/usr/local/bin/config-pin'cape overlays have been built and added to 
/lib/firmware & /boot/initrd.img-4.14.94-ti-r94, please reboot

Not sure about those errors.  At this point I'm guessing the echo > $SLOTS 
isn't needed since the new dtbo is now part of the initramfs image has it 
as part of the boot process.

Plugging in the cape and starting up the beagle should theoretically then 
make a One Wire device available on pin P8.11?

If the DTS file included the definitions from the example  BB-CAN0-00A0.dts 

 
and the prototype board contained a CAN bus bus driver connected to P9.19, 
P9.20 would, on power up those pins then be used by the One Wire code and 
the CAN bus code?

Is the difference then that a rebuilding of the initrd image is required 
for creating custom capes?  Is there a short cut?

Am I right that this is way more difficult than the echo to $SLOTS since it 
involves a build and reboot after each edit while developing the custom 
cape dts file?  
Again, is there an easier way rather than compiling every single dts file 
with the ./install.sh script?

Thanks
John Dammeyer

-- 
For more options, visit http://beagleboard.org/discuss

[beagleboard] changing the port in BBB

[casalnico2002]

Hello 

I have an internet connection and I need to share that service among 3 BBBs 
that are operating on the same site.

At any time, I will need to review (or change) remotely the configuration 
of each one. To do this, the ISP will assign a public IP to your router. I 
will connect the 3 BBB to a switch to share the internet service and 
configure the router with Network address translation (NAT), that is, to 
each BBB I will assign a different IP address and port. That way when I'm 
anywhere from the browser (Google chrome or firefox) of my lap top, I will 
write the public IP and the port assigned to each BBB to access each device.
I know how to assign a static IP to each BBB, but not how to change the 
default port (3000). Is it possible to program different ports to each BBB?

Thanks

-- 
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/14064352-0b4c-48eb-b946-8cf11292e57d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone cape universal anf u-boot falcon mode

[p1906]

Hi all,

I'm trying to boot bealgebone with u-boot in falcon mode but I don't know 
how to enable cape universal in order to use the beaglebone uarts.
I'm useìing the Robert Nelson kernel 4.14.87-bone-rt-r17 and I tried to 
pass "cape_universal=1" as kernel args but it doesn't work.

can someone give me a suggestion on how to do it?

Thanks
P1906

-- 
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/b2520d3c-378b-4d82-8c10-0b266341d5bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: full disk space

[Tarmo Kuuse]

Hi Erik,

On Thursday, 28 February 2019 18:00:46 UTC+2, erikb...@gmail.com wrote:
>
> thanks for the reply, im a newby at linux. ill try to refer to it as root 
> partition from now on.
>
> I flashed the image found from the beaglebones website.
> https://beagleboard.org/latest-images
>
> this one> Debian 9.5 2018-10-07 4GB SD IoT  
> 
>
> Do you know any alternatives? more cleaner images?
>

This is the "iot" variant which comes with an assortment of development 
tools pre-installed. Some of those seem rather specific (don't know the 
details, sorry) so there's a good chance you wouldn't need them all. You 
could uninstall those one by one, or you could begin fresh with a "console" 
image which has almost nothing added the base OS and install whatever 
packages are relevant. The corresponding image from the 2018-10-07 release 
would be this one:
https://rcn-ee.net/rootfs/bb.org/testing/2018-10-07/stretch-console/bone-debian-9.5-console-armhf-2018-10-07-1gb.img.xz

You could also poke around here and pick out something a little fresher 
(some are more experimental than others, the "keepers" file is a good 
source of hints as to which release to choose)
https://rcn-ee.net/rootfs/bb.org/testing/

--
Kind regards,
Tarmo

-- 
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/a1b2c636-c75e-4280-a328-34f798296fc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.