Re: [beagleboard] Ethernet not working with debian stretch 4.14.67-ti-r73

2018-09-06 Thread smith . winston . 101 
On Thursday, September 6, 2018 at 5:48:39 PM UTC-4, smith.wi...@gmail.com 
wrote:

>
> Just for sanity I will rebuild the rcn-ee_console_debian_stretch_armhf but 
> with a flasher and retry that.
>

I rebuilt from scratch and generated an eMMC flasher, installed and I get 
the same results as with USB mass-storage flashing.


I noticed that the fast-blink of the green LED starts almost at power up, 
which is odd and makes me think it's a u-boot or dtb issue?  Here's the 
compete output from power up to login prompt:

U-Boot SPL 2018.03-2-gac9cce7c6a (Apr 05 2018 - 13:07:46 -0500)
Trying to boot from MMC2
Loading Environment from EXT4... Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)


U-Boot 2018.03-2-gac9cce7c6a (Apr 05 2018 - 13:07:46 -0500), Build: 
jenkins-github_Bootloader-Builder-47

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: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)
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:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[00C0] ...
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
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
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1: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
mmc1(part 0) 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
2102 bytes read in 32 ms (63.5 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.67-ti-r73 ...
10379776 bytes read in 679 ms (14.6 MiB/s)
loading /boot/dtbs/4.14.67-ti-r73/am335x-boneblack.dtb ...
60317 bytes read in 61 ms (964.8 KiB/s)
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...
loading /boot/initrd.img-4.14.67-ti-r73 ...
4530206 bytes read in 315 ms (13.7 MiB/s)
debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=btrfs 
rootwait coherent_pool=1M net.ifnames=0 quiet] ...
debug: [bootz 0x8200 0x8808:45201e 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8fbad000, end 801e ... OK
   Loading Device Tree to 8fb9b000, end 8fbacb9c ... OK

Starting kernel ...

[0.000760] timer_probe: no matching timers found
[0.542293] dmi: Firmware registration failed.
[1.036826] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[1.253210] dmi-sysfs: dmi entry is absent.
[1.285511] omap_voltage_late_init: Voltage driver support not added
[1.595720] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: no source 
widget found for Playback
[1.604591] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: Failed to 
add route Playback -> direct -> TX

Debian GNU/Linux 9 arm ttyS0

rcn-ee.net console Debian Image 2018-09-06

Support/FAQ: http://elinux.org/BeagleBoardDebian

default username:password is [debian:temppwd]

arm login: 
 

Next up, I'll retry without btrfs (i.e. omitting the --rootfs btrfs on the 
sdcard_setup step).

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/d1f33255-1170-4449-b219-863609c60c00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] update & upgrade （bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img）

2018-09-06 Thread GU LANG 
debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0  179:00 14.9G  0 disk
└─mmcblk0p1  179:10 14.9G  0 part /
mmcblk1  179:80  1.8G  0 disk
├─mmcblk1p1  179:90   96M  0 part
└─mmcblk1p2  179:10   0  1.7G  0 part
mmcblk1boot0 179:16   01M  1 disk
mmcblk1boot1 179:24   01M  1 disk
mmcblk1rpmb  179:32   0  128K  0 disk
debian@beaglebone:~$ sudo df -h
Filesystem  Size  Used Avail Use% Mounted on
udev216M 0  216M   0% /dev
tmpfs49M  4.7M   44M  10% /run
/dev/mmcblk0p1   15G  2.8G   12G  21% /
tmpfs   242M 0  242M   0% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   242M 0  242M   0% /sys/fs/cgroup
tmpfs49M 0   49M   0% /run/user/1000


在 2018年9月7日星期五 UTC+8上午11:28:12，RobertCNelson写道：
>
> On Thu, Sep 6, 2018 at 10:22 PM GU LANG > 
> wrote: 
> > 
> > 2 G eMMC, but I use SDcard start BBB,not use emmc 
>
> Okay, i just assumed eMMC, so what does "df" show on your microSD and 
> what size was it advertised as? 
>
> 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/15a07f0f-1efb-4ec6-9b69-0f126b037987%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] update & upgrade （bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img）

2018-09-06 Thread Robert Nelson 
On Thu, Sep 6, 2018 at 10:22 PM GU LANG  wrote:
>
> 2 G eMMC, but I use SDcard start BBB,not use emmc

Okay, i just assumed eMMC, so what does "df" show on your microSD and
what size was it advertised as?

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

Re: [beagleboard] update & upgrade （bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img）

2018-09-06 Thread GU LANG 
2 G eMMC, but I use SDcard start BBB,not use emmc 

在 2018年9月7日星期五 UTC+8上午11:17:25，RobertCNelson写道：
>
> 在星期四，2018年9月6日在下午10点13郎顾< liul ... @ gmail.com  >写道： 
> > 
> >我烧的IMG到SDcard.and使用“须藤的/ opt /脚本/工具/ grow_ partition.sh “ 
> > 
> > 
> >当我升级，我得到 
> > 
>
> > RM：无法删除'的/ var /缓存/ apt / archives目录/ Apache2的-bin_2.4.25-3 + deb9u5_ 
> > armhf.deb'：只读文件SY茎 
>
> > RM：不能删除'/ var / cache / apt / archives / apache2-data_2.4.25-3 + 
> deb9u5_ all.deb'：只读文件系统 
> > rm：无法删除'/ var / cache / apt / archives / apache2-utils_2.4.25-3 + 
> deb9u5_armhf.deb'：只读文件系统 
> > rm：无法删除'/ var / cache / apt / archives / apache2_2.4.25-3 + 
> deb9u5_armhf。deb'：只读文件系统 
> > rm：无法删除'/ var / cache / apt / archives / ardupilot-copter-3.6-bbbmini_ 
> > 3.6.0-git20180807-0rcnee0~st 
> retch + 20180810_armhf.deb'：只读文件系统 
>
> 看起来你的空间不足.. 
>
> 这是4gb eMMC还是什么？ 
>
> 此致， 
>
> - 
> 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/cf4f3973-fec6-4a5b-8c98-58613d7a4149%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] update & upgrade （bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img）

2018-09-06 Thread Robert Nelson 
On Thu, Sep 6, 2018 at 10:13 PM GU LANG  wrote:
>
> I burn the img into SDcard.and use "sudo /opt/scripts/tools/grow_partition.sh"
>
>
> When I upgrade, I get
>

> rm: cannot remove 
> '/var/cache/apt/archives/apache2-bin_2.4.25-3+deb9u5_armhf.deb': Read-only 
> file sy   
>   stem
> rm: cannot remove 
> '/var/cache/apt/archives/apache2-data_2.4.25-3+deb9u5_all.deb': Read-only 
> file sys  
>tem
> rm: cannot remove 
> '/var/cache/apt/archives/apache2-utils_2.4.25-3+deb9u5_armhf.deb': Read-only 
> file  
> system
> rm: cannot remove 
> '/var/cache/apt/archives/apache2_2.4.25-3+deb9u5_armhf.deb': Read-only file 
> system
> rm: cannot remove 
> '/var/cache/apt/archives/ardupilot-copter-3.6-bbbmini_3.6.0-git20180807-0rcnee0~st
>  
> retch+20180810_armhf.deb': Read-only file system

Looks like you ran out of space..

Was this the 4gb eMMC or what?

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/CAOCHtYjdzhALSxrP7fuXyFAuvPH-AT%3DD2-8eiWhREGzOom%2BnHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] update & upgrade （bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img）

2018-09-06 Thread GU LANG 
I burn the img into SDcard.and use "sudo 
/opt/scripts/tools/grow_partition.sh"


When I upgrade, I get 



debian@beaglebone:~$ sudo apt-get update
Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:3 http://deb.debian.org/debian-security stretch/updates InRelease [94.3 
kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Get:6 http://deb.debian.org/debian stretch-updates/main armhf Packages 
[5,112 B]
Get:7 http://repos.rcn-ee.com/debian stretch InRelease [3,058 B]
Get:8 http://deb.debian.org/debian-security stretch/updates/contrib armhf 
Packag  
   es [1,764 B]
Get:9 http://deb.debian.org/debian-security stretch/updates/main armhf 
Packages
  [378 kB]
Get:10 http://deb.debian.org/debian-security stretch/updates/non-free armhf 
Pack
 ages [1,268 B]
Get:11 http://deb.debian.org/debian stretch/non-free armhf Packages [60.0 
kB]
Get:12 http://deb.debian.org/debian stretch/contrib armhf Packages [42.1 kB]
Get:13 http://deb.debian.org/debian stretch/main armhf Packages [6,927 kB]
Get:14 http://repos.rcn-ee.com/debian stretch/main armhf Packages [661 kB]
Fetched 8,385 kB in 1min 18s (106 kB/s)
Reading package lists... Done
debian@beaglebone:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libgl1-mesa-dri libopencl1 libwayland-egl1-mesa mesa-va-drivers 
mesa-vdpau-drivers ti-opencl
The following packages will be upgraded:
  apache2 apache2-bin apache2-data apache2-utils 
ardupilot-copter-3.6-bbbmini
  ardupilot-copter-3.6-blue ardupilot-copter-3.6-pocket 
ardupilot-rover-3.4-bbbmini base-files
  bb-beaglebone-io-installer bb-cape-overlays bb-customizations 
bb-johnny-five-installer
  bb-node-red-installer bonescript ca-certificates chromium curl dpkg 
dpkg-dev file
  firmware-am57xx-opencl-monitor fuse ipumm-dra7xx-installer libavcodec57 
libavformat57
  libavutil55 libcpupower1 libcups2 libcurl3 libcurl3-gnutls libdpkg-perl 
libdrm-amdgpu1
  libdrm-common libdrm-dev libdrm-etnaviv1 libdrm-exynos1 libdrm-freedreno1 
libdrm-nouveau2
  libdrm-omap1 libdrm-radeon1 libdrm-tegra0 libdrm2 libegl-mesa0 
libegl1-mesa libetnaviv libfuse2
  libgbm1 libgcrypt20 libgl1-mesa-glx libglapi-mesa libgles2-mesa 
libglx-mesa0 liblcms2-2
  libldap-2.4-2 libldap-common libmagic-mgc libmagic1 libpam-systemd 
libsmbclient
  libsoup-gnome2.4-1 libsoup2.4-1 libswresample2 libsystemd0 libticmem1 
libudev-dev libudev1
  libwayland-client0 libwayland-cursor0 libwayland-server0 libwbclient0 
libxapian30 linux-cpupower
  linux-libc-dev mesa-common-dev nodejs openssh-client openssh-server 
openssh-sftp-server patch
  pru-software-support-package samba-libs shared-mime-info systemd 
systemd-sysv ti-ipc-dra7xx udev
87 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 130 MB of archives.
After this operation, 20.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:2 http://repos.rcn-ee.com/debian stretch/main armhf nodejs armhf 
6.14.4-0rcnee0~stretch+20180815
  [7,916 kB]
Get:3 http://deb.debian.org/debian stretch/main armhf dpkg armhf 1.18.25 
[2,078 kB]
Get:1 http://101.110.118.33/deb.debian.org/debian stretch/main armhf 
base-files armhf 9.9+deb9u5 [67
 .3 kB]
Get:4 http://deb.debian.org/debian stretch/main armhf systemd-sysv armhf 
232-25+deb9u4 [81.3 kB]
Get:5 http://deb.debian.org/debian stretch/main armhf libpam-systemd armhf 
232-25+deb9u4 [176 kB]
Get:6 http://deb.debian.org/debian stretch/main armhf libudev-dev armhf 
232-25+deb9u4 [91.3 kB]
Get:7 http://deb.debian.org/debian stretch/main armhf libsystemd0 armhf 
232-25+deb9u4 [259 kB]
Get:8 http://deb.debian.org/debian stretch/main armhf systemd armhf 
232-25+deb9u4 [2,272 kB]
Get:9 http://deb.debian.org/debian stretch/main armhf udev armhf 
232-25+deb9u4 [1,077 kB]
Get:10 http://deb.debian.org/debian stretch/main armhf libudev1 armhf 
232-25+deb9u4 [120 kB]
Get:11 http://deb.debian.org/debian stretch/main armhf libgcrypt20 armhf 
1.7.6-2+deb9u3 [468 kB]
Get:12 http://deb.debian.org/debian stretch/main armhf libldap-common all 
2.4.44+dfsg-5+deb9u2 [85.5  
kB]
Get:13 http://deb.debian.org/debian stretch/main armhf libldap-2.4-2 armhf 
2.4.44+dfsg-5+deb9u2 [197  
kB]

Re: [beagleboard] Ethernet not working with debian stretch 4.14.67-ti-r73

2018-09-06 Thread smith . winston . 101 


On Thursday, September 6, 2018 at 5:18:07 PM UTC-4, RobertCNelson wrote:
>
>
> Just to confirm details, please restate the steps you did from the output 
> of the image builder script to sdcard.
>

Sure!

This is based on a pull of github.com/beagleboard/image-builder over the 
long weekend (which I think hasn't changed since):

time ./RootStock-NG.sh -c rcn-ee_console_debian_stretch_armhf
cd debian-9.5-console-armhf-2018-09-06
sudo ./setup_sdcard.sh --img-4gb 
../BBB-eMMC-debian-9.5-console-armhf-2018-09-06 --dtb beaglebone 
--enable-systemd --bbb-old-bootloader-in-emmc --rootfs btrfs

Now the flashing part is a bit odd but I don't think it is part of the 
problem (since I saw the same issue when installing via a flasher).  I'm 
using a variant of BBBlfs and the SPL/uboot binaries from 
https://github.com/ravikp7/node-beagle-boot to boot the BBB into USB Mass 
Storage mode and then mount the eMMC as /dev/sda, Finally, I dd the image 
to /dev/sda, mount /dev/sda1 and fix /etc/fstab (otherwise it won't boot!).

Just for sanity I will rebuild the rcn-ee_console_debian_stretch_armhf but 
with a flasher and retry that.

Thanks!

-W

-- 
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/00c6c517-18c4-4353-9dae-999eae7a5258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet not working with debian stretch 4.14.67-ti-r73

2018-09-06 Thread Robert Nelson 
On Thu, Sep 6, 2018, 3:51 PM  wrote:

> I built a debian stretch image (with 4.14.67-ti-r73) kernel using the
> current image-builder -- I used the rcn-ee_console_debian_stretch_armhf
> configuration.
>
> Once I've flashed it, when it comes up, I notice the green LED on the
> ethernet is blinking quickly.  Once it comes up, it ends up with a
> self-assigned IP, but eventually picks up a DHCP address.  Seems like it's
> dropping a lot of packets ... cannot SSH into it and ping shows
> intermittent results.
>

Just to confirm details, please restate the steps you did from the output
of the image builder script to sdcard.

Regards,

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

[beagleboard] Ethernet not working with debian stretch 4.14.67-ti-r73

2018-09-06 Thread smith . winston . 101 
I built a debian stretch image (with 4.14.67-ti-r73) kernel using the 
current image-builder -- I used the rcn-ee_console_debian_stretch_armhf 
configuration.

Once I've flashed it, when it comes up, I notice the green LED on the 
ethernet is blinking quickly.  Once it comes up, it ends up with a 
self-assigned IP, but eventually picks up a DHCP address.  Seems like it's 
dropping a lot of packets ... cannot SSH into it and ping shows 
intermittent results.

Nothing obviously wrong in dmesg, here's the tail end:

...
[   13.534669] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   15.044026] net eth0: initializing cpsw version 1.12 (0)
[   15.116989] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver 
[SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[   15.146311] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.152982] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full - 
flow control off
[   17.153073] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   17.361787] 8021q: 802.1Q VLAN Support v1.8
[   17.361874] 8021q: adding VLAN 0 to HW filter on device eth0
[   23.030864] random: crng init done
[   23.030890] random: 7 urandom warning(s) missed due to ratelimiting
[   32.941240] systemd[1]: apt-daily.timer: Adding 3h 18min 33.058208s 
random time.
[   33.917355] systemd[1]: apt-daily.timer: Adding 5h 56min 18.925035s 
random time.
[   37.074459] device-mapper: uevent: version 1.0.3
[   37.075002] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: 
dm-de...@redhat.com
[   44.261128] using random self ethernet address
[   44.261148] using random host ethernet address
[   44.301103] using random self ethernet address
[   44.301123] using random host ethernet address
[   44.420543] usb0: HOST MAC b0:d5:cc:xx:xx:xx
[   44.424277] usb0: MAC b0:d5:cc:xx:xx:xx
[   44.431951] usb1: HOST MAC b0:d5:cc:xx:xx:xx
[   44.432459] usb1: MAC b0:d5:cc:xx:xx:xx
[   44.790231] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   44.907574] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[   46.432911] systemd[1]: apt-daily.timer: Adding 3h 49min 1.211334s 
random time.
[   47.095854] net eth0: initializing cpsw version 1.12 (0)
[   47.185601] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver 
[SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[   47.201861] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   47.201883] 8021q: adding VLAN 0 to HW filter on device eth0
[   49.216703] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full - 
flow control off
[   49.216810] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

root@arm:/home/debian# ip addr show eth0
2: eth0:  mtu 1500 qdisc mq state 
UP group default qlen 1000
link/ether b0:d5:cc:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 169.254.180.191/16 brd 169.254.255.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 fe80::b2d5:ccff:fexx:/64 scope link 
   valid_lft forever preferred_lft forever

root@arm:/home/debian# uname -a
Linux arm 4.14.67-ti-r73 #1 SMP PREEMPT Thu Aug 30 00:08:52 UTC 2018 armv7l 
GNU/Linux


I mostly want to try out btrfs as a filesystem (to avoid corruption) and 
possibly use the overlayroot, but it seems I need stretch for that.  Note 
that I've tried the 4.4 kernel version with the same results, so I guess 
it's either something in stretch, or a dtb issue.

Any ideas???

Thanks!

-W

-- 
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/9b152d9a-ced2-4de9-a337-9675a1cfc9db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Welcome the Fall 2018 Embedded Linux Class to this group

2018-09-06 Thread Fred Kerr 
And I should have read the links that were right there, first. Think before 
posting before coffee. Sorry!

On Thursday, September 6, 2018 at 7:27:00 AM UTC-7, Fred Kerr wrote:
>
> Hello - please pardon my ignorance, I hadn't heard about this class 
> before. Could you post some introductory context?
>
> Is it possible to join the class, is it remote or F2F?
>
> Thanks,
> Fred
>
> On Monday, August 27, 2018 at 5:28:04 AM UTC-7, Mark A. Yoder wrote:
>>
>> The purpose of this posting is to announce that I'm once again teaching 
>> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
>> the  *Green Wireless.* 
>> I'm teaching as open-source as I can and have have posted many of course 
>> materials on eLinux.org [2] and github[3].
>>
>> I'm always open to ideas on what topics to include in the class and 
>> suggestions for interesting course projects.  For example we are starting
>> Python this week and hope to be writing simple kernel module 5 weeks from 
>> now.  That will be followed by a week of PRU programming.
>>
>> Class, please respond to this posting.  Others, please welcome my class.
>>
>> --Mark 
>>
>> --Prof. Mark A. Yoder 
>>   Rose-Hulman Institute of Technology [4] 
>>
>> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
>> [2] http://elinux.org/index.php?title=Category:ECE497 
>> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
>> [4] http://www.rose-hulman.edu 
>>
>

-- 
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/7869343d-8482-46ff-a92a-27a061db03e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Welcome the Fall 2018 Embedded Linux Class to this group

2018-09-06 Thread Fred Kerr 
Hello - please pardon my ignorance, I hadn't heard about this class before. 
Could you post some introductory context?

Is it possible to join the class, is it remote or F2F?

Thanks,
Fred

On Monday, August 27, 2018 at 5:28:04 AM UTC-7, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *Green Wireless.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/86246295-a44e-4f3e-afe1-b3d61237ad7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: battery power for PocketBeagle?

2018-09-06 Thread Fred Kerr 
I am concerned about the battery temperature for safety in my office,
house, and around my 4-year-old son. :) And I'm curious about logging stuff
infinitum.

I have it working with a fixed resistor (without attempting charging yet).

On Thu, Sep 6, 2018 at 7:18 AM Graham Haddock  wrote:

> Fred:
> The temperature coefficient is only important if you are going to use them
> as temperature monitors, and you are going to thermally/mechanically attach
> them to the battery.
>
> If you are just trying to get the battery power supply to run, and are not
> concerned about battery temperatures, a fixed resistor will work fine.
>
> --- Graham
>
> ==
>
> On Thu, Sep 6, 2018 at 3:34 AM Fred Kerr  wrote:
>
>> I am looking for 10K NTC Thermistors with B=3480. How critical is the B
>> value, or what range can I accept? Currently I am looking on Mouser.
>>
>> Is there a specific or recommended battery pack? I'm just using an 18650
>> from a local surplus store.
>>
>> Regarding the log file, I still need to do this:
>>
>> sudo /opt/scripts/tools/developers/update_bootloader.sh
>>
>> I'll also look for 100K thermistor with B=3960
>>
>> On Thursday, August 30, 2018 at 5:35:43 PM UTC-7, Fred Kerr wrote:
>>>
>>> It runs well with the soldered implementation. My breadboards are a
>>> little cheap.
>>>
>>> The attached minicom_20180830b.cap shows a boot with microUSB power from
>>> a wall wart (from my rpi3), then a boot with the battery circuit. I left
>>> both RX and TX attached; I'll play with disconnecting them another time.
>>>
>>> I'll look into getting some "telemetry" info from the pocket beagle. I'm
>>> open to suggestions about things to add/log, etc. Also, I think this pocket
>>> beagle doesn't have a fix that I got before - after the shutdown, things
>>> panic.
>>>
>>> If anything else jumps out from the log file, please let me know!
>>>
>>> On Wednesday, August 29, 2018 at 10:59:03 AM UTC-7, Fred Kerr wrote:

 I'll try again soon with my more stable circuit (*soldered), also with
 RX disconnected so I just get output from the Pocket Beagle and the only
 power input is from the battery circuit.

 (*Soldered, so no loose breadboard connections, better current carrying
 capacity, etc.)

 What is a good way to share log files? Mine can get verbose! I could
 store it somewhere and post a link - suggestions welcomed! I have a lot of
 possibilities, but just let me know what works best for you.

 On Tuesday, August 28, 2018 at 12:51:23 PM UTC-7, Fred Kerr wrote:
>
> Yes, it ran quite a lot longer on the 1F, but still hung.
>
> I wired this up (see pic) to be more stable than the breadboard mess I
> had. The led on 1.8k resistor is gonna run a lot longer than I'll take at
> lunch!!!
>
> Can I isolate RX and TX or...oh I just need TX from the beagle for
> visibility!
>
> 1F 5.5v supercap (that battery was discharged to 3.96v). This one has
> more charge. Also put a 1000uf electrolytic on the soldered version,
> "because".
>
> Fred Kerr (mobile)
>
> On Tue, Aug 28, 2018, 12:13 PM Jason Kridner 
> wrote:
>
>>
>>
>> On Monday, August 27, 2018 at 11:15:36 PM UTC-4, Fred Kerr wrote:
>>>
>>> Hello all,
>>>
>>> I'm being just a little bit careful here:
>>>
>>> I'm about to try this, but I will connect up the serial terminal
>>> first, so I can see output and interact with the board. (Graceful 
>>> shutdown!)
>>>
>>
>> Don't connect the power or RX (ie., serial cable to PocketBeagle)
>> signals to avoid them interfering. Great thing to monitor.
>>
>>
>>>
>>> I will test the serial connection first with just a micro USB
>>> charging cable rather than USB to a computer. (Simplify!)
>>>
>>
>> Not sure what you are testing here. Are you just saying you'll power
>> via the microUSB connection and not connect to a computer, just to see 
>> the
>> behavior? You are monitoring with a serial connection?
>>
>>
>>>
>>> It's my understanding that LiPo charging is disabled or not present
>>> in the firmware. (I'll give you the "uname -a" and other info the next 
>>> time
>>> I fire it up. Just let me know what and how to check.)
>>>
>>
>> It is not enabled by default. There is a flag in the PMIC that needs
>> to be enabled. We've been playing with a driver to set the flag, but 
>> there
>> are other bugs in that driver not related to actually charging.
>>
>>
>>>
>>> Also, it's not clear (without reading the data sheet :) ) about the
>>> resistor values for the thermistor and the parallel (linearizing?) 
>>> resistor.
>>>
>>> If you have a 10K thermistor, do you put it in parallel with a 10K
>>> resistor, or likewise 100K thermistor in parallel with a 100K resistor? 
>>> Do
>>> you put the thermistor anywhere in contact

Re: [beagleboard] Re: battery power for PocketBeagle?

2018-09-06 Thread Graham Haddock 
Fred:
The temperature coefficient is only important if you are going to use them
as temperature monitors, and you are going to thermally/mechanically attach
them to the battery.

If you are just trying to get the battery power supply to run, and are not
concerned about battery temperatures, a fixed resistor will work fine.

--- Graham

==

On Thu, Sep 6, 2018 at 3:34 AM Fred Kerr  wrote:

> I am looking for 10K NTC Thermistors with B=3480. How critical is the B
> value, or what range can I accept? Currently I am looking on Mouser.
>
> Is there a specific or recommended battery pack? I'm just using an 18650
> from a local surplus store.
>
> Regarding the log file, I still need to do this:
>
> sudo /opt/scripts/tools/developers/update_bootloader.sh
>
> I'll also look for 100K thermistor with B=3960
>
> On Thursday, August 30, 2018 at 5:35:43 PM UTC-7, Fred Kerr wrote:
>>
>> It runs well with the soldered implementation. My breadboards are a
>> little cheap.
>>
>> The attached minicom_20180830b.cap shows a boot with microUSB power from
>> a wall wart (from my rpi3), then a boot with the battery circuit. I left
>> both RX and TX attached; I'll play with disconnecting them another time.
>>
>> I'll look into getting some "telemetry" info from the pocket beagle. I'm
>> open to suggestions about things to add/log, etc. Also, I think this pocket
>> beagle doesn't have a fix that I got before - after the shutdown, things
>> panic.
>>
>> If anything else jumps out from the log file, please let me know!
>>
>> On Wednesday, August 29, 2018 at 10:59:03 AM UTC-7, Fred Kerr wrote:
>>>
>>> I'll try again soon with my more stable circuit (*soldered), also with
>>> RX disconnected so I just get output from the Pocket Beagle and the only
>>> power input is from the battery circuit.
>>>
>>> (*Soldered, so no loose breadboard connections, better current carrying
>>> capacity, etc.)
>>>
>>> What is a good way to share log files? Mine can get verbose! I could
>>> store it somewhere and post a link - suggestions welcomed! I have a lot of
>>> possibilities, but just let me know what works best for you.
>>>
>>> On Tuesday, August 28, 2018 at 12:51:23 PM UTC-7, Fred Kerr wrote:

 Yes, it ran quite a lot longer on the 1F, but still hung.

 I wired this up (see pic) to be more stable than the breadboard mess I
 had. The led on 1.8k resistor is gonna run a lot longer than I'll take at
 lunch!!!

 Can I isolate RX and TX or...oh I just need TX from the beagle for
 visibility!

 1F 5.5v supercap (that battery was discharged to 3.96v). This one has
 more charge. Also put a 1000uf electrolytic on the soldered version,
 "because".

 Fred Kerr (mobile)

 On Tue, Aug 28, 2018, 12:13 PM Jason Kridner 
 wrote:

>
>
> On Monday, August 27, 2018 at 11:15:36 PM UTC-4, Fred Kerr wrote:
>>
>> Hello all,
>>
>> I'm being just a little bit careful here:
>>
>> I'm about to try this, but I will connect up the serial terminal
>> first, so I can see output and interact with the board. (Graceful 
>> shutdown!)
>>
>
> Don't connect the power or RX (ie., serial cable to PocketBeagle)
> signals to avoid them interfering. Great thing to monitor.
>
>
>>
>> I will test the serial connection first with just a micro USB
>> charging cable rather than USB to a computer. (Simplify!)
>>
>
> Not sure what you are testing here. Are you just saying you'll power
> via the microUSB connection and not connect to a computer, just to see the
> behavior? You are monitoring with a serial connection?
>
>
>>
>> It's my understanding that LiPo charging is disabled or not present
>> in the firmware. (I'll give you the "uname -a" and other info the next 
>> time
>> I fire it up. Just let me know what and how to check.)
>>
>
> It is not enabled by default. There is a flag in the PMIC that needs
> to be enabled. We've been playing with a driver to set the flag, but there
> are other bugs in that driver not related to actually charging.
>
>
>>
>> Also, it's not clear (without reading the data sheet :) ) about the
>> resistor values for the thermistor and the parallel (linearizing?) 
>> resistor.
>>
>> If you have a 10K thermistor, do you put it in parallel with a 10K
>> resistor, or likewise 100K thermistor in parallel with a 100K resistor? 
>> Do
>> you put the thermistor anywhere in contact with the (e.g., 18650) LiPo?
>>
>
> Looking at the TPS65217 datasheet says to put a 75kohm resistor in
> parallel.
>
> I'm not sure, but I believe the actual thermal resistor should be
> something like
> https://www.ametherm.com/blog/thermistors/thermistors-ntc-thermistor-temperature-sensors-provide-li-ion-battery-safety/
> .
>
>
>>
>> From the prior thread, it seems to be sufficient

Re: [beagleboard] config-pin i2c not working

2018-09-06 Thread Graham Haddock 
Mark:

Well, I suspect it would take a deep dive into the drivers to answer that.

I agree with what you would expect, but there is software involved.

I obviously does not like to be configured twice?
The configuration depends on some assumed initial states that are no longer
true when it has already been configured?

I am not knowing.

--- Graham

==


On Thu, Sep 6, 2018 at 8:33 AM Mark A. Yoder  wrote:

> Graham:
>   Yes, it works without configuring, but why does it stop working when
> configured to be i2c?  And why does it start working when configured to be
> gpio?  That's the opposite of what I'd expect.
>
> --Mark
>
> On Wednesday, September 5, 2018 at 5:12:06 PM UTC-4, Graham wrote:
>>
>> Mark:
>>
>> That bus is configured by default, so you should not have to configure it
>> to use it.
>> It is the bus used to probe for and talk to the memory chip on equipped
>> capes.
>> Try using the I2C-2 bus without configuration. It should just work.
>>
>> --- Graham
>>
>> optout .
>>
>

-- 
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/CANN_KV7xD0%2BamDr-G_-tF%3DfRrSv-OH%3D0tpJufabdh_XVOA0bFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Static IP setting issue for Ethernet in pocket beagle bone

2018-09-06 Thread evilwulfie 
Think Conman

On 9/5/2018 11:34 PM, di...@devtechm2m.com wrote:
> Dear,
>
> I am working with Pocket beagle bone debian 9.2 version, i have
> interfaced Wiznet W5500 Ethernet IC with SPI1 of PBB.
> I would like to set IP as static(192.168.3.213) but the PBB is taking
> IP as Dynamic for every reboot.
>
> For setting IP as static, I followed the below procedure.
>
> 1. sudo ifconfig eth0 192.168.3.213 netmask 255.255.255.0 
>
> with the above command it happend to set IP but after reboot again PBB
> is taking IP as Dynamic.
>
> 2. I have modified below file
> /etc/network/interfaces
> auto eth0
> iface eth0 inet static
> address 192.168.3.213
> netmask 255.255.255.0
> After changing the file, i have rebooted the PBB but still it is not modified 
> IP as Static.PBB is taking IP as Dynamic
> Can any one help on the above.
> Thanks in advance.
> -- 
> 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/b450e9de-a7bf-4746-a201-f6fe279ec6fd%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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/17153baa-28d4-9295-b4ec-e3a5cfc4a541%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Static IP setting issue for Ethernet in pocket beagle bone

2018-09-06 Thread di...@devtechm2m.com 
Dear,

I am working with Pocket beagle bone debian 9.2 version, i have interfaced 
Wiznet W5500 Ethernet IC with SPI1 of PBB.
I would like to set IP as static(192.168.3.213) but the PBB is taking IP as 
Dynamic for every reboot.

For setting IP as static, I followed the below procedure.

1. sudo ifconfig eth0 192.168.3.213 netmask 255.255.255.0 

with the above command it happend to set IP but after reboot again PBB is 
taking IP as Dynamic.

2. I have modified below file
/etc/network/interfaces

auto eth0
iface eth0 inet static
address 192.168.3.213
netmask 255.255.255.0

After changing the file, i have rebooted the PBB but still it is not modified 
IP as Static.PBB is taking IP as Dynamic

Can any one help on the above.

Thanks in advance.


-- 
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/b450e9de-a7bf-4746-a201-f6fe279ec6fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] config-pin i2c not working

2018-09-06 Thread Mark A. Yoder 
Graham:
  Yes, it works without configuring, but why does it stop working when 
configured to be i2c?  And why does it start working when configured to be 
gpio?  That's the opposite of what I'd expect.

--Mark

On Wednesday, September 5, 2018 at 5:12:06 PM UTC-4, Graham wrote:
>
> Mark:
>
> That bus is configured by default, so you should not have to configure it 
> to use it.
> It is the bus used to probe for and talk to the memory chip on equipped 
> capes.
> Try using the I2C-2 bus without configuration. It should just work.
>
> --- Graham
>
> ==
>
> On Wed, Sep 5, 2018 at 3:04 PM Mark A. Yoder  > wrote:
>
>> I'm using the i2c bus 2 that appears on P9_21 and P9_22 on the Bone Black.
>>
>> If I run:
>> bone$ *config-pin P9_21 i2c*
>> bone$ *config-pin P9_22 i2c*
>>
>> My i2c bus doesn't work, but if I run:
>> bone$ *config-pin P9_21 gpio*
>> bone$ *config-pin P9_22 **gpio*
>>
>> it does?  What's up?
>>
>> --Mark
>>
>> sudo /opt/scripts/tools/version.sh 
>> [sudo] password for debian: 
>> git:/opt/scripts/:[ed7dd4c61a9c9307b08db8a7dcbaffac77a7f776]
>> eeprom:[A335BNLT0A5C3513BBBK3281]
>> model:[TI_AM335x_BeagleBone_Black]
>> dogtag:[BeagleBoard.org Debian Image 2018-07-02]
>> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
>> 2018.03-2-gac9cce7c6a]:[location: dd MBR]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
>> 2016.03-1-g9a81f4a]:[location: dd MBR]
>> kernel:[4.18.1-bone4]
>> nodejs:[v6.14.3]
>> uboot_overlay_options:[enable_uboot_overlays=1]
>> uboot_overlay_options:[disable_uboot_overlay_video=1]
>>
>> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
>> uboot_overlay_options:[enable_uboot_cape_universal=1]
>> pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
>> ]
>> pkg:[bb-cape-overlays]:[4.4.20180628.0-0rcnee0~stretch+20180628]
>> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
>> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
>> pkg:[roboticscape]:[0.4.4-git20180608.0-0rcnee0~stretch+20180609]
>> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
>> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
>> admin spi tisdk weston-launch xenomai]
>> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
>> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
>> net.ifnames=0 quiet]
>> dmesg | grep pinctrl-single
>> [1.368684] pinctrl-single 44e10800.pinmux: 142 pins, size 568
>> dmesg | grep gpio-of-helper
>> [1.398397] gpio-of-helper ocp:cape-universal: ready
>> END
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/9b8153f1-ca60-420e-843e-dbb9863f68dd%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/356924fb-a347-4be2-9169-1014ea86cb49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: battery power for PocketBeagle?

2018-09-06 Thread Fred Kerr 
I am looking for 10K NTC Thermistors with B=3480. How critical is the B 
value, or what range can I accept? Currently I am looking on Mouser.

Is there a specific or recommended battery pack? I'm just using an 18650 
from a local surplus store.

Regarding the log file, I still need to do this:

sudo /opt/scripts/tools/developers/update_bootloader.sh

I'll also look for 100K thermistor with B=3960

On Thursday, August 30, 2018 at 5:35:43 PM UTC-7, Fred Kerr wrote:
>
> It runs well with the soldered implementation. My breadboards are a little 
> cheap.
>
> The attached minicom_20180830b.cap shows a boot with microUSB power from a 
> wall wart (from my rpi3), then a boot with the battery circuit. I left both 
> RX and TX attached; I'll play with disconnecting them another time.
>
> I'll look into getting some "telemetry" info from the pocket beagle. I'm 
> open to suggestions about things to add/log, etc. Also, I think this pocket 
> beagle doesn't have a fix that I got before - after the shutdown, things 
> panic.
>
> If anything else jumps out from the log file, please let me know!
>
> On Wednesday, August 29, 2018 at 10:59:03 AM UTC-7, Fred Kerr wrote:
>>
>> I'll try again soon with my more stable circuit (*soldered), also with RX 
>> disconnected so I just get output from the Pocket Beagle and the only power 
>> input is from the battery circuit. 
>>
>> (*Soldered, so no loose breadboard connections, better current carrying 
>> capacity, etc.)
>>
>> What is a good way to share log files? Mine can get verbose! I could 
>> store it somewhere and post a link - suggestions welcomed! I have a lot of 
>> possibilities, but just let me know what works best for you.
>>
>> On Tuesday, August 28, 2018 at 12:51:23 PM UTC-7, Fred Kerr wrote:
>>>
>>> Yes, it ran quite a lot longer on the 1F, but still hung.
>>>
>>> I wired this up (see pic) to be more stable than the breadboard mess I 
>>> had. The led on 1.8k resistor is gonna run a lot longer than I'll take at 
>>> lunch!!!
>>>
>>> Can I isolate RX and TX or...oh I just need TX from the beagle for 
>>> visibility!
>>>
>>> 1F 5.5v supercap (that battery was discharged to 3.96v). This one has 
>>> more charge. Also put a 1000uf electrolytic on the soldered version, 
>>> "because".
>>>
>>> Fred Kerr (mobile)
>>>
>>> On Tue, Aug 28, 2018, 12:13 PM Jason Kridner  wrote:
>>>


 On Monday, August 27, 2018 at 11:15:36 PM UTC-4, Fred Kerr wrote:
>
> Hello all,
>
> I'm being just a little bit careful here:
>
> I'm about to try this, but I will connect up the serial terminal 
> first, so I can see output and interact with the board. (Graceful 
> shutdown!)
>

 Don't connect the power or RX (ie., serial cable to PocketBeagle) 
 signals to avoid them interfering. Great thing to monitor.
  

>
> I will test the serial connection first with just a micro USB charging 
> cable rather than USB to a computer. (Simplify!)
>

 Not sure what you are testing here. Are you just saying you'll power 
 via the microUSB connection and not connect to a computer, just to see the 
 behavior? You are monitoring with a serial connection?
  

>
> It's my understanding that LiPo charging is disabled or not present in 
> the firmware. (I'll give you the "uname -a" and other info the next time 
> I 
> fire it up. Just let me know what and how to check.)
>

 It is not enabled by default. There is a flag in the PMIC that needs to 
 be enabled. We've been playing with a driver to set the flag, but there 
 are 
 other bugs in that driver not related to actually charging.
  

>
> Also, it's not clear (without reading the data sheet :) ) about the 
> resistor values for the thermistor and the parallel (linearizing?) 
> resistor.
>
> If you have a 10K thermistor, do you put it in parallel with a 10K 
> resistor, or likewise 100K thermistor in parallel with a 100K resistor? 
> Do 
> you put the thermistor anywhere in contact with the (e.g., 18650) LiPo?
>

 Looking at the TPS65217 datasheet says to put a 75kohm resistor in 
 parallel.

 I'm not sure, but I believe the actual thermal resistor should be 
 something like 
 https://www.ametherm.com/blog/thermistors/thermistors-ntc-thermistor-temperature-sensors-provide-li-ion-battery-safety/
 . 
  

>
> From the prior thread, it seems to be sufficient (if even necessary) 
> just to connect a 10K resistor from TS (P2-16) to ground (P2-15).
>

 Yes, that is supposed to work, ignoring the battery temperature.
  

>
> 10uF cap from battery (P2-14) to ground (P2-15).
>
> (Tangent/future: What about larger cap, perhaps using a 5.5V supercap, 
> detect supercap discharging (lipo voltage to ~min input voltage on vbat) 
> and give an interrupt to shut the board down?)
>
>