**** BEGIN LOGGING AT Tue Jan 11 02:59:56 2022 Jan 11 06:58:08 Anyone know where to source Pocketbeagles? I'm from Canada and all distributors are out of stock. Is it possible to source PocketsBeagles directly from manufacturers in larger quantities (~100)? Jan 11 17:10:27 Anyone familiar with the Beaglebone Blue board? Jan 11 17:10:28 Particularly, using the RoboticsCape/LibRobotControl library. Jan 11 17:10:28 I'm trying to use the board's DMP (Digital Motion Processor), but upon calling rc_mpu_initialize_dmp() I get an error saying "ERROR: opening gpiochip: No such file or directory" Jan 11 17:12:07 hmm Jan 11 17:12:57 It also happens when I use the rc_test_dmp program that's included Jan 11 17:14:49 lol, looks like the gpio code in librobotcontrol is broken on kernel 4.19 Jan 11 17:15:07 that's what people get for hardcoding dynamically assigned numbers I guess Jan 11 17:17:21 oh never mind Jan 11 17:17:42 ? Jan 11 17:17:56 I was looking at /sys/class/gpiochip numbering, not the /dev/gpiochip numbering, which actually differs Jan 11 17:18:03 (obnoxiously) Jan 11 17:18:10 then I'm not sure Jan 11 17:19:48 I mean, it's still a bad idea to hardcode /dev/gpiochip numbers which are presumably still dynamically assigned, but in practice I'd expect gpiochip0..3 to all exist and correspond to the gpio0..3 controllers Jan 11 17:20:18 i dont even have a sys/class/gpiochip directory, or a /dev/gpiochip Jan 11 17:20:25 uhh Jan 11 17:20:39 those aren't directories but prefixes Jan 11 17:20:50 as in, /dev/gpiochip0 Jan 11 17:21:21 I see it gets the gpiochip number from the rc_mpu_config_t argument to rc_mpu_initialize_dmp() Jan 11 17:21:44 but rc_mpu_default_config() should fill that in correctly Jan 11 17:22:08 or rc_mpu_set_config_to_default() Jan 11 17:22:53 specifically it should set it to 3, i.e. it would be looking for /dev/gpiochip3 Jan 11 17:23:18 My gpiochip0 (and 32, 64, 96, etc) are all under the /sys/class/gpio/ directory, could that be an issue? since on yours, is under /sys/class/ Jan 11 17:23:24 i dont see a gpiochip3 here on mines Jan 11 17:23:37 it's /sys/class/gpio/ yes, sorry Jan 11 17:24:02 what kernel version are you running (uname -r) ? and what image version? (cat /etc/dogtag) Jan 11 17:24:36 4.4.59-ti-r96 Jan 11 17:24:47 that's reaaaly ancient Jan 11 17:25:14 so that's almost certainly your issue Jan 11 17:25:27 try reflashing with a recent image Jan 11 17:26:30 download the "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" image from the "Flasher Debian images" section of https://beagleboard.org/latest-images Jan 11 17:27:09 flash to microsd card using https://www.balena.io/etcher/ Jan 11 17:27:33 Okay Jan 11 17:27:35 and boot the beaglebone from that sd card. it should automatically erase and reflash the on-board eMMC Jan 11 17:27:59 I'll try that Jan 11 17:28:03 and see if it works Jan 11 17:28:07 Thankyou! Jan 11 17:28:20 since your current system is really ancient it's possible you may need to force SD boot by holding down the boot button while applying power (you can let go once the power led turns on) Jan 11 17:30:00 the "SD" button I mean Jan 11 17:30:38 I should probably backup my code files on the system before doing this too, I assume? Jan 11 17:30:52 yes, backup anything you don't want to lose Jan 11 17:31:58 kk Jan 11 18:55:14 zmatt how do I confirm that the beaglebone is being flashed? I held down the "SD" button on the corner of the board while I plugged it in/applied power. and i saw 4 LEDs at the start. then those went off, and there's just been 2 LEDs flashing back and forth really fast, ever since then. but it's been well over 60 minutes now Jan 11 18:59:04 Black_Ice_80, are the LEDS' doing a cylon pattern? board will shut down when done.. Jan 11 19:00:08 rcn-ee not sure what a cyclone pattern looks like. But there's 2 LEDs flashing one at a time Jan 11 19:00:33 Black_Ice_80, https://www.youtube.com/watch?v=7HN8879HGNI Jan 11 19:00:53 if just 2, it's not a the flasher.. Jan 11 19:01:11 I guess its not flashing then :/ thats not happening Jan 11 19:01:27 Black_Ice_80, what file did you flash to your microSD? Jan 11 19:01:45 (actual file name) Jan 11 19:04:11 bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz Jan 11 19:04:33 Black_Ice_80, well that's not the flasher... so login into running board ;) Jan 11 19:07:00 ooh i had the wrong file Jan 11 19:07:01 thankyou Jan 11 19:49:29 zmatt updating fixed the issue :D Jan 11 21:04:43 zmatt: are you using BBs in D&D speakers? Jan 11 21:14:20 Black_Ice_80: nice! Jan 11 21:15:11 Black_Ice_80: I did explicitly mention to get the flasher! from the flasher images section! Jan 11 21:16:10 yeah, that was a mistake on my part. once i got the flasher, everything worked out! Jan 11 21:17:49 hnv: BBBs yes, we started on an osd335x-based design but other stuff has had priority Jan 11 21:19:45 The osd sip in a custom pcb? Jan 11 21:20:26 yeah Jan 11 21:21:55 but there hasn't really been much time to work on that, and the BBB-based board works fine so there also hasn't been a ton of motivation **** ENDING LOGGING AT Wed Jan 12 02:59:57 2022