[beagleboard] Re: BB black Debian wifi problem
One more thing to check is that the firmware is available and gets loaded.
Then it has worked for me.
/Sven
Den måndag 2 mars 2015 kl. 11:17:05 UTC+1 skrev Dajiang He:
Hi,
I have a BB Black RevC with its original Debian OS.
When I plugged in a Aztech wifi dongle: the dongle's blue light is on.
when I do lsusb, I can see
us 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 006: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU
802.11n WLAN Adapter
Bus 001 Device 005: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
the wifi adapter is detected.
when I do lsmod,
Module Size Used by
binfmt_misc 5377 1
g_multi47670 2
libcomposite 14299 1 g_multi
arc41660 2
rtl8192cu 73560 0
rtlwifi63798 1 rtl8192cu
rtl8192c_common51523 1 rtl8192cu
mac80211 411868 3 rtlwifi,rtl8192c_common,rtl8192cu
cfg80211 344277 2 mac80211,rtlwifi
rfkill 16656 1 cfg80211
mt7601Usta601404 0
it looks like the driver is loaded into OS.
this is my interface file in /etc/networks regarding to wlan0 part
#auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
#nl80211
and wpa_supplicant part
network={
ap_scan=1
ssid=myssid
psk=**
key_mgmt=WPA-PSK2
My problem is I cannot get the wifi connection.
If I do ifconfig, I can see wlan0.
Can any expert tell me what I missed?
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: how to copy sd card kernel image into emmc memory of beaglebone black by uisng windows os?
As far as I remember, kernel is not located on a Windows-readable filesystem. Its easy enough to copy kernel when running Linux though. You must also copy modules directory (in /lib/modules) for the kernel you want to boot normally. And maybe change some uEnv variables. /Sven Den fredag 16 september 2016 kl. 07:19:52 UTC+2 skrev kara...@yahoo.com: > > how to copy sd card kernel image into emmc memory of beaglebone black by > uisng windows os? > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/91a0fce9-37d1-4f03-8b6d-1b54a8d29ff6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Buildroot question ?
As I see it you should raw copy sdcard.img (dd, etcher) to a sdcard and make sure it gets booted from. /Sven Den fredag 5 maj 2017 kl. 13:38:53 UTC+2 skrev bianchi: > > Everyone, > > I have built a boot image for BeagleBone Black with buildroot, > until : > > -rw-r--r-- 1 bianchi bianchi37264 May 5 13:32 am335x-boneblack.dtb > -rw-r--r-- 1 bianchi bianchi35372 May 5 13:32 am335x-bone.dtb > -rw-r--r-- 1 bianchi bianchi42096 May 5 13:32 am335x-evm.dtb > -rw-r--r-- 1 bianchi bianchi40888 May 5 13:32 am335x-evmsk.dtb > -rw-r--r-- 1 bianchi bianchi 16777216 May 5 16:26 boot.vfat > -rw-r--r-- 1 bianchi bianchi78292 May 5 13:18 MLO > -rw-r--r-- 1 bianchi bianchi 14505984 May 5 16:26 rootfs.ext2 > lrwxrwxrwx 1 bianchi bianchi 11 May 5 16:26 rootfs.ext4 -> > rootfs.ext2 > -rw-r--r-- 1 bianchi bianchi 10649600 May 5 16:26 rootfs.tar > -rw-r--r-- 1 bianchi bianchi 3424743 May 5 16:26 rootfs.tar.bz2 > -rw-r--r-- 1 bianchi bianchi 31283712 May 5 16:26 sdcard.img > -rw-r--r-- 1 bianchi bianchi 625888 May 5 13:17 u-boot.img > -rwxr-xr-x 1 bianchi bianchi2 May 5 13:18 u-boot-spl.bin > -rw-r--r-- 1 bianchi bianchi 186 May 5 16:26 uEnv.txt > -rw-r--r-- 1 bianchi bianchi 4995616 May 5 13:32 zImage > > My question is, > How can I make it boot until Linux prompt ? > > Thanks > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3769598d-baed-423a-a0d5-145c3aeda726%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Build root(can't open /dev/ttyO0: No such file or directory )
Hi. The serial ports have been default-renamed from ttyOx to ttySx. There is a kernel config to not do this. Or you can create links from /dev/ttyOx to /dev/ttySx so that programs trying to use ttyOx works. /Sven Den fredag 6 september 2019 kl. 11:43:38 UTC skrev jennifer Dsilva: > > Hi , > > I am using Build root buildroot-2018.08. I am doing nfs mounting on > Beaglebone black. > > while booting I am getting the following logs. > > How to fix this issue..Need help > > > > ubuntu@ubuntu-MS-7A15:~$ sudo minicom > [sudo] password for ubuntu: > > Welcome to minicom 2.7.1 > > OPTIONS: I18n > Compiled on Aug 13 2017, 15:25:34. > Port /dev/ttyUSB0, 16:43:29 > > Press CTRL-A Z for help on special keys > > > U-Boot SPL 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500) > Trying to boot from MMC2 > Loading Environment from EXT4... > ** Unable to use mmc 0:1 for loading the env ** > > > U-Boot 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: > jenkins5 > > CPU : AM335X-GP rev 2.1 > I2C: ready > DRAM: 512 MiB > No match for driver 'omap_hsmmc' > No match for driver 'omap_hsmmc' > Some drivers were not found > > Reset Source: Power-on reset has occurred. > > RTC 32KCLK Source: External. > > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > Loading Environment from EXT4... > > ** Unable to use mmc 0:1 for loading the env ** > > Board: BeagleBone Black > > not set. Validating first E-fuse MAC > > BeagleBone Black: > > BeagleBone: cape eeprom: i2c_probe: 0x54: > > BeagleBone: cape eeprom: i2c_probe: 0x55: > > BeagleBone: cape eeprom: i2c_probe: 0x56: > > BeagleBone: cape eeprom: i2c_probe: 0x57: > > Net: eth0: MII MODE > > cpsw, usb_ether > > Press SPACE to abort autoboot in 2 seconds > > board_name=[A335BNLT] ... > > board_rev=[00C0] ... > > switch to partitions #0, OK > > mmc0 is current device > > SD/MMC found on device 0 > > switch to partitions #0, OK > > mmc0 is current device > > Scanning mmc 0:1... > > gpio: pin 56 (gpio 56) value is 0 > > gpio: pin 55 (gpio 55) value is 0 > > gpio: pin 54 (gpio 54) value is 0 > > gpio: pin 53 (gpio 53) value is 1 > > switch to partitions #0, OK > > mmc0 is current device > > gpio: pin 54 (gpio 54) value is 1 > > Checking for: /uEnv.txt ... > > 500 bytes read in 5 ms (97.7 KiB/s) > > gpio: pin 55 (gpio 55) value is 1 > > Loaded environment from /uEnv.txt > > Importing environment from mmc ... > > Checking if uenvcmd is set ... > > gpio: pin 56 (gpio 56) value is 1 > > Running uenvcmd ... > > Booting from network... > > link up on port 0, speed 100, full duplex > > Using cpsw device > > TFTP from server 192.168.7.1; our IP address is 192.168.7.3 > > Filename 'uImage'. > > Load address: 0x8200 > > Loading: >
Re: [beagleboard] writing data to 1-wire DS2433 eeprom fails
The eeprom probably is a device, not a filesystem. Use dd instead. /Sven tisdag 29 september 2020 kl. 17:59:14 UTC+2 skrev Johan Lind: > I tried with only a short (6 bytes) string but still the same behaviour. > > > tisdag 29 september 2020 kl. 17:45:47 UTC+2 skrev robert.sty...@gmail.com: > >> I suggest trying to write less than 32 bytes (the dmesg implies something >> wrong with offset or count) -- create a file of less than 32 bytes and copy >> to eeprom >> cd ~ >> echo "1234567890" > file10 >> cp -T file10 /sys/bus/w1/devices/23-02eddd9b/eeprom >> >> In the data sheet you need a much smaller R[PU] to write than read >> https://datasheets.maximintegrated.com/en/ds/DS2433.pdf >> >> On Tuesday, 29 September 2020 at 16:03:48 UTC+1 RobertCNelson wrote: >> >>> On Tue, Sep 29, 2020 at 9:55 AM 'Johan Lind' via BeagleBoard >>> wrote: >>> > >>> > Yes, it does still show eeprom >>> > >>> > debian@beaglebone:~$ ls /sys/bus/w1/devices/23-02eddd9b >>> > driver eeprom id name power subsystem uevent >>> > debian@beaglebone:~$ ls /sys/bus/w1/devices/ >>> > 23-02eddd9b w1_bus_master1 >>> > debian@beaglebone:~$ >>> > debian@beaglebone:~$ ls -al /sys/bus/w1/devices/23-02eddd9b/ >>> > total 0 >>> > drwxrwxr-x 3 root gpio 0 Sep 29 14:00 . >>> > drwxrwxr-x 4 root gpio 0 Sep 29 14:00 .. >>> > lrwxrwxrwx 1 root gpio 0 Sep 29 14:00 driver -> >>> ../../../bus/w1/drivers/w1_slave_driver >>> > -rw-rw-r-- 1 root gpio 512 Sep 29 14:07 eeprom >>> >>> Side note, you don't' have to be root, the "gpio" group is the default >>> for debian.. >>> >>> > -r--r--r-- 1 root gpio 4096 Sep 29 14:00 id >>> > -r--r--r-- 1 root gpio 4096 Sep 29 14:00 name >>> > drwxrwxr-x 2 root gpio 0 Sep 29 14:00 power >>> > lrwxrwxrwx 1 root gpio 0 Sep 29 14:00 subsystem -> ../../../bus/w1 >>> > -rw-rw-r-- 1 root gpio 4096 Sep 29 14:00 uevent >>> > debian@beaglebone:~$ >>> >>> not sure why you can't write... >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >> -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/69f994ba-cbbd-4680-840a-a353be874be9n%40googlegroups.com.
Re: [beagleboard] writing data to 1-wire DS2433 eeprom fails
Maybe kernel must have crc enabled for 2433 writes? Last line implies something about writes. config W1_SLAVE_DS2433 tristate "4kb EEPROM family support (DS2433)" help Say Y here if you want to use a 1-wire 4kb EEPROM family device (DS2433). config W1_SLAVE_DS2433_CRC bool "Protect DS2433 data with a CRC16" depends on W1_SLAVE_DS2433 select CRC16 help Say Y here to protect DS2433 data with a CRC16. Each block has 30 bytes of data and a two byte CRC16. Full block writes are only allowed if the CRC is valid. /Sven onsdag 30 september 2020 kl. 10:56:55 UTC+2 skrev Johan Lind: > Well, I have an i2c memory on the same board and to read and write to that > I can use the following commands: > write > cat data.eeprom > /sys/bus/i2c/devices/2-0057/eeprom > read > cat /sys/bus/i2c/devices/2-0057/eeprom | hexdump > > I did try your suggestion of using dd but I could not get it to work. > root@beaglebone:/home/debian# dd if=/dev/zero > of=/sys/bus/w1/devices/23-02eddd9b/eeprom bs=32 > dd: error writing '/sys/bus/w1/devices/23-02eddd9b/eeprom': Invalid > argument > 1+0 records in > 0+0 records out > 0 bytes copied, 0.0159578 s, 0.0 kB/s > root@beaglebone:/home/debian# > > As the eeprom is written to contain data on another device, so I thought > it would be enough to use /dev/zero as input. > Reading out data show no change of content (as expected consider the > output from dd) > cat /sys/bus/w1/devices/23-02eddd9b/eeprom | hexdump > 000 00ff 55aa 00ff 55aa 00ff 55aa 00ff 55aa > onsdag 30 september 2020 kl. 07:15:53 UTC+2 skrev Sven Norinder: > >> The eeprom probably is a device, not a filesystem. >> Use dd instead. >> /Sven >> >> tisdag 29 september 2020 kl. 17:59:14 UTC+2 skrev Johan Lind: >> >>> I tried with only a short (6 bytes) string but still the same behaviour. >>> >>> >>> tisdag 29 september 2020 kl. 17:45:47 UTC+2 skrev >>> robert.sty...@gmail.com: >>> >>>> I suggest trying to write less than 32 bytes (the dmesg implies >>>> something wrong with offset or count) -- create a file of less than 32 >>>> bytes and copy to eeprom >>>> cd ~ >>>> echo "1234567890" > file10 >>>> cp -T file10 /sys/bus/w1/devices/23-02eddd9b/eeprom >>>> >>>> In the data sheet you need a much smaller R[PU] to write than read >>>> https://datasheets.maximintegrated.com/en/ds/DS2433.pdf >>>> >>>> On Tuesday, 29 September 2020 at 16:03:48 UTC+1 RobertCNelson wrote: >>>> >>>>> On Tue, Sep 29, 2020 at 9:55 AM 'Johan Lind' via BeagleBoard >>>>> wrote: >>>>> > >>>>> > Yes, it does still show eeprom >>>>> > >>>>> > debian@beaglebone:~$ ls /sys/bus/w1/devices/23-02eddd9b >>>>> > driver eeprom id name power subsystem uevent >>>>> > debian@beaglebone:~$ ls /sys/bus/w1/devices/ >>>>> > 23-02eddd9b w1_bus_master1 >>>>> > debian@beaglebone:~$ >>>>> > debian@beaglebone:~$ ls -al /sys/bus/w1/devices/23-02eddd9b/ >>>>> > total 0 >>>>> > drwxrwxr-x 3 root gpio 0 Sep 29 14:00 . >>>>> > drwxrwxr-x 4 root gpio 0 Sep 29 14:00 .. >>>>> > lrwxrwxrwx 1 root gpio 0 Sep 29 14:00 driver -> >>>>> ../../../bus/w1/drivers/w1_slave_driver >>>>> > -rw-rw-r-- 1 root gpio 512 Sep 29 14:07 eeprom >>>>> >>>>> Side note, you don't' have to be root, the "gpio" group is the default >>>>> for debian.. >>>>> >>>>> > -r--r--r-- 1 root gpio 4096 Sep 29 14:00 id >>>>> > -r--r--r-- 1 root gpio 4096 Sep 29 14:00 name >>>>> > drwxrwxr-x 2 root gpio 0 Sep 29 14:00 power >>>>> > lrwxrwxrwx 1 root gpio 0 Sep 29 14:00 subsystem -> ../../../bus/w1 >>>>> > -rw-rw-r-- 1 root gpio 4096 Sep 29 14:00 uevent >>>>> > debian@beaglebone:~$ >>>>> >>>>> not sure why you can't write... >>>>> >>>>> Regards, >>>>> >>>>> -- >>>>> Robert Nelson >>>>> https://rcn-ee.com/ >>>>> >>>> -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e73a99a5-1f00-4d62-9dea-016856f8f1d3n%40googlegroups.com.
