Project

General

Profile

Forums » Software Development »

Can not enable WL1837 Wi-Fi

Added by Lucas Andre Silva 24 days ago

Hello,

We've been trying to enable Wi-Fi support on the MitySOM-AM62A development kit (TI WL1837).

While following the procedures here does work on the pre-built reference image, we've been unable to get it to work when building `tisdk-edgeai-image` from scratch from the current commit of oe-layersetup.

U-Boot 2024.04-ti-g388d9d808b4b (Jan 15 2025 - 21:28:03 +0000)

SoC:   AM62AX SR1.0 HS-FS
Model: Critical Link MitySOM-AM62A
MitySOM-62x - Model No: 62A74-TX-XAE-RI Serial No: 24008030 Part Number: 80-001736RI-2A
DRAM:  4 GiB
Core:  92 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc1:1... 
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1, eth1: ethernet@8000000port@2
Hit any key to stop autoboot:  0 
Resetting HDMI tfp410
Setting bus to 1
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
628 bytes read in 34 ms (17.6 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
53172 bytes read in 168 ms (308.6 KiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 0 with data@addr=0x82000000 53172 bytes: Success!
11604048 bytes read in 381 ms (29 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 2 with data@addr=0x82000000 11604048 bytes: Success!
Failed to load 'rproc'
Failed to load 'u-boot'
27734528 bytes read in 1116 ms (23.7 MiB/s)
69014 bytes read in 39 ms (1.7 MiB/s)
Working FDT set to 88000000
2289 bytes read in 36 ms (61.5 KiB/s)
** No partition table - mmc 0 **
    Remote Processors are already initialized
Can't set block device
Can't set block device
Can't set block device
Can't set block device
Can't set block device
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'mmc 1' failed
Loading Boot0001 'mmc 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fa00000.bootdev':
Scanning bootdev 'mmc@fa10000.bootdev':
Bus usb@31100000: generic_phy_get_bulk : no phys property
Register 1000840 NbrPorts 1
Starting the controller
USB XHCI 1.10
scanning bus usb@31100000 for devices... 2 USB Device(s) found
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
ethernet@8000000port@2 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@2: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@2: am65_cpsw_start end error
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
ethernet@8000000port@2 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@2: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@2: am65_cpsw_start end error
No more bootdevs
---  -----------  ------  --------  ----  ------------------------  ----------------
(1 bootflow, 1 valid)

When we remove the name_overlays, the boot works (but without wifi support).

Any ideas why this happens?
Thanks
Lucas


Replies (7)

RE: Can not enable WL1837 Wi-Fi - Added by Jonathan Cormier 24 days ago

Hi Lucas,

We ran into this last week while we were testing the next release. I'll hurry along the release of the fix.

RE: Can not enable WL1837 Wi-Fi - Added by Lucas Andre Silva 23 days ago

Hi Jonathan

Thank you very much for the response and quick solution.

We will test this solution early next week and then provide feedback.

Thanks and Best Regards

Lucas

RE: Can not enable WL1837 Wi-Fi - Added by Lucas Andre Silva 19 days ago

Hello Jonathan,

Thanks again, we can confirm that the overlay is loaded and that the interface is up.

By the way, do you know if there's out-of-the-box support for the Bluetooth device on the WL1837? After a cursory glance I was unable to confirm.

Thanks and Best Regards
Lucas

RE: Can not enable WL1837 Wi-Fi - Added by Jonathan Cormier 19 days ago

Hi Lucas,

Good to hear.

By the way, do you know if there's out-of-the-box support for the Bluetooth device on the WL1837? After a cursory glance I was unable to confirm.

Unfortunately on our devkit, we hooked up the BT to WKUP_UART0, not realising that TI was already using that UART for their firmware. The -2 version of the baseboard has some 0-ohm resistors we can move to try using the UART2 instead but its was marked low priority to try.

We've used this WIFI module on the 335x previously and BT worked fine so I don't expect there to be issues with the driver. If you have need for it, I can get it put on the schedule to test.

The instructions we'd test would be very similar to the 335x wiki: https://support.criticallink.com/redmine/projects/armwifi/wiki/Bluetooth_Configuration_and_Usage

Do you know what mode you'd be using the BT for?

RE: Can not enable WL1837 Wi-Fi - Added by Jonathan Cormier 19 days ago

Note for a new design, I'd recommend swapping to a m.2. e-key connector as it will provide much more compatibility with wifi/bt modules of all brands and allow some flexibility if chip shortages happen again. I can provide a reference design if that interests you.

RE: Can not enable WL1837 Wi-Fi - Added by Lucas Andre Silva 18 days ago

Hello Jonathan

For my current project I don't need Bluetooth, but it would be good to test it for future applications.

If you could suggest a reference design I would appreciate it.

Thanks and Best Regards

Lucas

    (1-7/7)     Go to top
    Add picture from clipboard (Maximum size: 1 GB)