**** BEGIN LOGGING AT Fri Nov 29 02:59:58 2019 Nov 29 03:36:09 are you sure it got applied? Nov 29 03:36:46 if you compiled it with latest overlay-utils then it should be listed in /proc/device-tree/chosen/overlays (just like recent bb.org-overlays do) Nov 29 03:38:12 also the compatible-string should be prefixed with "adi,": https://github.com/RobertCNelson/linux-stable-rcn-ee/blob/master/drivers/staging/iio/adc/ad7192.c#L923-L926 Nov 29 03:40:28 another issue is that this overlay won't be compatible with cape-universal, so you either need to disable cape-universal or fix compatibility by renaming your spi device node to spi0channel@0 => https://github.com/mvduin/overlay-utils/blob/master/spi0.dtsi#L46-L47 Nov 29 03:41:15 why the ti,no-idle ? Nov 29 03:43:02 I can't remember why. I will try renaming the spi device. btw, dmesg says: "ad7192 spi1.0: noplataform data?" Nov 29 03:43:31 ehh Nov 29 03:44:31 which kernel are you using? Nov 29 03:44:50 (full uname -r) Nov 29 03:45:17 4.14.49-ti-r54 Nov 29 03:45:48 there's normally only one reason for using ti,no-idle and that's when the device is being used by PRU, but in that case it should have status="disabled" to ensure no kernel driver will attach to it Nov 29 03:46:43 the driver you're trying to use didn't support DT configuration yet in that kernel version: https://github.com/RobertCNelson/linux-stable-rcn-ee/blob/4.14.49-ti-r54/drivers/staging/iio/adc/ad7192.c Nov 29 03:48:06 I was blindly assuming that lol Nov 29 03:50:15 well, not blindly, just seeing master, not 4.14.49 in github Nov 29 03:51:29 yeah github for some reason has issues with this repo, although you can find the releases under https://github.com/RobertCNelson/linux-stable-rcn-ee/releases Nov 29 03:51:55 but if you already know the release, easiest is to just fill the release directly into the url Nov 29 03:53:26 interesting that the tags are shown on https://github.com/RobertCNelson/linux-stable-rcn-ee/tags but not in the branch selection popup Nov 29 06:54:09 Hi Friends suddenly my beaglebone OS is crashed . I don't know what it is happened. please help to me Nov 29 06:54:37 that's really not enough information for anyone to possibly be able to help you Nov 29 06:56:16 when i was trying to sending the files using winscp suddenly my friend is blocked the internet after that OS is crashed Nov 29 06:57:03 when i was trying to sending the files using winscp suddenly my friend is blocked the IP address after that OS is crashed Nov 29 06:57:12 yes you just said that Nov 29 06:57:49 not internet he has blocked the IP address Nov 29 06:58:12 is there any solution recover the erased epprom data Nov 29 06:58:42 the only reason I can think that could cause problems by transferring files to the beaglebone would be running out of disk space, but that still shouldn't crash the system Nov 29 06:58:49 you probably mean eMMC, not eeprom? Nov 29 06:59:14 and if you mean whether it's possible to recover eMMC contents even if the system no longer boots, then the answer is yes Nov 29 06:59:34 if you mean whether it's possible to recover data after erasing then the answer is no Nov 29 07:00:15 oho again i need to reflash the OS is it ? Nov 29 07:01:01 you seem to be constantly changing your question... are you asking about recovering data or about getting the beaglebone back into functional state? Nov 29 07:01:22 recovering data Nov 29 07:04:18 if the beaglebone no longer boots, then you can simply boot from an sd card (containing a normal ("standalone") image, NOT a flasher!), then mount eMMC and rescue data from it. if you have sufficient knowledge you can also use this to try to analyze what went wrong and/or get the system on eMMC back into working state Nov 29 07:07:19 ok zmatt thanks for your valuable information Nov 29 13:42:42 ad7193 driver: Should I compile the newest module with DT compatibility? or should I recompile the kernel with platform data? Nov 29 14:07:28 CoffeeBreakfast: platform data is not a thing anymore Nov 29 14:08:02 if updating the kernel is not an option, backporting the driver might be an alternative Nov 29 14:21:59 gp Nov 29 22:19:06 Okay...I have been downgraded to "know-nothing" in the realm of ArduCopter so far. Nov 29 22:19:07 ... Nov 29 22:19:39 There is about six or seven calibration steps that need to take place for me to make ArduCopter work on the BBBlue (I think). Nov 29 22:20:04 Anyway, Mission Planner is stating this fact when I sign in w/ SITL into MP (Mission Planner). Nov 29 22:20:53 I have logs. Please hold if you are an avid BBBlue fanatic, like me, w/ likeness for ArduCopter. Nov 29 22:24:44 Please hold longer. Trouble! Nov 29 22:30:10 I have sitl and small in my folder index but they are elf files or something, i.e. maybe mavlink. They are not human readable. Nov 29 22:30:11 Blah! Nov 29 22:34:16 Okay. So, I think I need Mission Planner for reading the values. Off to get it on this 'puter. Nov 29 23:07:58 Was ArduCopter made to make people lose their Bag-of-Candy? Nov 29 23:13:14 Forget the question for now. I am sorry. I have been working on the software just for a bit. I guess I will start from scratch again. Nov 30 02:04:23 Otay. This fellow helped me out a bit on the GITTER channel for the bbmini page. I think I may have solid gold now. Ya boy! **** ENDING LOGGING AT Sat Nov 30 02:59:57 2019