| 06:07 | Jessykinha | hi |
| 14:32 | topi` | jnettlet: I managed to create a souped-up cable usbA <-> usbA with D+ and D- crossed. I have an older HB Pro here to test it with, is there any LED that should lit up if I connect a +5V power source to that USB-OTG port? |
| 14:33 | topi` | or any other means to actually verify that the cable works and is able to provide sufficient amperage for the usb-otg flashing/efusing process? |
| 15:31 | jnettlet | topi`, you need to power the target board separately that is why you need the resistor. If it works, lsusb on the host will show freescale device in recovery mode. |
| 15:47 | topi` | I looked at the "older" document, and it says green and white cables should be connected to each other as-is, and not crossed like I did |
| 15:47 | topi` | I guess I'll redo the cabling :) |
| 15:47 | topi` | my soldering iron was so shitty that I decided to do shrink-tubing instead |
| 17:02 | jnettlet | I am working on a hardware developer platform to make this much easier. Finally found a decent chip to use. |
| 18:51 | topi` | what's the best way to identify whether the HB SOM has broadcom or wilink8 chip? "lsusb" won't work... |
| 18:51 | topi` | does wilink8 connect via SDHC? |
| 18:53 | topi` | I guess there is no such thing as a "lssdio";) |
| 19:00 | topi` | I see the sdhcs in the /sys/firmware/devicetree but it's nearly impossible to know which is a SD card and which is a SDIO device like wifi chip |
| 19:09 | jnettlet | topi`, wilink8 has a big silver chip on it next to the antenna, the BCM variants are black chips. |
| 19:10 | jnettlet | topi`, but modern u-boots will detect them properly and add a -som-15 suffix to the dtb name. |
| 19:10 | topi` | ok, interesting |
| 19:11 | topi` | I just want to be able to handle both v1.5 soms and the newer ones :) I want to give them custom hostapd flags |
| 19:11 | topi` | I think the Wilink8 can handle advanced 802.11n flags like RX-STBC1, SHORT-GI-20 etc |
| 19:11 | jnettlet | topi`, yes it can |
| 19:11 | jnettlet | for detection....let me think about it. You should be able to read the device-tree properties. |
| 19:12 | jnettlet | but you will need additional patches for upstream. |
| 19:12 | topi` | does UBOOT pass the kernel which .dtb it used? |
| 21:22 | Artox | topi`: the product name is available somewhere in /sys |
| 21:23 | Artox | err proc /proc/device-tree/model |
| 21:24 | Artox | but I have a feeling that string doesn't tell you about the SoM |
| 21:24 | Artox | it could, but apparently it doesn't |
| 21:25 | Artox | hah, I know |
| 21:26 | Artox | https://github.com/mxOBS/deb-pkg_cuboxi-firmware-wireless/blob/master/debian/cuboxi-firmware-wireless-bluetooth.brcm_patchram_plus.init |
| 21:26 | Artox | there should be a vendor id available too somewhere |
| 21:27 | Artox | ; /sys/bus/sdio/devices/mmc1\:0001\:2/vendor and /sys/bus/sdio/devices/mmc1\:0001\:2/device |
| 21:28 | Artox | or perhaps better yet: /sys/class/net/wlan0/device/{vendor,device} |