**** BEGIN LOGGING AT Fri Mar 29 02:59:57 2019 Mar 29 07:23:31 Hello, I am using the version 8.7 BBBW. Sometimes UART1 does not respond. Working only after power down, wait for few seconds and power up. Even restarting could not help. It seems hardware issue. Any help is greatly appreciated. Mar 29 09:10:28 Hello, I am using the version 8.7 BBBW. Sometimes UART1 does not respond. Working only after power down, wait for few seconds and power up. Even restarting could not help. It seems hardware issue. Any help is greatly appreciated. Mar 29 10:20:04 Hi Mar 29 10:21:04 I'm having a hard time finding the beagleboard-x15 revC schematics. The wiki only mentions revB1 (https://elinux.org/Beagleboard:BeagleBoard-X15) Mar 29 12:25:09 (that's because rev B1 is the latest revision of the beagleboard-x15 and rev C does not exist) Mar 29 14:10:23 Rev C = Rev B1 + Silicon Bump Mar 29 14:11:33 ah! I didn't realize that. But yeah I see it now on the wiki page Mar 29 14:13:35 From the PCB side it didn't matter, from the software perspective the 2nd phy doesn't have errata limiting it o 100Mbps, so the device tree has really only one node change.. Mar 29 14:14:41 (if no B1 where off in the wild, we might have just ignored that, and called it the B1..) Mar 29 14:15:39 (oh and the iodelay values for mmc1.. so two changes..) Mar 29 14:16:02 well there are separate dts files for -revb1 and -revc Mar 29 14:16:40 the wiki page could definitely use a bit of updating I think, to make the version history more clear and not use future tense for things that are now long in the past Mar 29 14:19:01 after production moved to PTI, i don't think CircuitCo and Gerald cared to much about updating that page. ;) Mar 29 14:19:29 well someone probably should. that wiki page is still one of the first things you find Mar 29 14:28:26 that should be good enough.. Mar 29 14:29:15 well there's still the whole bit that talking about rev C as if it's still in the future Mar 29 14:29:27 under "CURRENT STATUS" Mar 29 14:31:55 okay, ripped that extra stuff out, and just added under production at PTI, buy here.. Mar 29 14:32:09 seems good! Mar 29 14:33:49 but now the original problem remains that nothing documents that rev C = rev B1 pcb with AM5728/AM5729 r2.0 ... but that should probably go into the github (even if it's just a short readme) Mar 29 14:34:16 btw is the bbx15 guaranteed to have an am5729, or are they also produced with am5728 parts? Mar 29 14:35:04 all rev c's have the eve bit's NOT fused out.. Mar 29 14:35:23 i.e. am5729. cool :) Mar 29 14:35:28 am5728 on package, but am5729 internallly, or whatever weird thing TI did.. Mar 29 14:35:38 the package of mine says am5729 Mar 29 14:36:35 it's one of those things jason fought with ti about, and it was always a "maybe" we'd get to use the eve bits someday.. Mar 29 14:37:22 but that fight has been won right? they even removed the "EVE is not supported" notices from the TRM Mar 29 14:40:52 Yeap, once TI released the tild-api library.... But everything is still built on-top of non-mainline remoteproc changes.. Mar 29 14:41:26 hmm, time to make uio-eve? ;) Mar 29 14:43:12 jason might have a heart attack if that came out.. Mar 29 14:43:59 it probably wouldn't even need any new kernel driver to be honest, uio_pdrv_genirq + some way to allocate physical memory (cmemk?) suffices Mar 29 14:44:19 unless there's an iommu in the way that needs to be managed Mar 29 14:49:31 have you looked at the ti reference manual for the EVE subsystem, it's a pretty comical one paragraph overview.. Mar 29 14:49:46 it has proper documentation in the dra75x trm Mar 29 14:49:57 * rcn-ee[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/IXXCCnpITAftDBeXaCWZGjrq > Mar 29 14:50:06 and that's it.. Mar 29 14:50:39 yeah they didn't document it in the am572x trm, but that doesn't matter since it is still publicly documented in other TRMs Mar 29 15:11:32 eve == embedded vision engine? Mar 29 15:11:38 yep Mar 29 15:12:02 that is supposed to be the big deal in the BBB AI? Mar 29 15:13:42 yeapers Mar 29 15:13:55 + the DSPs Mar 29 15:14:04 (even thou it's also in teh x15) Mar 29 15:14:08 https://training.ti.com/deep-learning-tidl-overview Mar 29 15:14:10 k thanks Mar 29 15:14:48 yeah but the bbai is a lot cheaper and more compact, and has wifi Mar 29 15:17:44 same wifi as the pi, it's going to be a pain in the ... Mar 29 15:17:59 lol Mar 29 17:37:19 hi Mar 29 17:45:03 pueablo: "hi" is not likely to get a response here. if you want help with something, just ask your question and have patience. although there are plenty of knowledgable people here, most only glance at chat occasionally so it can take hours to get a response Mar 29 20:43:37 hi Mar 29 20:43:56 i have question Mar 29 20:45:09 which os is better for beaglebone black Mar 29 20:45:52 can anyone help me??? Mar 29 20:58:50 i like debian Mar 29 20:59:04 other like yocto Mar 29 20:59:21 what are you going to do with it nikola_ ? Mar 29 21:00:25 nikola_: "better" is a really vague criterium, but for most users I would recommend the official images (debian) Mar 29 21:04:31 i want to get data from serial device and USB and send it to virtual server Mar 29 21:04:56 which OS is better for my project?? Mar 29 21:07:33 just use the latest official image Mar 29 21:08:07 (your project imposes no real requirements or constraints on the OS) Mar 29 21:11:30 ok thanks and which language do you recommend for get data from uart noddjs or C++?? Mar 29 21:14:37 which language do you recommend for get data from uart noddjs or C++?? Mar 29 21:14:47 can anyone help me? Mar 29 21:15:05 this is important for me Mar 29 21:17:42 May Noddjs have a good time to get the data?? Mar 29 21:19:22 stop repeating your questions and nagging. most people here only occasionally glance at chat, so it can take time to get a reaction. saying "can anyone help me?" or "this is important for me" is not going to help you get a response faster, it will just annoy people Mar 29 21:19:48 and you can use whatever programming language you want Mar 29 21:20:53 and for "getting data from a uart", the is either "don't care" (if you don't have specific requirements) or "depends" (if you have special requirements that you did not tell us) Mar 29 21:22:00 moreover I feel like this is information you could easily find out yourself. just google "nodejs serial port" and see if whatever you find meets your needs **** ENDING LOGGING AT Sat Mar 30 02:59:57 2019