This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DLPDLCR2000EVM: Re: BBB-blank-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img

Part Number: DLPDLCR2000EVM

Tool/software: Linux

I have not been able to get this release to boot and/or work so any help would be appreciated. I did get the image for bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img written to my 64GB micro SD and boot that to a Desktop on the HDMI port using a mouse and keyboard. But I can't get the examples to work properly. The cape is there and the Python scripts installed after all the updates but get a badly formatted image from the DLP Eval. I used the 9.1 release from the BeagleBoard site before the Jessie 8.9 link was available.

I use a Mac so I used its tools to write the image to the microSD. These look like:

diskutil list
diskutil unmountDisk /dev/disk2
sudo dd if=./BBB-blank-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img of=/dev/rdisk2 bs=1m

I check the card after it writes (I have ExtFS drivers) and rename the boot directive file as required. As I said, this works for the 9.1 image

But using this with the Jessie 8.9 build gets only the panning blue LED status but the EVM is lit with the default screen.

Does this Jessie build work only through SSH?

Or am I not writing the image properly?

Or do I need this release: bone-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img.xz ?

I have Linux (ubuntu 16 LTS) only as a VM - so would prefer to use Mac tools.

  • James,

    Thanks for your interest in our DLP products.

    I have a couple questions. First off, when you say "panning blue LED status" are you referring to the alternating pattern of 4 LEDs flashing one after the other?

    Second, You are referring to having trouble with a "badly formatted image from the DLP Eval". Can you describe what you mean by this in more detail?

    Best Regards,

    Philippe Dollo

  • The blue LEDs light sequentially back and forth like the Knight Rider car Kitt.

    I asked about a badly formed image but don't believe this is the issue any more. The directory structure and all files are readable. I do not believe I am having problems with the image transfer.

    I tried the bone-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img file and I believe that it booted properly as the LEDs settled into a pattern similar to the booting from the BBB without the microSD. However, I still see no data on the HDMI channel like I did with the 9.1 image from the BeagleBoard site or the build flashed into the BBB. The EVM lit up as it should as well.

    Is this build enabled for text (terminal) output or a desktop to the HDMI port or only SSH remote over the network? I haven't had time to check that yet as work has been very busy and holidays (relatives) coming...

  • James,

    Just to clarify, when you see this pattern the SD card is actually programming the on-board flash of the BeagleBone Black and installing the operating system. This is different from booting off the SD card. After the process completes and the LEDs turn off, you actually need to remove the SD card before powering on the system. Otherwise, you are effectively reinstalling the operating system every time you power on.

    I hope this helps,

    Philippe Dollo
  • Phillippe,

    Thank you for giving the LED status 411.

    I thought you had to hod the button down that is near the SD slot to get the BBB to flash to OS. The BBB-blank-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img.img exhibits this LED behavior this but not the bone-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img does not.

    Is there a file that is directing the BBB firmware to flash the SDcard file structure to the device. What I am really asking is about what each of these builds is designed to do. I don't see anything at / that different. The bbb-uEnv.txt files are identical and I am renaming them to enable the SDcard to boot (on both images after writing to SDcard) per

    ##Rename as: uEnv.txt to override old bootloader in eMMC
    ##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.

    I am a nOOb regarding the BBB so pardon my ignorance.

    James Carter
  • James,

    It is not easy to discern, but you have the right idea. The difference is as follows:

    > BBB-blank-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img
    This image will always write to the eMMC flash on the BBB and install the Debian OS onto it. You are supposed to boot the system once with the SD card inside, then remove the SD card and boot without the SD card every time afterwards.

    > bone-debian-8.9-lxqt-4gb-armhf-2017-08-01-4gb.img
    This image boots directly to the operating system and runs off of the SD card. System files are saved to the SD card instead of the eMMC flash. You need to have the SD card inserted every time you boot with this image.

    I recommend you also ask the BeagleBoard.org community for assistance with BeagleBone-specific inquiries. You can find them at beagleboard.org/discuss or http://beagleboard.org/discuss for non BBB devices.

    I hope this helps.

    Best Regards,
    Philippe Dollo
  • Thank you Philippe!

    I wish I had gotten this tidbit before trying to use the -blank- version. No doubt the BBB OS that was resident in the new kit has been corrupted. I guess I may as well just let the -blank- image finish the Flash process and go with that.

    Thanks again!
  • Glad to be of assistance. Best of luck in your development, James.

    Best Regards,

    Philippe Dollo