I had the same problem with my BBBW. I tried both methods to make the wifi
work, but none was completly succesfull.
The "dd" method made no difference, the board still saw it as simple BBB.
The second method was succesful - the board was set as BBBW but when I
tried turning the Wifi on it
On Sun, Nov 18, 2018 at 2:35 PM wrote:
>
> Okay, now I'm curious.
>
> I was too lazy to ground a pin and run "dd", so I tried the "dtb" solution
> first. It worked.
>
> I can understand why the "dd" to fix the corrupted eeprom works. (That's
> RobertCNelson's solution.)
> Why does editing the
On Fri, Nov 9, 2018 at 2:56 PM wrote:
>
> Thank you for your assistance Robert.
> Unfortunately after following those steps the wlan0 and connman services
> still could not enable the wifi. Was there another step after executing "dd"
>
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
>
On Thu, Nov 8, 2018 at 9:46 PM wrote:
>
> here are the results - it should be a BeagleBone Black - Wireless.
> Something about the wlan0 not coming up too?
>
> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> ]eprom:[A335BNLTâ–’O
> model:[TI_AM335x_BeagleBone_Black]
>
On Thu, Nov 8, 2018 at 7:08 PM wrote:
>
> Sorry, what was the final solution to this?
> If I ground this pin everything will work?
Run this command and share it's output with us to help you debug:
sudo /opt/scripts/tools/version.sh
and then tell us what board it should be..
Regards,
--
Ok should've guessed that, it works now.
Thanks for the help Robert!
Burak
On Mon, Jan 29, 2018 at 8:43 PM, Robert Nelson
wrote:
> On Mon, Jan 29, 2018 at 11:40 AM, BURAK SONER wrote:
> > Hi Robert,
> >
> > I've grounded TP1 (something like a via I
Hi Robert,
I've grounded TP1 (something like a via I suppose so I stuck a jumper in
and connected the other end to P9-1). I checked with a thin tip multimeter
touching the golden part of the via (not the jumper) and verified they're
connected. I logged in as root and entered the following
On Mon, Jan 29, 2018 at 11:40 AM, BURAK SONER wrote:
> Hi Robert,
>
> I've grounded TP1 (something like a via I suppose so I stuck a jumper in and
> connected the other end to P9-1). I checked with a thin tip multimeter
> touching the golden part of the via (not the jumper)
On Mon, Jan 29, 2018 at 12:24 AM, BURAK SONER wrote:
> Hi Robert,
>
> Thanks for the quick answer! Here's the output:
>
> git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
> eeprom:[A335BNLT*]
Another case of eeprom mis-programmed:
GND TP1 then run as root:
dd
Hi Robert,
Thanks for the quick answer! Here's the output:
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT*]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.09-rc2-2-g7c9353]
kernel:[4.9.45-ti-r57]
On Sun, Jan 28, 2018 at 12:51 PM, wrote:
> Hi Robert,
>
> Same problem as Mostafa Bahrami on my side too. I've downloaded the other
> version of stretch. The file I've downloaded is ->
> "bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img"
>
> I can't see even a wlan0 device when
On Sat, Jan 7, 2017 at 11:31 AM, Kevin Gordon wrote:
> I carried out:
> "I now have the BBBW booting from the new image
> (debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb), configuring the 4DCAPE-70T
> display from its eeprom, with keyboard and mouse.
> #ifconfig -a //
12 matches
Mail list logo