Showing posts with label Beaglebone. Show all posts
Showing posts with label Beaglebone. Show all posts

Saturday, February 4, 2017

Flash BeagleBone (Black Rev C) eMMC with Debian Jessie IoT


  • Download the latest image,

wget https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz

  • Then write the image in to your SD card,

xzcat bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz | sudo dd of=/dev/sdc
sync

  • After the image is written to the SD card, mount the rootfs partition.
  • Then change directory to boot directory
  • vi uEnv.txt file and find below lines,

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

  • uncomment below line, save and exit

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


  • Enter the SD card in to the Beaglebone and connect the power. The OS will be flashed in to the eMMC for about 20 minutes and then all the LEDs will be turned off.
  • Remove the power code, then remove the SD card and connect the power again.

Sunday, March 13, 2016

My first experience with beaglebone serial port

Yesterday, I received beaglebone and PL2303HX USB to TTL serial cable I ordered few weeks a go. First thing I tried to do with the beaglebone was to try it's serial port.

So I connected the serial cable with the beaglebone and PC. I use fedora on my PC, so I used screen program to communicate with the serial port.

Then I powered up the beaglebone using the mini USB port and was waiting for the messages to be printed in the serial console.

Well, the good news was that messages were printed. but there were bad news.
sometimes it showed garbled messages. Also when it showed messages correctly, I wasn't able to type. It was simply a read only screen session.

What went wrong? I started googling and couldn't find any clue. finally I landed on a page where it lists beaglebone HW faults and it listed a similar scenario described as a HW fault. But it was a very old issue and cannot believe it still exists in new boards.

So I started diagnosing the issue.
First I tried to check whether it is an issue with the PC. Therefore I connected the beaglebone and the serial cable setup with my windows laptop. I did't get garbled messages on my screen session this time (I used Putty) but still I couldn't type.

So this must be an issue with either the beaglebone or the serial cable. If it's an issue with the beaglebone, I do not have any option. So I decided to diagnose the serial cable. I opened the USB side of the cable to check the circuit. the USB side can be easily opened since it was not sealed.

Huh, Found the issue!!!. The green wire was detached from the PCB due to a bad soldering job.
I soldered the green wire to the PCB again and reconnected the setup with the PC.

voila, screen session is bidirectional now. :)