Actions
Forum Thread Details
  • Replies 18 replies
  • Subscribers 103 subscribers
  • Views 3061 views
  • Users 0 members are here
Related

Beaglebone Blue Bricked

jomoenginer

So, I loaded the latest Debian image for the Beaglebone boards, Debian 9.5 2018-10-07 4GB SD LXQT, and was using this for a short bit, but for some reason after trying to run a QT compiled program via remote ssh the BBBlue froze and will not boot any more.  I powered off the board and when it powers on only the Green and Red LEDS from the status bank stay constantly on and the Battery LEDs flash a bit but then 2 stay on constantly; CHG and the one labeled 75.

I have removed all of the EduMIP connections from the board as well as a n LCD that was connected but still nothing happens.  This board does not have the FTDI connections like the Black so I do not have a way to get a console to it to see if it is locking up somewhere.  

 

I've tried removing the SD card as well as use a known good one but still no luck. 

 

This board was running fine for sometime now so I am not sure what happened.  It was not until I loaded the new image that I ran into an issue.

 

Anyone else run into this issue with the Blue?

Parents

  • I got it working with an MSP432, Jon

    image

     

    I'll write down the instructions. It's easy.

  • in reply to Jan Cumps

    Locate the debug header. I used this website as inspiration.

    Ultimate Serial Port

     

    image

     

    You need:

    MSP432 LaunchPad , red or black) and BB

    2 USB cables, one for each. Don't plug in yet.

    3 female to female jumpers (I only have male to female and used a breadboard as interconnect.

    On your MSP432, remove the RXD and TXD jumpers in the middle. Don't worry about the other 4, they can be mounted or removed.

    image

    Connect TX to TX, RX to RX. (yes, I thought I needed to swap but it is what it is - edit:because the PCB of the launchpad labels the microcontroller side signals). See schematic. Tap the signals from the debugger side of the LaunchPad

     

    Then connect the MSP432 USB. Check in the Device monitor what port number is assigned to the UART.

    Open Putty, create a serial connection.

    Here are the settings (use your com port)

    image

    Connect.

     

    Nothing shows. That's normal

     

    Now plug in your BeagleBoard. Your putty session is an active UART session into the debug port.

     

    Good luck.

  • in reply to Jan Cumps

    Cool, but I have a few FDTI to USB cables so the MSP432 is not needed.  Also, this is a BB Blue not a Black which does not have the UART pins broke out like on a Black.  I'll have to try a JST to FTDI to USB connection to see if the console is output on one of the JST UART connections.

  • in reply to jomoenginer

    Good luck. The UART connectors don't all have the same size, it seems.

  • in reply to Jan Cumps

    I compared the schematics.

    The connector I'm using to capture the debug info is connected to signals UART0_TX and UART0_RX.

    On the Blue, these same signals are connected to UT0.

     

    image

     

    Edit: attention - on the Blue these lines are not buffered. They connect directly to the processor. On the Black there's a buffer in between.

     

    Edit2: I've been playing with the debug session a little.

    You have to pres the space bar fairly quick after startup (you have 2 seconds after the prompt) to get into uboot.

    ? gives the uboot help.

    I haven't found the command that forces a linux boot from SD Card ...

  • in reply to Jan Cumps

    Yeah, thanks, but I got that. I just have not connected to the board yet.

     

    However I doubt there will be much of anything coming out since the LEDs are not going through the normal boot sequence.  Just the RED and GREEN LED stay lit and no others outside of the battery LEDs light up.

     

    The Blue has a button labeled SD which should force a boot from SD card, however I believe the default is to boot from SD card if it is present.

  • in reply to jomoenginer

    No luck using the UARTs from the Blue.  There is no data coming from these interfaces in its current state. 

     

    I've posted this on the BeagleBoard Google forum as well but no response as of yet.  I did find another post there with a similar scenario but no resolve was posted so I'm calling it dead. 

     

    Oh, well.

Reply Children
No Data