Hi,
I have BeagleBoneBlack(revC) and this capacitive touchscreen from Chipsee (https://www.logicsupply.com/bbb-exp-c/).
From chipsee support I got this link with Debian Jessie: (with note: Currently we only have SD version for Jessie.)Now I have 16GB SD card with this Debian Jessie and with my custom stuff (java, sql, x11vnc, …) installed. I use only 2.81GiB of space because I want copy SD card partitions to internal eMMC memory of my BeagleBoneBlack board. Internal eMMC memory has 3.56GiB of free space. When I used OS Debian 7.5 Wheezy (2014-05-14) from I could use linux command for “flashing” eMMC memorythis way: But there is a problem with ChipseeDebian Jessie(20160728), when I copy partitions via command, power off the board, pull out the SD card from BBB, switch SW8 to “eMMC” on Chipsee board and then power on. For one second there is an image with white background and Debian logo on it and then only black screen and nothing happens. Also "ping " doesn’t work. When I have SD card inserted, there is also white background and Debian logo on it for one second, but immediately after that, there is black screen with “linux penguin” in left upper corner and then OS Debian Jessie successfully starts. So my question is how is it possible (if at all) to flash internal eMMC memory with my SD card(Debian Jessie with my custom stuff)? I 've found filewith this boot rule:##enable Generic eMMC Flasher:##make sure, these tools are installed: dosfstools rsync#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.shI uncommented line “cmdline” and reboot device. But OS Debian Jessie was started again without any flashing to eMMC memory.I am still trying to contact with chipsee support but they reply very rarely.
Hi,
I have BeagleBoneBlack(revC) and this capacitive touchscreen from Chipsee
(Shared Product 404 | OnLogic).
From chipsee support I got this link with Debian Jessie:
https://chipsee-us.s3.amazonaws.com/prebuilt-bbb/prebuilt-bbb-exp70-c-v2-debian-sd-20160728.tar.gz
(with note: Currently we only have SD version for Jessie.)Now I have 16GB SD card with this Debian Jessie and with my custom stuff
(java, sql, x11vnc, ...) installed.
I use only 2.81GiB of space because I want copy SD card partitions to
internal eMMC memory of my BeagleBoneBlack board.
Internal eMMC memory has 3.56GiB of free space.When I used OS Debian 7.5 Wheezy (2014-05-14) from
https://beagleboard.org/latest-images I could use linux command dd for
"flashing" eMMC memory this way:
sudo dd if=/dev/mmcblk0 of=/dev/mmcblk1 bs=10M, where mmbclk0 is SD card and
mmcblk1 is internal eMMC memory.But there is a problem with ChipseeDebian Jessie(20160728), when I copy
partitions via dd command, power off the board, pull out the SD card from
BBB,
switch SW8 to "eMMC" on Chipsee board and then power on.
you'll need to update the UUID variable in /boot/uEnv.txt along with
the parameters in /etc/fstab
For one second there is an image with white background and Debian logo on it
and then only black screen and nothing happens. Also "ping <ip address>"
doesn't work.
When I have SD card inserted, there is also white background and Debian logo
on it for one second, but immediately after that, there is black screen with
"linux penguin" in left upper corner and
then OS Debian Jessie successfully starts.So my question is how is it possible (if at all) to flash internal eMMC
memory with my SD card(Debian Jessie with my custom stuff)?
I 've found file /boot/uEnv.txt with this boot rule:
##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.shI uncommented line "cmdline" and reboot device. But OS Debian Jessie was
started again without any flashing to eMMC memory.I am still trying to contact with chipsee support but they reply very
rarely.
Plug in a usb-serial adapter, you should see that eMMC flasher logging
the process over serial
Regards,
Dňa utorok, 2. mája 2017 16:52:46 UTC+2 RobertCNelson napísal(-a):
I tried to find UUIDs using command ls -lh /dev/disk/by-uuid/
`
total 0
lrwxrwxrwx 1 root root 15 May 10 08:44 4e0b1eb4-56d0-41fb-af83-cd6b165ba3b5 → …/…/mmcblk1p2
lrwxrwxrwx 1 root root 15 May 10 08:44 BC9C-F1D3 → …/…/mmcblk1p1
`
I used these values for modifying files /etc/fstab and /boot/uEnv.txt (same way as I mentioned in previous post).
Then I flashed eMMC via “dd” command and I tried to run system without SD card. Result: black screen, no blinking USER LEDs.
Please, what am I doing wrong?
From http://beagleboard.org/latest-images
“To turn these images into eMMC flasher images, edit the /boot/uEnv.txt file on the Linux partition on the microSD card and remove the ‘#’ on the line with ‘cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh’. Enabling this will cause booting the microSD card to flash the eMMC. Images are no longer provided here for this to avoid people accidentally overwriting their eMMC flash.”
This didn’t work but I tried run this script manually:
cd /opt/scripts/tools/eMMC/ sudo ./init-eMMC-flasher-v3.sh
Then I tried to start system without inserted SD card. Screen is blank, but ping, ssh, even rdp works. VNC not because of blank screen.
From /var/log/lightdm/lightdm.log:
beaglebone lightdm[2909]: ** (lightdm:2909): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files beaglebone lightdm[2909]: ** (lightdm:2909): WARNING **: Error using VT_GETSTATE on /dev/console: Inappropriate ioctl for device beaglebone lightdm[2909]: ** (lightdm:2909): WARNING **: Error using VT_GETSTATE on /dev/console: Inappropriate ioctl for device
I updated scripts using:
cd /opt/scripts/ git pull
Then I ran:
`
cd /opt/scripts/tools/eMMC/
sudo ./init-eMMC-flasher-v3.sh
`
Result:
`
The Chipsee 7inch capes are fun as there is no eeprom (can bus is used
on those i2c pins)
Follow these instructions:
Step 1: Flash BBB without LCD plugged in:
Grab either image:
Use Etcher.io to write it to a microSD card:
Stick the microSD into the BBB (without the LCD plugged in), hold down
the "boot" button, insert power, remove finger from the 'boot" button,
let it flash (cyclon led pattern), wait till the board power's down.
Step 2: Remove microSD, First Boot, update /boot/uEnv.txt
With the board booted:
Open /boot/uEnv.txt
There are two 7inch Chipsee Lcd's
BBB + 7 Chipsee with Cap touch:
dtb=am335x-boneblack-bbb-exp-c.dtb
BBB + 7 Chipsee with Res touch:
dtb=am335x-boneblack-bbb-exp-r.dtb
and we need to disable uboot_overlays (this lcd doesn't support that)..
So in /boot/uEnv.txt (if you have the chipsee 7inch lcd) you'll need
to make two changes:
dtb=am335x-boneblack-bbb-exp-c.dtb
and change:
enable_uboot_overlays=1
to:
#enable_uboot_overlays=1
Step 3: (internet connection required) update kernel
There's a known issue with the "r99" kernel installed by default with
this lcd (just fixed it yesterday) update to "r100" or just wait till
next Monday when new images are published..
cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh
you should see:
Thank you very much for your time and detailed answer.
But as I wrote, I need “backup” SD card with my custom stuff which I want to use for flashing eMMC in another BBBs.
I 've found script /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
Is this the only option for me?
Dňa štvrtok, 11. mája 2017 18:51:15 UTC+2 RobertCNelson napísal(-a):
I followed your instructions.
After step 5 lxqt really showed up, touchscreen tracked finger (it will be needed calibration, but ok).
My changes:
1.)unblocking putty login via “root”
/etc/ssh/sshd_config: PermitRootLogin without-password —> PermitRootLogin yes
2.)
purging packages for freeing disk space: ti-llvm-3.6, upm, chromium-browser, nodejs, vim-runtime, qupzilla
3.)
purging connman, installing ifplugd, setting static IP address via /etc/network/interfaces
After some testing restarts (which I made continuously) I ended with black screen and for some minutes appeared "beaglebone login: " with blinking cursor
I tried your instructions even twice (with my changes in another order), but I ended still with same problem.
I 've found this discussion with similar problem, it seems: http://stackoverflow.com/questions/41608276/by-flashing-emmc-beaglebone-black-not-working-after-second-reboot
From /var/log/lightdm/lightdm.log:
`
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=2290
[+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Registered seat module surfaceflinger
[+0.07s] DEBUG: Adding default seat
[+0.07s] DEBUG: Seat: Starting
[+0.07s] DEBUG: Seat: Creating user session
[+0.08s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.08s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.08s] DEBUG: User debian added
[+0.09s] DEBUG: Seat: Creating display server of type x
[+0.10s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.10s] DEBUG: Using VT 7
[+0.10s] DEBUG: Seat: Starting local X display on VT 7
[+0.10s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.10s] DEBUG: DisplayServer x-0: Can’t launch X server X, not found in path
[+0.10s] DEBUG: DisplayServer x-0: X server stopped
[+0.10s] DEBUG: Releasing VT 7
[+0.10s] DEBUG: Seat: Display server stopped
[+0.10s] DEBUG: Seat: Can’t create display server for automatic login
[+0.10s] DEBUG: Seat: Session stopped
[+0.10s] WARNING: Error using VT_GETSTATE on /dev/console: Inappropriate ioctl for device
[+0.11s] DEBUG: Seat: Stopping display server, no sessions require it
[+0.11s] DEBUG: Seat: Creating greeter session
[+0.11s] DEBUG: Seat: Creating display server of type x
[+0.11s] DEBUG: Using VT 7
[+0.11s] DEBUG: Seat: Starting local X display on VT 7
[+0.11s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.11s] DEBUG: DisplayServer x-0: Can’t launch X server X, not found in path
[+0.11s] DEBUG: DisplayServer x-0: X server stopped
[+0.11s] DEBUG: Releasing VT 7
[+0.11s] DEBUG: Seat: Display server stopped
[+0.11s] DEBUG: Seat: Can’t create display server for greeter
[+0.11s] DEBUG: Seat: Session stopped
[+0.11s] DEBUG: Seat: Stopping display server, no sessions require it
[+0.11s] DEBUG: Seat: Stopping
[+0.11s] DEBUG: Seat: Stopped
`
I 've tried reinstall lightdm
sudo apt-get remove lightdm* --purge
sudo reboot
On display appeared:
Debian GNU/Linux 8 beaglebone tty1 BeagleBoard.org Debian Image 2015-05-07 Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian default username:password is [debian:temppwd] beaglebone login: <blinking cursor>
Then I install lightdm via putty
sudo apt-get install lightdm*
and restarted via sudo reboot
Display started but with logon screen on it for entering name and password.
I set autologon for lightdm in /etc/lightdm/lightdm.conf:
autologin-user=root
autologin-user-timeout=0
and then: dpkg-reconfigure lightdm
sudo reboot
link: http://www.linuxserve.com/2015/06/how-to-enable-automatic-login-on-debian.html
OS Debian start with autologon.
I hope this reinstalling will be sufficient for me.
link: http://www.linuxserve.com/2015/06/how-to-enable-automatic-login-on-debian.html
Hi,
I successfully installed my custum stuff(java,sql,vnc,…) on Debian Jessie (BBB-blank-debian-8.8-lxqt-4gb-armhf-2017-05-07-4gb.img.xz).
Then I tried make “SD card flasher” via this approach:
For many BeagleBone Debian users, there is a simple alternative of using the /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh to write an image from the on-board eMMC to a microSD card in a way that the microSD card becomes a "flasher" to write to other BeagleBone eMMCs. Simply boot off the on-board eMMC that you wish to copy, insert a blank microSD card at least 4GB, run the script as root and wait for the script to complete. At that point, you shut down your board and remove the microSD card. Booting off that microSD card on other BeagleBones should result in the typical "flasher" process writing the contents onto that BeagleBone's eMMC. The source code for the script is at [https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh](https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh).
source: http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents
uname -a: Linux beaglebone 4.4.62-ti-r103 #1 SMP Fri May 12 22:14:44 UTC 2017 armv7l GNU/Linux
I also updated scripts via “cd /opt/scripts” + “git pull”. I noticed that script file functions.sh was updated yesterday (15th May 2017) with note: eMMC: drop uuid usage.
When script [beaglebone-black-make-microSD-flasher-from-eMMC.sh](https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh) finished, there was message on putty (and then on touchscreen displayed):
Please connect a usb serial adapter to the bbb and post the serial log
to pastebin.com with that "created" sd card..
Regards,
Thanks for your answer.
I actually have only “TTL-232R-5V” cable. I assume, I need cable with 3.3V connectors because of preventing of BBB damage. So I’ve just ordered one (FTDI TTL-232R-3.3V).
Dňa utorok, 16. mája 2017 15:55:06 UTC+2 RobertCNelson napísal(-a):
Hi,
here is log:
https://pastebin.com/wUABfyUU
Dňa utorok, 16. mája 2017 15:55:06 UTC+2 RobertCNelson napísal(-a):
Hi,
I 've found out that you actually make some changes in https://github.com/RobertCNelson/boot-scripts/tree/master/tools/eMMC
It looks, it will be relevant for me, isn’t it?
From log https://pastebin.com/wUABfyUU
`
mount: can’t find /root in /etc/fstab
done.
Target filesystem doesn’t have requested /opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh.
`
Some printouts from initramfs:
`
(initramfs) ls -l /etc
-rw-r–r-- 1 0 0 0 May 16 2017 fstab
note: /etc/fstab is empty
Yeap it is..
UUID's are broken on v4.4.x-ti, luckly we have static mmc names in
v4.4.x-ti.. While 3.8.13 needs uuid's as the mmc names are not
static..
So your problem should also be fixed now on master. 
Regards,
It works great. Thank you. 
Now I have two identical BBBs with Chipsee display.
Only one question. Flasher on SD card consists now of one ext4 partition “rootfs”.
Is it possible to make *.img backup file from this ext4(linux) partitioned SD card on OS Windows 8.1? Win32DiskImager and Windows Explorer doesn’t recognize the SD card. Ether.io can only flash SD card from existing img file, I think. Or I have to use virt. PC with Ubuntu and maybe “dd”?
Dňa štvrtok, 18. mája 2017 21:05:52 UTC+2 RobertCNelson napísal(-a):
On Fri, 19 May 2017 05:49:04 -0700 (PDT), Radovan Chovan
<rado991@gmail.com> declaimed the following:
Only one question. Flasher on SD card consists now of one ext4 partition
"rootfs".
Is it possible to make *.img backup file from this ext4(linux) partitioned
SD card on OS Windows 8.1? Win32DiskImager and Windows Explorer doesn't
How did you determine that? By the lack of a volume label/properties in
the explorer?
Win32DiskImager, so far as I know, uses low level raw I/O operations on
the /device/, not the partition. Did you specify the correct device for the
SD card and try reading (well, also give it a file name in which to save).
You do have to put the SD card into the reader before starting
Win32DiskImager -- it doesn't seem to rescan the populated USB slots
otherwise (I just ran the sequence: open imager program, insert SD card,
check the drop down and only saw my two external hard drives; shut down
program, restart it, and now the SD card "drive" was listed)
I used MiniTool Partition Wizard for finding out partition rootfs(ext4). But I cannot add drive letter to this partiton.
I tried run Win32DiskImager as Admin, run it before inserting SD card, after inserting SD card, but without any success.
Dňa piatok, 19. mája 2017 15:58:24 UTC+2 Dennis Lee Bieber napísal(-a):
Thanks for your help RobertCNelson and Dennis Lee Bieber.
Finally I used Virtual Box with Ubuntu for creating backup .img file of my SD card flasher via “dd” command and then I shrunk this img file from 14,7GB to 3,5GB via “truncate” command.
Now I have all what I needed.