On Thu, May 18, 2017 at 5:06 PM Niels Jakob Buch wrote:
> Argh, waiting on a pile of JST-XX connectors to get the Blue-world up and
> running. But thanks!
>
I happen to really like the
https://www.seeedstudio.com/Grove-Universal-4-Pin-to-Beaglebone-Blue-4-Pin-Female-JST-SH-Conversion-Cable-10-pc
I have the same problem. I ordered two of those but both of them have I/O
error.
This happens with the eMMC and the SD card as well.
dmesg shows memory block errors.
Is it the hardware? Did I get 2 out of those 10 faulty ones?
On Thursday, 8 March 2018 17:46:53 UTC-8, megl...@gmail.com wrote:
I have tried:
- 4 distinct power supplies (3 x 5V, 1x 12V)
- SD card and built in memory
- 3 different OS images
-- latest 'iot' image from https://beagleboard.org/latest-images
-- image referenced in BeagleBoneBlue FAQ,
https://debian.beagleboard.org/images/bone-debian-8.7-iot-armhf-2017-03-19-4
Same problems on new Beagle Bone Blue.
Unpacked, powered up, worked like 5 minutes until IO errors.
Kind regards,
Bm
On Wednesday, August 23, 2017 at 11:49:22 PM UTC+2, Jeffrey Obadal wrote:
>
> I don't have my logs with me, but I believe mine looked pretty much just
> like that. Unfortunately
I don't have my logs with me, but I believe mine looked pretty much just
like that. Unfortunately both of mine spits out errors just trying to
update Debian. Using an SD Card delays the error a little longer, but
eventually it gets some disk access errors and goes into read only mode. I
wonder if t
I also am having the same issue. I thought it was broken hardware so I
bought a new one and the same thing happened again. I found that I can
usually induce the errors by transferring a large amount of files using
scp.
I'm going to check UART0 for additional information once I get the cabling
Any update on this problem. I ordered a beaglebone blue from Arrow and I'm
having the same problems. Writing/reading to the eMMC just randomly fails.
They sent me another one, this ones a little better... but eventually i get
input/output errors. I thought it was the power supply maybe at first,
I just checked and the JST-SH connector pins, inside the terminal are only
1mm apart. https://is.alicdn.com/img/pb/863/022/524/524022863_862.jpg
I guess I will wait for the wire assemblies.
On Friday, 19 May 2017 00:06:02 UTC+2, William Hermans wrote:
>
>
>
> On Thu, May 18, 2017 at 2:06 PM, Nie
On Thu, May 18, 2017 at 2:06 PM, Niels Jakob Buch wrote:
> Argh, waiting on a pile of JST-XX connectors to get the Blue-world up and
> running. But thanks!
>
So, I actually have no idea of the pin pitch on those JST headers. But the
serial debug cable I bought years ago, and still use. Has fairl
Argh, waiting on a pile of JST-XX connectors to get the Blue-world up and
running. But thanks!
On Thursday, 18 May 2017 22:21:46 UTC+2, William Hermans wrote:
>
> UART0 looks to be tied to a 4pin JST-SH connector. How exactly that works
> out, you'll have to tell me. I do not own a beaglebone bl
UART0 looks to be tied to a 4pin JST-SH connector. How exactly that works
out, you'll have to tell me. I do not own a beaglebone blue. Software wise
though, it should be exactly the same.
On Thu, May 18, 2017 at 6:01 AM, Niels Jakob Buch wrote:
> Will try that if attaching the cable does not wo
Will try that if attaching the cable does not work
Now comes the noob question: How do I attach the cable, seems that there is
plenty BeagleBone Black tutorials on that, but not sure how to do it on the
blue one.
On Wednesday, 17 May 2017 23:49:32 UTC+2, William Hermans wrote:
>
> A couple
A couple of other things you could try.
1) Occasionally installing Linux to an sdcard for this purpose can fail
silently. You could try to re-image the sdcard in hopes that this might be
the case in your situation.
2) Pick a slightly newer, or slightly older sdcard image, install that.
Then see i
On Wed, May 17, 2017 at 2:12 PM, Niels Jakob Buch wrote:
> That makes sense, will try that.
>
> But are there no log-file where this kernel output is stored?
>
Well it could be, but I do not think Robert persists logs between reboots.
Maybe I'm wrong. So then assuming if what I say is true, you'
That makes sense, will try that.
But are there no log-file where this kernel output is stored?
On Wednesday, 17 May 2017 22:48:24 UTC+2, William Hermans wrote:
>
> Get, and connect a serial debug cable. Connect to your support PC, use
> puTTY or another serial client software to view the kernel
Get, and connect a serial debug cable. Connect to your support PC, use
puTTY or another serial client software to view the kernel output as it's
running, and what errors are being displayed, when this happens.
On Wed, May 17, 2017 at 1:25 PM, Niels Jakob Buch wrote:
>
> Hi there, new to Beaglebo
16 matches
Mail list logo