RE: Bringing up the BRCM43362 on Beaglebone Black

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Some progress, but I'm hoping that someone can give me a clue...

I have set up the pins on mmc0 according to the TI pinmux tool and I am
following the example from the kernel documentation which shows how to setup
a node with properties controlling the Broadcom wireless device.  (See the
dtsi snippets below)

The board detects the 43362 module and attempts to load the firmware and
nvram data.  Unfortunately, inserting the module after the board is up
causes things to die and booting with the module in the SDIO slot causes me
to end up at the initramfs prompt.

According to the pinmux tool MMC0 should not be overlapping with MMC1 so I
am not entirely sure why there is a conflict.

Any thoughts?



>From am335x-bone-common.dtsi:

              mmc1_pins: pinmux_mmc1_pins {
                      pinctrl-single,pins = <
                              0x100 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /*
(G17) mmc0_clk.mmc0_clk */
                              0x104 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /*
(G18) mmc0_cmd.mmc0_cmd */
                              0xfc ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G16)
mmc0_dat0.mmc0_dat0 */
                              0xf8 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G15)
mmc0_dat1.mmc0_dat1 */
                              0xf4 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (F18)
mmc0_dat2.mmc0_dat2 */
                              0xf0 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (F17)
mmc0_dat3.mmc0_dat3 */
                      >;
              };

	&mmc1 {
	        status = "okay";
	        vmmc-supply = <&wlan_en_reg>;
	        bus-width = <0x4>;
	        pinctrl-names = "default";
	        pinctrl-0 = <&mmc1_pins>;

	        ti,non-removable;
	        keep-power-in-suspend;

	        brcmf: bcrmf@1 {
	                reg = <1>;
	                compatible = "brcm,bcm4329-fmac";
	                interrupt-parent = <&gpio3>;
	                interrupts = <21 0x4>;
	                interrupt-names = "host-wake";
	        };
	};


This is the output from the system when I boot with the module in the SDIO
card slot...



U-Boot SPL 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15)
Trying to boot from MMC
bad magic


U-Boot 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15 -0500), Build:
jenkins-github_Bootloader-Builder-351

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
Card did not respond to voltage select!
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
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1: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
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
1240 bytes read in 15 ms (80.1 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-4.4.9-ti-r25 ...
7833256 bytes read in 445 ms (16.8 MiB/s)
loading /boot/dtbs/4.4.9-ti-r25/am335x-boneblack.dtb ...
61356 bytes read in 28 ms (2.1 MiB/s)
loading /boot/initrd.img-4.4.9-ti-r25 ...
4982404 bytes read in 289 ms (16.4 MiB/s)
debug: [console=ttyO0,115200n8
root=UUID=db3220db-46db-4ddc-8504-e5a149f91b6f ro rootfstype=ext4 rootwait
coherent_pool=1M quiet cape_universal=enable] ...
debug: [bootz 0x82000000 0x88080000:4c0684 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x7786a8 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8fb3f000, end 8ffff684 ... OK
   Loading Device Tree to 8fb2d000, end 8fb3efab ... OK

Starting kernel ...

[    2.019050] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    2.190699] omap_voltage_late_init: Voltage driver support not added
[    2.198119] PM: Cannot get wkup_m3_ipc handle
[    2.309576] bone_capemgr bone_capemgr: slot #0: No cape found
[    2.353579] bone_capemgr bone_capemgr: slot #1: No cape found
[    2.397568] bone_capemgr bone_capemgr: slot #2: No cape found
[    2.441568] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait...
mount: can't find /root in /etc/fstab
Target filesystem doesn't have requested /sbin/init.
mount: mounting /dev on /root/dev failed: No such file or directory
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
modprobe: module ehci-pci not found in modules.dep
modprobe: module ehci-orion not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep


BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)







-----Original Message-----
From: linux-omap-owner@xxxxxxxxxxxxxxx
[mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren
Sent: Tuesday, June 7, 2016 2:05 AM
To: Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx>
Cc: linux-omap@xxxxxxxxxxxxxxx
Subject: Re: Bringing up the BRCM43362 on Beaglebone Black

* Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx> [160603 10:51]:
> Any idea what is wrong and how to get the 43362 module up and running 
> on the Beaglebone Black?

Please check pin muxing, regulators and clocks for the MMC.
Then you need to check the regulators and clocks for the WLAN module. The
WLAN module typically has some GPIO pin to enable it that might be in
addition to the regulator.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the
body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at
http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux