I have no idea what you've done, and why your board isn't working as
shipped. *You* need to do some troubleshooting, figure out what the problem
is. Then fix it. Think of this as a good learning experience.

If the board is booting, and you have a serial debug cable already, then
you do not exactly *need* a sdcard. However, like the serial debug cable.
Having an sdcard around, can be very handy. How would you propose to fix
the eMMC file system if you ever put it in a non bootable state ?

Anyway, I would probably start with *ifconfig* on both sides of the
connection. To see why a connection is not happening. Passed that, *route
-n*, and *lsmod* may come in handy too.

On Mon, Mar 23, 2015 at 8:35 PM, Faddah Steve Yuetsu Wolf <[email protected]>
wrote:

>
> hello again, william,
>
> and thank you again for answering me back so promptly.
>
> i all ready do have a serial debug cable, it came as part of a "kit" for
> the beaglebone black rev. c from element14/eleduino (
> http://www.amazon.com/gp/product/B00P48PQTS/). it is the kind that is
> like the adafruit serial debug cable (
> http://elinux.org/Beagleboard:BeagleBone_Black_Serial#Adafruit_4_Pin_Cable_.28PL2303.29),
> the black wire going to the debug J1 jumper, the green going to pin 4 for
> recieve and the white going to pin 5 for transmit.
>
> i have all ready used it today to re-set the ssh server on the beaglebone
> and reboot it for changes to take effect using this app for Chromebooks,
> Beagle Term (
> https://chrome.google.com/webstore/detail/beagle-term/gkdofhllgfohlddimiiildbgoggdpoea)
> —  and it worked great (unless i did something like have it print screen of
> loooooong error logs, then it crashed my entire Chromebook waiting on it to
> get log messages all the way back from when the beaglebone black board and
> kernel were created/initialized).
>
> i got most of this info from the kind people in live chat/irc freenode
> #beagle channel.
>
> so, given i have the serial debug cable, any way you could please step me
> through what to do here? or do i still need to go out and get a microSD
> card to do the flash, etc.?
>
> please let me know. and i do appreciate all the help.
>
> best,
>
> —  faddah
>      portland, oregon, u.s.a.
>
>
>
> On Monday, March 23, 2015 at 8:16:17 PM UTC-7, William Hermans wrote:
>>
>> 1) get a blank sdcard.
>> 2) write a bootable 'stock' command line only image to it.
>> 3) edit the sdcard images files to either . . .
>>    a) load g_serial
>>    b) load g_ether and edit /etc/network/interfaces to reflect that both
>> the BBB and the host PC are on the same network. Be aware of the piece of
>> work, know as "connman"
>>    c) Just get an ethernet patch cable, and connect directly to the BBB
>> from the host PC. Again, edit /etc/network/interfaces to give *both* a
>> static IP and make sure both are on the same network.
>>    d) buy a serial debug cable, and connect via your favorite serial
>> communications app. No idea what is available on Chromium.miniconn probably
>> . . .
>>
>> Anyhow, once you're in, it should not be too much of a problem to
>> identify the eMMC, and troubleshoot whats going on. Ideally, a serial debug
>> cable would be best, as you get to see whats happening at boot time.
>> However, a decent one can cost around $20, and if you poke around and find
>> one on ebay for ~$2, you're likely going to be waiting for that slow boat
>> to arrive from China . . .
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to