Bug 194251 - Efika MX Smartbook (imx51) WiFi does not work anymore
Summary: Efika MX Smartbook (imx51) WiFi does not work anymore
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: CURRENT
Hardware: arm Any
: --- Affects Only Me
Assignee: freebsd-arm (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-08 19:25 UTC by Guillaume Bibaut
Modified: 2018-05-28 19:45 UTC (History)
2 users (show)

See Also:


Attachments
usbconfig output (471 bytes, text/plain)
2014-10-09 06:17 UTC, Guillaume Bibaut
no flags Details
dmesg.boot (10.07 KB, text/plain)
2014-10-10 17:20 UTC, Guillaume Bibaut
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume Bibaut 2014-10-08 19:25:38 UTC
I had compiled a 11-CURRENT FreeBSD for Efika MX during August 2014, and most things and especially the Wireless Network Interface was working nice at that time.
I've just compiled a new pull of 11-CURRENT for the same hardware and have installed it, and now the WiFi does not work anymore. It was using the if_run driver. But even if I load the driver, nothing happens at all.

I can see that during september 2014 there were some refactor of the imx IOMUX code in the sys/arm/freescale/imx tree and I'm thinking it may be linked to that.
It seems the commiter is 'ian'.

Could someone look into this please ? I'd like my Efika MX Smartbook not to become useless :)
Comment 1 Ian Lepore freebsd_committer 2014-10-09 03:34:14 UTC
The old imx51 iomux code wasn't so much refactored as just plain deleted because it was completely unused.  There is no pinmux data in the efikamx.dts or imx51.dtsi files, and no drivers or other code ever called the imx51 iomux functions.

To my understanding, we have always relied on using a "usb start" command in u-boot to configure the clocks and pins for usb.  The usb on my imx53 system has never worked unless I do "usb start" in u-boot first.

Does the usbconfig command show any devices besides the root hub after you've booted?
Comment 2 Guillaume Bibaut 2014-10-09 06:17:17 UTC
Created attachment 148127 [details]
usbconfig output

There is no ethernet device in the usbconfig output, while the wifi switch is on.
Comment 3 Guillaume Bibaut 2014-10-09 06:21:14 UTC
Also when I'm on the u-boot cli a 'usb start' tells me it didn't find ethernet device while the wifi switch is on. I'm now wondering sadly if it is not hardware related.
the 'usb tree' only shows a keyboard attached.
Comment 4 Ian Lepore freebsd_committer 2014-10-09 13:42:38 UTC
Given that other usb devices are working and only the wifi device is not, it does sound like it may be a problem with the device.  Can you try the device on another system?
Comment 5 Aleksandr Rybalko freebsd_committer 2014-10-10 06:49:58 UTC
hi yom@! (sorry, I don't know your name :) )

Can you, please, submit dmesg(1) output too?

Thanks!
Comment 6 Guillaume Bibaut 2014-10-10 17:18:05 UTC
(In reply to Ian Lepore from comment #4)
> Given that other usb devices are working and only the wifi device is not, it
> does sound like it may be a problem with the device.  Can you try the device
> on another system?

I'm going to try to install a downgraded version of 11-CURRENT in August when it was still working, not sure if it would be enough. What do you think about it ?
Comment 7 Guillaume Bibaut 2014-10-10 17:19:20 UTC
(In reply to Aleksandr Rybalko from comment #5)
> hi yom@! (sorry, I don't know your name :) )
> 
> Can you, please, submit dmesg(1) output too?
> 
> Thanks!

Hello :)
I'm attaching the dmesg.boot.
Comment 8 Guillaume Bibaut 2014-10-10 17:20:15 UTC
Created attachment 148174 [details]
dmesg.boot

this is the /var/run/dmesg.boot file on the Efika MX
Comment 9 Aleksandr Rybalko freebsd_committer 2014-10-11 19:38:12 UTC
Hi Guillaume!

so, looks like ehci core works fine, at least it attach t.pad and keyboard.
since it so, we have to find:
1. if wireless card is alive;
2. if GPIO pin give us required value.

To make test simple, you can try to test wireless card somewhere else.
For example: I use that card in my laptop.
Are you able to do that?

Ian, do we write some default values to pinmux? If so, it is bad idea. Not always possible to get all required information about board, but pinmux is not so simple to test it by hand and get things which is left.

Thanks!
Comment 10 Ian Lepore freebsd_committer 2014-10-11 20:44:29 UTC
The new pinmux driver is purely fdt data-driven.  If there are pinctrl-0 properties on enabled devices, then the pinmux driver configures the pins as directed by those properties, when the pinmux driver attaches.  None of our imx5 or imx6 dts files have any pinctrl-0 properties in them yet, so the driver is really doing nothing at all (which is what the old driver did, since nothing called its functions).
Comment 11 Aleksandr Rybalko freebsd_committer 2014-10-11 20:47:23 UTC
Aha, got it.

Thanks, Ian!
Comment 12 Guillaume Bibaut 2014-10-14 09:49:32 UTC
(In reply to Aleksandr Rybalko from comment #9)
> Hi Guillaume!
> 
> so, looks like ehci core works fine, at least it attach t.pad and keyboard.
> since it so, we have to find:
> 1. if wireless card is alive;
> 2. if GPIO pin give us required value.
> 
> To make test simple, you can try to test wireless card somewhere else.
> For example: I use that card in my laptop.
> Are you able to do that?
> 
> Ian, do we write some default values to pinmux? If so, it is bad idea. Not
> always possible to get all required information about board, but pinmux is
> not so simple to test it by hand and get things which is left.
> 
> Thanks!

I've been able to get the wireless card from the EfikaMX, I'll test it later today on a computer with PCIE slot.
Comment 13 Guillaume Bibaut 2014-10-14 19:58:31 UTC
(In reply to Guillaume Bibaut from comment #12)
> (In reply to Aleksandr Rybalko from comment #9)
> > Hi Guillaume!
> > 
> > so, looks like ehci core works fine, at least it attach t.pad and keyboard.
> > since it so, we have to find:
> > 1. if wireless card is alive;
> > 2. if GPIO pin give us required value.
> > 
> > To make test simple, you can try to test wireless card somewhere else.
> > For example: I use that card in my laptop.
> > Are you able to do that?
> > 
> > Ian, do we write some default values to pinmux? If so, it is bad idea. Not
> > always possible to get all required information about board, but pinmux is
> > not so simple to test it by hand and get things which is left.
> > 
> > Thanks!
> 
> I've been able to get the wireless card from the EfikaMX, I'll test it later
> today on a computer with PCIE slot.

I'm sorry but I can't test the wireless card on my other computer, I thought the slot was the same size but it is not.
I had an old laptop, but the wireless card in that laptop is not using the same slot configuration at all.
Comment 14 Aleksandr Rybalko freebsd_committer 2014-10-14 20:26:29 UTC
Ok, then you can try another method (maybe even easy one :) )
Try to prepare and boot from SD card with Genesi's Linux.

Thanks.
Comment 15 Guillaume Bibaut 2014-10-15 19:40:43 UTC
(In reply to Aleksandr Rybalko from comment #14)
> Ok, then you can try another method (maybe even easy one :) )
> Try to prepare and boot from SD card with Genesi's Linux.
> 
> Thanks.

I've tried to follow your advice, but it seems that the SD card won't load from the u-boot.imx I found there : http://people.freebsd.org/%7Eray/u-boot_efika_mx_smartbook.imx

when I type 'mmc rescan', it tells me :
esdhc_init: Card did not respond to voltage select!

I wanted to try that linux installation with the dd'd sd card : http://techuman.wordpress.com/2014/05/02/ubuntu-12-04-lts-now-running-on-efika-mx-smartbook/
Comment 16 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:45:19 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.