**** BEGIN LOGGING AT Mon Mar 04 02:59:57 2019 Mar 04 03:04:28 Just as I was about to test my battle bot for the faire, the dang motor connection came undone. Solder! Mar 04 03:05:08 BBBW, MotorCape, and a platform for busting bots. Mar 04 03:06:21 Only one, only one. Aw! Mar 04 03:07:09 I got a new pivot feature too. Yea. Mar 04 03:11:41 pivot = uncontrollable circling. Mar 04 14:50:15 rcn-ee: for info, I've finally setup this cyw4343 with brcmfmac. It too a lot of time to figure this out though :P Bacically, the firmware crashed due to incorrect 32kHz configuration. Mar 04 14:52:02 we haven't got 32kHz signal connected and this was enabled in nvram (boardflags3) Mar 04 14:52:32 Maybe this will help with your boards too: https://marc.info/?l=linux-wireless&m=155171085203797&w=2 Mar 04 14:55:17 today we learn, correct configuration helps with correct functioning ;) Mar 04 14:55:49 yeah, the problem is that there is no official documentation for boardflags3 available :-) Mar 04 14:55:57 that sounds great Mar 04 14:56:12 and you are either big player and contact cypress directly Mar 04 14:56:25 or you just spend a lot of time figuring this out Mar 04 14:56:30 this was my case :( Mar 04 14:56:57 ah it's originally a broadcom chip Mar 04 14:57:06 yep, that's right Mar 04 14:57:20 I mean, they usually have excellent documentation *cough* *cough* Mar 04 14:57:38 hehe Mar 04 14:59:26 actually the datasheet claims it should autodetect whether you use an external 32768 Hz crystal Mar 04 14:59:40 "Note: The CYW4343W will auto-detect the LPO clock. If it senses a clock on the EXT_SLEEP_CLK pin, it will use that clock. If it Mar 04 14:59:43 doesn't sense a clock, it will use its own internal LPO." Mar 04 15:00:08 was the boardflags3 thing overriding this? Mar 04 15:00:34 (or did you have EXT_SLEEP_CLK floating rather than grounded?) Mar 04 15:00:36 I don't think so, the firmware simply crashed and brcmfmac module didn't load Mar 04 15:01:07 it may be floating, yes Mar 04 15:01:26 "To use the internal LPO: Tie EXT_SLEEP_CLK to ground. Do not leave this pin floating." -- page 15 of the datasheet Mar 04 15:03:11 Possibly this is why it did't work, I'll try to ground this tomorrow and retry Mar 04 15:03:39 https://developer.electricimp.com/hardware/nvramimageguide Mar 04 15:03:40 :) Mar 04 15:04:02 I can't resolve you td-kros Mar 04 15:04:24 I should disable this dnssec things Mar 04 15:04:42 mawk: yes you should, dnssec is misdesign Mar 04 15:05:51 td-kros: ohh, so things are further complicated because you're actually using a module built around the cyw4343, and the nvram image is actually specific for those Mar 04 15:07:30 I think this should be general for all cyw4343, initially this flag was selected to 0x08000000, it started to work once I've change this to 0x04000000. Mar 04 15:08:41 be back later.. Mar 04 15:13:16 ah, you're right it does say the nvram image is for the embedded wifi core Mar 04 16:20:43 I have made an addition to librobotcontrol - Is there a guide to how to compile an ARM-version without doing it on the actual Beagle (cross compile)? Mar 04 16:22:30 qemu with an armhf perhaps? Mar 04 16:23:59 using qemu wouldn't be cross-compiling, it would be native-compiling in an emulator Mar 04 16:24:06 Yes Mar 04 16:24:36 I have arm-cross-compiler installed. any guide for how to use that? Mar 04 16:25:09 does it have any library dependencies? otherwise just using the cross-compiler (arm-linux-gnueabihf-gcc) instead of the native compiler probably suffices Mar 04 16:27:15 inside the "library" directory you can probably do: make CC=arm-linux-gnueabihf-gcc LINKER=arm-linux-gnueabihf-gcc all Mar 04 16:28:02 why not compile on the beaglebone? Mar 04 16:29:02 I am installing all the necessary packages to do so now - They were just readily available on my PC, so ... Mar 04 16:30:34 /18/18 Mar 04 16:30:36 /18 Mar 04 16:30:42 one of those days. Mar 04 16:31:00 * zmatt says hello to vagrantc's cat Mar 04 16:32:21 if only Mar 04 16:33:15 quite a few warnings/errors when running make package (lintian) Mar 04 16:33:45 zmatt, make command appeared to work :) Mar 05 00:52:24 I could not figure out why the bot would not work. Now, I remember. The MotorCape needs the BBBW to be plugged in via jack and not via USB. Mar 05 00:52:27 Aw! Mar 05 00:55:08 USB to jack on the way! **** ENDING LOGGING AT Tue Mar 05 02:59:57 2019