Flashing eMMC memory from SD card with Chipsee Debian Jessie

[Radovan Chovan]

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:  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.

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.sh

I 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.

[Robert Nelson]

On Tue, May 2, 2017 at 9:46 AM, Radovan Chovan <rad...@gmail.com> wrote:
> 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:
> 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.sh
>
> I 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,

--
Robert Nelson
https://rcn-ee.com/

[Radovan Chovan]

Dňa utorok, 2. mája 2017 16:52:46 UTC+2 RobertCNelson napísal(-a):

On Tue, May 2, 2017 at 9:46 AM, Radovan Chovan <rad...@gmail.com> wrote:

> you'll need to update the UUID variable in /boot/uEnv.txt along with
> the parameters in /etc/fstab

Note: I have access to SD card versions of these files, so I edited files on SD card (not on eMMC internal memory)
/etc/fstab - before changes:

# /etc/fstab: static file system information.
#
# Auto generated by RootStock-NG: setup_sdcard.sh
#
/dev/mmcblk0p1  /  ext4  noatime,errors=remount-ro  0  1
debugfs  /sys/kernel/debug  debugfs  defaults  0  0

/etc/fstab - after changes:

# /etc/fstab: static file system information.
#
# Auto generated by: beaglebone-black-eMMC-flasher.sh
#
UUID=50d572df-6313-4600-844c-5da83e43e5b5  /  ext4  noatime,errors=remount-ro  0  1
UUID=E302-7CCA  /boot/uboot  auto  defaults  0  0
debugfs  /sys/kernel/debug  debugfs  defaults  0  0

I used UUID values from my two BeagleBoneBlack Debian Wheezy(2014-05-14) boards (they have same UUID values, because they were flashed from same SD card I think) which runs on eMMC.



/boot/uEnv.txt - before changes:

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

#uname_r=4.4.9-ti-r25
uname_r=4.4.9+
#uuid=
#dtb=

##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)

##BeagleBone Black: HDMI (Audio/Video) disabled:
#dtb=am335x-boneblack-emmc-overlay.dtb

##BeagleBone Black: eMMC disabled:
#dtb=am335x-boneblack-hdmi-overlay.dtb

##BeagleBone Black: HDMI Audio/eMMC disabled:
#dtb=am335x-boneblack-nhdmi-overlay.dtb

##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
#dtb=am335x-boneblack-overlay.dtb

##BeagleBone Black: wl1835
#dtb=am335x-boneblack-wl1835mod.dtb

##BeagleBone Green: eMMC disabled
#dtb=am335x-bonegreen-overlay.dtb

cmdline=coherent_pool=1M quiet cape_universal=enable

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M quiet cape_universal=enable video=HDMI-A-1:1024x768@60e

##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
#cape_enable=bone_capemgr.enable_partno=

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

/boot/uEnv.txt - after changes

...
##note: the eMMC flasher script relies on the next line
mmcroot=UUID=50d572df-6313-4600-844c-5da83e43e5b5 ro
mmcrootfstype=ext4 rootwait fixrtc

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync

cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

Then I rebooted board via "sudo reboot". Switch SW8 on Chipsee board was still "uSD".

After reboot there is white background and Debian logo on it for one second, immediately after that there is black screen with "linux penguin" in left upper corner for cca 10 minutes and then only black screen.
USER LEDs state:
[x] [] [] []
USERLED0 is still blinking (2times quickly, then short pause and this is repeating).

When I removed SD card, switched SW8 to "eMMC", only Debian logo appeared for one second and then nothing happened.
USER LEDs state:
[] [] [] []
 
Is now my only solution flash SD card again? Fortunately I made backup (*.img) via Win32DiskImager.
And what could I do wrong with editing two mentioned files?

> Plug in a usb-serial adapter, you should see that eMMC flasher logging
> the process over serial

Do you have some "manual" for me, how can I see these logging messages on my PC(OS Windows8.1)?
But there is better option for me (which I used with Debian Wheezy and 4D Systems Touchscreen) : Flashing eMMC via "dd" command (OS runs on SD card via this process), then removing SD card and start OS from eMMC without inserted SD card.

Regards,

--
Radovan

[Radovan Chovan]

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?

[Radovan Chovan]

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

[Radovan Chovan]

I updated scripts using:

cd /opt/scripts/
git pull

Then I ran:

cd /opt/scripts/tools/eMMC/
sudo ./init-eMMC-flasher-v3.sh

Result:

================================================================================
eMMC has been flashed: please wait for device to power down.
================================================================================
Calling shutdown

But after removing SD card and switching SW8 to "eMMC", the BBB didn't boot - all 4 USER LEDs are lit, but nothing else happens.

[Robert Nelson]

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:

Jessie:
https://rcn-ee.net/rootfs/bb.org/testing/2017-05-07/lxqt-4gb/BBB-blank-debian-8.8-lxqt-4gb-armhf-2017-05-07-4gb.img.xz

Stretch:
https://rcn-ee.net/rootfs/bb.org/testing/2017-05-07/stretch-lxqt/BBB-blank-debian-stretch-lxqt-armhf-2017-05-07-4gb.img.xz

Use Etcher.io to write it to a microSD card:

https://etcher.io/

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:

#-----------------------------
#info: you are running: [4.4.62-ti-r99], latest is: [4.4.62-ti-r100] updating...

Step 4: Shutdown, plug in Chipsee LCD, (switch moved to eMMC) and apply power

Step 5: enjoy your lcd, lxqt will show up, touchscreen will track finger

Step 6: Profit

[Radovan Chovan]

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):

[Radovan Chovan]

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

[Radovan Chovan]

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

[Radovan Chovan]

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.

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 finished, there was message on putty (and then on touchscreen displayed):

================================================================================
eMMC has been flashed: please wait for device to power down.
================================================================================
Calling shutdown

==> Setting LEDs to

BeagleboneBlack board was automatically powered down.

Then I put this SD card to my new BeagleboneBlack board, connect via USB cable to my PC(OS Windows) and then after 15 seconds all 4 USER LEDS lit for short while, then "randomly" blinked some USER LEDs and after this only USER LED#0 blinked periodically and nothing more happened. BBB board was not recognized as new USB device. Ping 192.168.7.2 doesn't work.

So I want to ask how can I make "SD card flasher" or find out what's going wrong with SD card.
Thanks.

[Robert Nelson]

Please connect a usb serial adapter to the bbb and post the serial log
to pastebin.com with that "created" sd card..

[Radovan Chovan]

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):

[Radovan Chovan]

Hi,
here is log:
https://pastebin.com/wUABfyUU

Dňa utorok, 16. mája 2017 15:55:06 UTC+2 RobertCNelson napísal(-a):

[Radovan Chovan]

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
--
(initramfs) ls -l /dev/[hs]da*
ls: /dev/[hs]da*: No such file or directory
--
(initramfs) cat /proc/cmdline
console=ttyO0,115200n8 root=UUID=6021a462-9c63-4b6d-b9bd-f2899aeb9608 ro rootfstype=ext4 rootwait init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
--
(initramfs) ls -l /opt/scripts/tools/eMMC
ls: /opt/scripts/tools/eMMC: No such file or directory
--
(initramfs) ls -l /opt/scripts/
ls: /opt/scripts/: No such file or directory
--
(initramfs) ls -l /opt
ls: /opt: No such file or directory
--
(initramfs) cat /proc/modules
pru_rproc 15431 0 - Live 0xbf00e000
pruss_intc 8603 1 pru_rproc, Live 0xbf007000
pruss 12090 1 pru_rproc, Live 0xbf000000
--
(initramfs) uname -a
Linux (none) 4.4.62-ti-r103 #1 SMP Fri May 12 22:14:44 UTC 2017 armv7l GNU/Linux
--
(initramfs) ls -lh /dev/disk/by-uuid/
total 0
lrwxrwxrwx    1 0        0             15 Jan  1 00:00 04B8-ED71 -> ../../mmcblk1p1
lrwxrwxrwx    1 0        0             15 Jan  1 00:00 5a4cb80a-b996-4f9f-a74f-56737dab20de -> ../../mmcblk0p1
lrwxrwxrwx    1 0        0             15 Jan  1 00:00 9ce896da-274e-407e-aca1-b27b768b8dfc -> ../../mmcblk1p2
--

Dňa štvrtok, 18. mája 2017 9:07:30 UTC+2 Radovan Chovan napísal(-a):

[Robert Nelson]

On Thu, May 18, 2017 at 9:16 AM, Radovan Chovan <rad...@gmail.com> wrote:
> 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?

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. ;)

[Radovan Chovan]

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):

[Dennis Lee Bieber]

On Fri, 19 May 2017 05:49:04 -0700 (PDT), Radovan Chovan
<rad...@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)
--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[Radovan Chovan]

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):

[Radovan Chovan]

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.

[Dennis Lee Bieber]

On Sun, 21 May 2017 23:12:20 -0700 (PDT), Radovan Chovan
<rad...@gmail.com> declaimed the following:

>I used MiniTool Partition Wizard for finding out partition rootfs(ext4).
>But I cannot add drive letter to this partiton.

It does not surprise me -- Windows really only works with NTFS and
(ex)FAT formats.

However, the card reader slot itself should have a drive letter (mine
show up even with no card inserted). If you have NO drive letters for the
card reader slots then you may need to use the disk management console ("my
computer"/"this computer" -- right click/manage... Storage/Disk
Management).

The top will only show mounted "drives" (those with a file system
Windows recognizes). The bottom will show each physical drive with regions
indicating the partitioning. For a Windows format, the drive letter will be
in the partition area -- for empty card reader slots, the drive letter is
on the left side, such as:

Disk 4 (G:)
Removable
No Media

Disk 5 (H:)
Removable
No Media

Disk 6
Removable
No Media

4 is my SD card slot, 5 is my CF card slot. 6 (and 7) are Memory Stick
and some other little used card format. There is a reason they do not have
drive letters -- I removed them so they wouldn't show up, as I do not have
any cards in those formats.

If your SD card slot has no drive letter, right click on the "disk #"
and select "Change drive letter and paths". [ADD], (it should present the
next available drive letter by default), [OK], [OK]

[Radovan Chovan]

Thanks for your time.
I tried your instructions, I have

Disk 1
Removable (F:\)
No Media

But still no success with Win32DiskImager. I got Lock Error: An error occurred when attempting to lock the volume. Error 5: Access is denied. I tried to reboot my PC but it didn't help.

As I wrote in my last post I solved this problem using VirtualBox with Ubuntu, so please consider the problem resolved.

Dňa pondelok, 22. mája 2017 17:27:56 UTC+2 Dennis Lee Bieber napísal(-a):

[Dennis Lee Bieber]

On Mon, 22 May 2017 23:36:28 -0700 (PDT), Radovan Chovan
<rad...@gmail.com> declaimed the following:

>Thanks for your time.
>I tried your instructions, I have
>
>Disk 1
>Removable (F:\)
>No Media
>
>But still no success with Win32DiskImager. I got Lock Error: An error
>occurred when attempting to lock the volume. Error 5: Access is denied. I
>tried to reboot my PC but it didn't help.
>

Sounds like some other program is running in the background that has
taken ownership of the drive. Though a Google search seems to blame the
card reader itself:
https://openenergymonitor.org/forum-archive/node/3240.html
while others blame music players and anti-virus:
https://answers.launchpad.net/win32-image-writer/+question/205161
(though that is old enough that the author claims a change in processing at
the end). A more up-to-date thread is:
https://sourceforge.net/p/win32diskimager/tickets/9/
which had updates in December... How old is your copy of the program? The
current download appears to be only 2.5 months old.

>As I wrote in my last post I solved this problem using VirtualBox with
>Ubuntu, so please consider the problem resolved.
>

>D?a pondelok, 22. mája 2017 17:27:56 UTC+2 Dennis Lee Bieber napísal(-a):

>>
>> On Sun, 21 May 2017 23:12:20 -0700 (PDT), Radovan Chovan

>> <rad...@gmail.com <javascript:>> declaimed the following:

>> wlf...@ix.netcom.com <javascript:> HTTP://wlfraed.home.netcom.com/

[Radovan Chovan]

I saw the thread https://sourceforge.net/p/win32diskimager/tickets/9/ before, but nothing helped to me.
I 've used Win32DiskImager v0.8. I see, it exists v1.0 on sourgeforge.net.

Dňa utorok, 23. mája 2017 16:33:31 UTC+2 Dennis Lee Bieber napísal(-a):

[Radovan Chovan]

Hi RobertCNelson,

I downloaded "flasher" Debian image  "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" from https://beagleboard.org/latest-images.

It doesn't work with Chipsee display.

4 years ago we solved this problem for Debian Jessie 8.

Do you have some solution for newest Debian 10.3.?

I need new Debian version because Debian 8 Jessie support ended in June 2020.

Thanks.

Best Regards

Radovan Chovan

Dátum: streda 24. mája 2017, čas: 8:02:39 UTC+2, odosielateľ: Radovan Chovan

[Radovan Chovan]

Hi,

does anyone know if it is Chipsee cape compatible with newer Debian (9, 10) at all?

Thanks.

Dátum: utorok 6. apríla 2021, čas: 14:13:08 UTC+2, odosielateľ: Radovan Chovan