Yeap, i’ve got an antenna installed.
Regards,
Hello Sir,
See here: https://wikidevi.com/wiki/AMPAK. My device is listed as early as kernel 3.10+. I think I will try 4335 instead of 4339. Would this even make sense? What if I try to add the files as UART instead of SDIO?
…
I have not received WiFi access yet.
Where did you find that info. about the need for brcmfmac4339-sdio.txt and .bin or whatever in the /lib/firmware/brcm/ dir?
Seth
P.S. I apologize for this headache. I am out of ideas. That is all. I see the schematic states AP6212 is the chip for WIFI/BT but I have a AP6335. Do you think this would make a difference? Page 16 on this .pdf shows the pins of the chip (supposedly): http://www.t-firefly.com/download/firefly-rk3288/hardware/AP6335%20datasheet_V1.3_02102014.pdf. If that site is risky on your end, I will find another site. I do not even think that this chip is a broadcom chip at all.
Okay Sir,
@RobertCNelson: As far as I can tell, ARM chips on the Linux side is not supportive of this WiFi/BT chip (AP6335). I am pretty sure.
…
I just ran through some of the /arch/arm/ directories to look around to find if ARM supports these WiFi chips on github under torvalds/linux.
Seth
P.S. The Taiwan side of things states that prior to 2015, Broadcom was owned by Broadcom but that they were bought out by some co. and renamed Broadcom Ltd. Anyway…I might have to go to the ARM community to find answers. I will keep you updated. Do you think I should have installed rfkill at all?
Sir,
I do not have modprobe installed on my machine or I just do not know how to utilize it yet. Either way, I found this idea: https://wiki.debian.org/brcm80211#supported.
I was probably wrong or I need to type up my own driver. I see that thing are supported or not supported on different pages online. It is hard to guess. I will keep testing.
Oh and sir, if you know how I can get modprobe on this machine, please reply. I will try to look this up in time.
Seth
P.S. I also found some interesting info. about older models of the software that may still be on the computer (debian@arm)/PICO-PI. Noted here, I have many different variations of software for other chips available on my machine. Do you think I should erase them? Then, I could try just “barebones” and start from scratch w/ what is listed —> AP6335 = brcmfmac = BCM4335/BCM4339. What do you think?
Sir,
I am up to my old tricks again. Here, https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware.git, is where I figured I could get some firmware for Linux.
I know I may have typed out a lot so far. Please, if you can find time, read the info. and try to reply to any of it. I would kindly appreciate it.
Seth
P.S. I might need to run the CC of the kernel again if I get this info. cloned. I have not found another option. I found the packages.debian.org site and I see you already made the firmware available to this board for brcmfmac .bin files and .pci files.
Hello Sir,
@RobertCNelson…did you ever get any info. back from the Wandboard People? I contacted them. They huffed and puffed and blew me away. I think they are not particularly nice about the users in their community online (forums and/or their website).
…
Anyway, I have been unsuccessful so far (still).
Seth
P.S. If anything works ever, I will contact you again. If things are driving me batty again, I will reply again.
@RobertCNelson
@silver2row
Hii, I stay 1 week trying this tutorial
My issue is in t the command ums 0 mmc 0
ums 0 mmc 0
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
=> usb start
starting USB…
USB0: Port not available.
USB1: MXC USB port 1 not yet supported
lowlevel init failed
=> mmc rescan
MMC: no card present
mmc_init: -123, time 2
=> mmc list
FSL_SDHC: 0
FSL_SDHC: 1 (eMMC)
=> mmc info
MMC: no card present
mmc_init: -123, time 2
It looks like your version of u-boot you’ve installed can’t read the eMMC…
I would bug the author of that tutorial or use the one we provide:
Regards,
@RobertCNelson tks
I solve ums 0 mmc 0 . At least I think I solved:
https://drive.google.com/file/
I solved issue because I followed your tutorial so far to flash the image. At this point I used the command: sudo dd if = core-image-base-imx7d-pico.sdimg of = / dev / sdd bs = 1M; sudo sync
I can see my board in ls /dev/tty.* but I can’t access (my yocto device 2.6 – thud) using picocom or minicom
I put EXTRA_IMAGE_FEATURES_append = " package-management " because I need
opkg
What about this command mmc partconf 0 0 7 0? do i need this?
What about openCV and python3? I need very much these 3 components. What about Ubuntu?
My board (imx7d-pico kit) don’t have microSd card input.
We need that for mainline u-boot
in debian that’s
sudo apt install python3 python3-opencv libopencv-dev
Right here: https://www.digikey.com/eewiki/display/linuxonarm/PICO-PI-IMX7#PICO-PI-IMX7-Ubuntu18.04LTS
None of the imx6d-pico kit’s have a microsd card, that’s why the directions on https://www.digikey.com/eewiki/display/linuxonarm/PICO-PI-IMX7 are so confluted, as you need u-boot to share the eMMC as a usb flash device.
Regards,
@RobertCNelson Pls. what abiut my problem? after I flash mender yocto 2.6 thud image? (I see in ls, but I can’t access yocto using picocom or minicom (using every options of these consoles).
How to I can flash your debian 9 or your ubuntu 18 in my imx7-pico? (I only have eMMC to this)
Sounds like you should ask the developers behind Mender…
Well start here: https://www.digikey.com/eewiki/display/linuxonarm/PICO-PI-IMX7 and work your way down every step on the page… (just choose ubuntu over debian for your rootfs)
Regards,
@RobertCNelson My imx7d pico android things start kit died
https://community.nxp.com/message/1214690
Pls help me
@neuberfran, please check your jumpers, I’ve never used NXP’s MFG tool, but you can double check if the board is in the correct mode in linux by running this lsusb command:
lsusb | grep Freescale
Bus 00x Device 00y: ID 15a2:0076 Freescale Semiconductor, Inc
If it responds with that usb vid/pid id, then it’s in usb boot rom mode…
Regards,
I think that is not the problem. Should be. I think it’s more serious. You have to pass the multimeter, I think. Could you give me tips on passing the multimeter. I inform you that I never touched these low jumpers, the ones that are furthest from the GPios.
@neuberfran, so you have the jumpers exactly the way shown on;
However if you scroll down to the schematic area, it shows this conflicting data:
Which is the way i show it on my wiki page:
Which works for me.
Regards,
@RobertCNelson I had already tried various settings on the jumpers that are closest to the gpios and never solved.? What should I try with the multimeter?
