**** BEGIN LOGGING AT Sat Jan 12 02:59:57 2019 Jan 12 03:16:11 Hey GenTooMan: Is that the first book or the second one? Jan 12 03:16:30 I am asking b/c the first book is a lost cause on CC. Jan 12 03:16:42 Most ideas are out of date. Jan 12 03:18:26 I found eewiki from DigiKey. They have some good ideas. Jan 12 03:43:58 comments started 2014 so probably about 4 years ago edition Jan 12 04:30:25 Oh. I got that book but it is way outdated. Jan 12 04:30:43 It was outdated in 2015, i.e. the first time I tried to CC. Jan 12 04:31:50 There was a library the book writer used to CC for a toolchain. That toolchain was gone the following year. Jan 12 04:55:36 GenTooMan: I tried everything. If you are interested in what i am doing, pm me. I do not want to bash a ton of English up and down these screens in public, i.e. like I usually do. Jan 12 05:54:55 dreamhiker: \o/ Jan 12 05:56:05 set_: you're trying to compile a kernel for some random board right, not a beaglebone? Jan 12 05:56:33 or actually why are you even trying to compile a kernel? what is the end goal you're trying to achieve? Jan 12 05:59:49 zmatt: The damn board does not understand my commands. It does not turn on, it does not recognize my ssh requests, and the damn thing is beat for now. It came this way. Jan 12 06:00:15 which board? Jan 12 06:00:32 I know it is not BBB related but I thought since CC is a thing, we could discuss it. Jan 12 06:00:39 PICO-PI-IMX7 Jan 12 06:01:17 cross-compiling a kernel for the beaglebone is trivial Jan 12 06:01:26 Oh. Jan 12 06:01:30 rcn made convenient scripts for it Jan 12 06:01:47 but I very very much doubt you need to compile a kernel to get a board working Jan 12 06:02:18 I figured since the eewiki has info. on BBB stuff, I could use what I learned on this other board. Jan 12 06:02:21 you're not the only person on the planet with that board presumably, I have trouble believing there are no working images Jan 12 06:02:53 I compiled the kernel and used an already made/minified version of Debian for the board. Jan 12 06:03:35 I came out w/ a new vision. CC is not all bits and bangs. Jan 12 06:03:51 Would you like to see the instructions? Jan 12 06:03:54 sure Jan 12 06:03:56 Yea! Jan 12 06:04:35 https://www.digikey.com/eewiki/display/linuxonarm/PICO-PI-IMX7 is the instructions for this particular board w/ the ARM Cortex-A7 and M4. Jan 12 06:05:12 I looked online at the Wandboard people. I think they hate me. I moved on. Jan 12 06:06:11 I got all the instructions completed. I cannot ssh into the board, yet. Jan 12 06:06:20 ... Jan 12 06:07:33 Oh and sir, how do you think my config file should look from: https://www.digikey.com/eewiki/display/linuxonarm/PICO-PI-IMX7#PICO-PI-IMX7-Setupextlinux.conf? Jan 12 06:09:32 I ask b/c the kernel is 4.20.x. Should I have .zImage after any of my options in the .conf file? Jan 12 06:09:55 is this thing ultranew or something? Jan 12 06:10:20 I have no clue. I think it may be but they have imx8 already. Jan 12 06:10:29 This is an imx7. Jan 12 06:10:37 I mean the board Jan 12 06:10:47 And that Android Things crap is just that, crap. Jan 12 06:10:55 To me, yea. Jan 12 06:11:07 so why did you get a board that is specifically advertised for android? Jan 12 06:11:12 In relation to time, I am not sure. Jan 12 06:11:37 B/c...I read about putting Linux on it w/ Ubuntu, Yocto Project, and Debian. Jan 12 06:11:45 hm, it doesn't seem to be new Jan 12 06:11:46 I wanted to try new ideas. Jan 12 06:12:23 Get this zmatt: There are two options only for each question to set up the board w/ Android Things. Neither of the two options worked. Jan 12 06:12:26 Blah! Jan 12 06:13:02 1. is for this. 2. is for that. Jan 12 06:13:13 1. and 2. did not work. There was no way to set up the board. Jan 12 06:13:43 I should have stuck w/ CC w/ the BBB and related boards. Jan 12 06:14:13 https://www.technexion.com/support/download-center/?wpv-product=pico-imx7-emmc this seems to have a prebuilt ubuntu sd card image at least Jan 12 06:14:31 This board did not come w/ an SD Card slot. Jan 12 06:14:43 what? Jan 12 06:14:47 Serious! Jan 12 06:14:50 No port for SD. Jan 12 06:14:59 euh Jan 12 06:15:01 hum Jan 12 06:15:18 So, I am CC'ing trying to do anything to get an image on this board. Jan 12 06:15:57 how would that help? Jan 12 06:16:22 I can use u-boot to put an image on the board after compiling a kernel that is supposedly working. Jan 12 06:16:40 I'm still in the "what?" phase though, why would there be sd card downloads for this board if it has no sd slot? rcn's instructions are also for preparing an sd card Jan 12 06:16:54 I'm looking at the hardware manual right now Jan 12 06:16:59 I know. Jan 12 06:17:27 Hey. I am fooled too. This bunch of engineers said SD compatability but there is none. Jan 12 06:18:06 Now, this person that has volunteered to help, is taking my backward talks while we both try to figure out how to put an image on the board. Jan 12 06:18:06 this is so weird Jan 12 06:18:30 I thought it would be under the add on to the board. But, nope! Jan 12 06:19:22 I went to them to ask for guidance. They said, "Tech Nexion" made the board. Talk to them. Jan 12 06:19:38 Their forum has been crapped on by everyone in the world. SPammers. Jan 12 06:20:42 Oh and zmatt: The instructions can be made to work w/out SD Card. I am pretty sure that is what rcn stated. Jan 12 06:21:27 There are like 50 nonsensical chats in a log somewhere online for DigiKey.com Tech Forum. Jan 12 06:21:28 ... Jan 12 06:21:40 I have been unable to make it work so far. Jan 12 06:24:14 you know... maybe you should have bought a different board, lol XD Jan 12 06:25:24 like, the board's boot options are eMMC or serial Jan 12 06:25:26 fuck that Jan 12 06:25:59 that's just awful, no wonder you have trouble with this board Jan 12 06:27:28 Yep. Jan 12 06:27:36 Now, I know. Jan 12 06:28:03 writing to eMMC via serial is not easy. Jan 12 06:28:23 It is damn near impossible from what I can tell. Jan 12 06:28:59 yeah, sorry but consider abandoning this thing Jan 12 06:29:18 how did you even end up with this thing? Jan 12 06:29:34 The USB OTG -C is used for power. Then, there is a serial port via USB. Jan 12 06:30:17 I did some research and thought, yea, nice. New ideas from Android! Then, I had to face it. I/O and visions from Android are not that great. Jan 12 06:30:28 Java! Jan 12 06:30:30 Blah. Jan 12 06:31:22 I wonder if I can boot that board via USB. Jan 12 06:31:39 I have put other OS on hardware via USB. Jan 12 06:33:31 Sorry. USB Drive. Jan 12 06:42:42 the hardware manual does not indicate any other boot methods Jan 12 06:43:35 hmm wait Jan 12 06:43:55 I am reading the SRM again. Jan 12 06:47:11 p. 1122 shows different ways the chip can boot. Jan 12 06:47:35 the srm? of the imx7 SoC you mean? Jan 12 06:49:06 Yes. Jan 12 06:50:06 the SoC supporting something does not imply the board does Jan 12 06:53:31 6.6.2.4. of the SRM states something interesting. Something about the arm core expiring and Watchdog timers are listed. Jan 12 06:53:56 I will look at the board set up again. Jan 12 06:53:57 where did you find the imx7 processor reference manual? it doesn't seem to be freely downloadable Jan 12 06:54:08 or, whatever you're reading Jan 12 06:54:12 Please hold. I will find it again. Jan 12 06:54:21 NXP, probably. Jan 12 06:54:31 or Tech Nexion. Jan 12 06:55:48 Taiwan! Jan 12 06:56:08 oh lol you can bypass the whole login stuff at nxp, the direct download link works fine Jan 12 06:56:37 Ha. Jan 12 06:56:56 https://www.technexion.com/search/PICO-PI-IMX7/ Jan 12 06:57:10 They are all outdated. Jan 12 06:57:23 2015 and 2017 stuff is all they have, I am pretty sure. Jan 12 06:59:55 https://www.technexion.com/support/knowledgebase/loading-bootable-software-images-onto-the-emmc-of-picosom-on-pico-pi/ is some ideas. Jan 12 07:01:39 so what is your goal with this board? what particular feature are you interested in to be worth investing this much effort? Jan 12 07:02:06 Fun! Jan 12 07:02:26 And yes, I am being serious. Jan 12 07:03:01 okay, so technexion has tools and instructions for loading an image onto the eMMC Jan 12 07:03:07 and they have prefab ubuntu images Jan 12 07:03:12 sounds like all the ingredients you need Jan 12 07:03:30 Some people can make a living dealing in this field. Me, on the other hand (as you know), does life as a choice and for fun. Since electronics were around, I will promote them for fun and in life. Jan 12 07:03:31 ... Jan 12 07:04:04 I will try it out. I am going to let rcn know about the site and instruction set in case he/she needs help. Jan 12 07:04:19 Is rcn male? Jan 12 07:04:34 Either way, it does not matter. Jan 12 07:04:47 or just leave him be, he has plenty of stuff on his mind no doubt Jan 12 07:04:52 yes, robert c nelson Jan 12 07:05:04 I know. Robert is a male name. Jan 12 07:05:14 anyway, I've got stuff to do Jan 12 07:05:16 I was thinking of how much stuff he actually does. Jan 12 07:05:25 Oh. Okay. Later for now and thank you. Jan 12 07:52:05 HI... I have issue with BBB serial output... I cannot see anz serial output when I use 5v DC 3.5A power supply Jan 12 07:52:18 With USB supply.. I have no issue Jan 12 08:00:22 heh, wonder if that's a missing ground connection :) Jan 12 08:00:33 he might never find out Jan 12 08:04:16 oh lol, good catch Jan 12 18:40:04 I have a lot of warnings when I compile the output of your tool (but also had some of them when writing the overlays by hand), is that expected zmatt ? Jan 12 18:40:26 the only serious warning seems to be this: mrf24j40.dtbo: Warning (reg_format): "reg" property in /fragment@2/__overlay__/mrf24j40@0 has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1) Jan 12 18:42:53 so I added back the address-cells thing Jan 12 18:43:19 with an overrided value of just 1 address cell (I guess it's the chip select line) and 0 size cells (it's single bit data line SPI) Jan 12 18:50:02 just suppress the warning, dtc is wrong Jan 12 18:50:20 and no your interpretation of those properties is incorrect Jan 12 18:51:04 I see Jan 12 18:51:05 thanks Jan 12 18:51:13 basically, since an overlay is not a proper DT but merely fragments of DT in a container format, dtc cannot actually perform the sanity checks it's trying to do Jan 12 18:51:34 yeah Jan 12 18:51:50 that's one reason I don't use overlays myself ;) Jan 12 18:51:58 but I was still doing stuff, afk Jan 12 19:02:34 I used this for the pinctrl for a GPIO that should be used as falling edge interrupt: PIN_GPIO_PULLUP(P9_23) Jan 12 19:20:29 yeah that's fine for an input. if you know for sure the pin is externally driven (push-pull, or open-drain with external pull-up) then you might also use PIN_GPIO_NOPULL Jan 12 19:20:47 but it doesn't really matter Jan 12 19:21:21 I generally leave pull-up/down enabled unless I have a really good reason to disable them.. they Jan 12 19:21:55 they're very weak anyway (100 kΩ ±50%) and basically just meant to prevent inputs from floating Jan 12 19:30:57 well it's an interrupt line, I wouldn't want spurious interrupts Jan 12 19:31:01 even though it can't hurt I guess Jan 12 19:31:15 it's not as bad as spurious wakeups if saving power Jan 12 19:31:42 I'm taking example from your example .dtsi, it's quite nice Jan 12 19:31:59 the thing that's not nice is waiting 2 minutes for the bbb to connect to ethernet Jan 12 19:32:19 I ^P^M in my shell until I can connect Jan 12 19:33:07 looks like I wrote a nice overlay, the only problem now is that there's already an overlay for the SPI thing I'm using, presumably in universal-cape (?) Jan 12 19:33:15 so it's talking about conflicts in pinmux Jan 12 19:33:50 I guess I have to use &ocp { P9_28_pinmux { status = "disabled"; }; }; for every single pin I'm using ? Jan 12 19:35:16 let's try it, I have two minutes to spare Jan 12 19:38:08 welllll... you might want to just disable the universal overlay first, see if that works Jan 12 19:38:17 and then analyze if there are more conflicts Jan 12 19:39:07 pins aren't the only thing where conflicts can arise, you also both use the spi peripheral Jan 12 19:39:14 and both use a gpio Jan 12 19:39:24 I was afraid of disabling the universal overlay, my system is on eMMC Jan 12 19:39:31 not on sd card Jan 12 19:39:36 universal overlay isn't responsible for eMMC Jan 12 19:39:39 yeah I know Jan 12 19:39:45 but if things go wrong I'll have a hard time re-enabling it back Jan 12 19:40:06 so, formerly the universal overlay actually got automatically disabled if a cape or custom overlay was enabled Jan 12 19:40:15 ah Jan 12 19:40:26 well for conflicts I used the "exclusive-use" directive but it wasn't enough Jan 12 19:40:29 because the universal overlay basically conflicts with everything Jan 12 19:40:32 it needed the ocp thing Jan 12 19:40:35 I see Jan 12 19:40:40 exclusive-use is metadata that's ignored by u-boot Jan 12 19:40:44 ah Jan 12 19:40:45 shame Jan 12 19:40:54 the comments said it was ignored by the sysfs, I didn't know for uboot Jan 12 19:41:09 yeah ditto Jan 12 19:41:51 I see people on forum modifying the universal-cape, is that a good idea ? Jan 12 19:41:57 or just disabling it altogether can't harm Jan 12 19:42:03 so, as for the risk of not booting.. that's a thing in general when messing with overlays since u-boot just rudely fails to boot if it finds any issue with any overlay Jan 12 19:42:10 but recovery is very easy Jan 12 19:42:41 as long as you have a bootable sd card around Jan 12 19:42:47 or a serial console cable Jan 12 19:43:30 the former is easier: boot from sd card, mount emmc, fix its /boot/uEnv.txt, unmount emmc, poweroff Jan 12 19:45:48 so, the idea behind those P9_28_pinmux { status = "disabled"; }; thingies is that they disable the universal overlay's pinmux helpers for pins that your overlay uses, which would otherwise conflict Jan 12 19:45:57 ah Jan 12 19:46:02 I see Jan 12 19:46:09 thus hopefully being able to still use config-pin on the remaining pins Jan 12 19:46:11 ok I have a network connection between my two devices, great Jan 12 19:46:16 yeah Jan 12 19:46:31 the connection isn't especially reliable Jan 12 19:46:36 well it reliably borks the data Jan 12 19:46:54 poor signal integrity? try lower spi clock frequency? Jan 12 19:47:22 it's already pretty low Jan 12 19:47:28 I thought it was the opposite, too low frequency Jan 12 19:47:32 I'll try that anyway Jan 12 19:47:42 also it's on 2.4GHz channel 11 which is crowded, but that can't mess the data Jan 12 19:47:44 there is a checksum Jan 12 19:47:51 btw, earlier you mentioned spurious interrupts... pin conf should not be able to cause those one way or another, the only thing you can do wrong is disable the receiver (PIN_GPOUT) in which case you'll get no interrupt whatsoever Jan 12 19:48:08 well it was in level interrupt mode Jan 12 19:48:16 so it was interrupting over and over Jan 12 19:48:17 that's not in the pinconf though Jan 12 19:48:22 that's in your interrupt declaration Jan 12 19:48:23 yeah Jan 12 19:48:29 I figured that out later Jan 12 19:48:52 so, what does your connection look like exactly? physically I mean Jan 12 19:49:42 actually I should probably do shopping first Jan 12 19:50:34 between the bbb and the module ? I soldered the module (which has castellated vias) to a piece of prototype board, soldered pin headers, then used dupont female-female cables to link that to the bbb Jan 12 19:51:39 ok yeah no the UDP data isn't messed up with Jan 12 19:51:47 and since 6LoWPAN is only udp it makes sense Jan 12 19:52:02 I don't know how pings are handled in the protocol Jan 12 19:52:05 but ok, it works ! Jan 12 19:52:09 thanks for the help zmatt Jan 12 19:52:20 now the goal is to sanitize this device tree, and learn the proper syntaxes Jan 13 01:55:13 Compiling is on the rise among youths. Jan 13 01:55:50 is that those under 30 (hippie youths of the 2000's)? Jan 13 01:56:02 Yep. Jan 13 01:56:17 Long hair, shaggy carpet, and vans. Jan 13 01:57:08 GenTooMan: You are not going to believe my fault today, yesterday, and the day before. Jan 13 01:57:47 I had the board I was targeting in compilation 180 degrees in the wrong direction. The jumper pins almost did not forgive me. Jan 13 01:58:04 I feel better already. Jan 13 01:58:25 set_ having experienced my own hilarious faults, I probably will. oh yeah that stupid happens. Hence the saying measure twice cut once. Jan 13 01:58:43 Right, right. Everyone keeps telling me that. Jan 13 01:58:55 "Measure once, cut twice!" Jan 13 01:59:15 set_ well yeah if you cut twice you'll need more material (AKA BBB) Jan 13 01:59:41 More BBBs of the plenty. To tell you the truth, I cannot believe how long my BBBs have lasted. Jan 13 01:59:51 No sales pitch. Jan 13 02:00:00 I still have the rev. Bxx. Jan 13 02:00:22 2 GB and the SD Card on it works fine. Jan 13 02:00:31 I probably should start actually using mine. I have 3 rev B's an original Beagle bone too. Jan 13 02:00:47 Y'all might want to outsource for cheaper parts. Jan 13 02:00:52 Just kidding. Jan 13 02:01:39 GenTooMan: I have been trying to pair this receiver (R/C) w/ a transmitter and all while attached to the BBB. Jan 13 02:02:01 R/C is not easy. As soon as microcontrollers are involved, things change. Jan 13 02:02:49 Now, 12 pin chips is not what I am discussing. Complex boards w/ do-dats and thing-a-ma-giggies is making it difficult for the R/C person. Jan 13 02:03:27 <<<< not a R/C person but aspiring Jan 13 02:04:21 I still cannot make my BBB take flight. I tried ArduPilot, DroneKit, and I think I will use my own ideas as soon as I pair this receiver and transmitter. Jan 13 02:04:51 One button! It is supposed to pair w/ one button. And guess what? Jan 13 02:05:16 That is right. No pairing. Jan 13 02:05:19 Aw! Jan 13 02:05:36 dang. did I do that. brb Jan 13 02:15:45 So a-pair-ently ... Jan 13 02:33:29 Zoinks. Jan 13 02:33:56 GenTooMan: Say this happens... Jan 13 02:33:59 Okay so... Jan 13 02:34:46 I compile, add the Debian image from rcn to the board, and then I have to exit u-boot to finish. Jan 13 02:35:09 I exit u-boot by control-c and then reset. Jan 13 02:35:14 But... Jan 13 02:35:32 Here is the kicker. u-boot comes back up and I have only three seconds to make a decision. Jan 13 02:35:40 I pushed the button. Jan 13 02:35:56 Now! My board is gone from the desktop and I am back in the u-boot cli. Jan 13 02:36:13 What would you have done? Jan 13 02:43:56 I was reading up on u-boot. I could not find out their way of exiting the cli. Jan 13 02:49:34 set_ not the proverbial "exit"? method? Jan 13 02:50:20 I do not think so. I thought of everything. I pulled up the list of commands and everything. Jan 13 02:51:08 ... Jan 13 02:51:33 set_ no reboot now command? Jan 13 02:51:39 Nope. Jan 13 02:51:53 set_ no give up hope because we got you again command? Jan 13 02:52:02 Nope. Jan 13 02:52:11 Not a one. Jan 13 02:52:18 you would think they would have that at least Jan 13 02:52:48 I would but I could not implement it. So, I have to stay quiet at Tim's house. Jan 13 02:53:20 GenTooMan: What are you doing? Jan 13 02:54:15 Aces high? **** ENDING LOGGING AT Sun Jan 13 02:59:57 2019