**** BEGIN LOGGING AT Wed Oct 19 02:59:56 2022 Oct 19 03:55:48 well, the server works. As per Flask has deduced it...the server runeths! Oct 19 03:56:19 I need to learn about WiFi and 5GHz on the remotes now. Argh. Oct 19 04:26:44 Hey, hackster.io let me use my old account again. It is a miracle! Oct 19 04:26:53 Updates underway! Oct 19 06:10:20 hi my name is lakshmi. Oct 19 06:11:01 currently i am working on the beaglebone black board Oct 19 06:11:59 in BBB rev c i am working on the EMMC. Oct 19 06:12:50 In EMMC i need to store the my sensor parameters . Oct 19 06:13:32 by using the TI Rtos i implemented code but its not working. Oct 19 06:14:53 do you have any example code. Oct 19 06:15:02 please send me that Oct 19 06:32:34 Guest17: for questions about TI-RTOS use TI's support forum: https://e2e.ti.com/support/processors-group/processors/f/processors-forum Oct 19 06:33:43 i alredy contacted with the TI support. they suggested to contact with beaglebone support team Oct 19 06:33:55 they're wrong to suggest that Oct 19 06:34:47 can you link to the e2e thread where they suggested that? Oct 19 06:36:10 can you tell me how to test the EMMC on beagle bone with TI Rtos Oct 19 06:36:19 no, I know nothing about TI-RTOS Oct 19 06:36:46 so how can you test the eMMC on BBB. Oct 19 06:36:49 but eMMC on the BBB works exactly the same as eMMC on any other AM335x device. your question is TI-RTOS specific, not beaglebone specific Oct 19 06:36:58 people generally use debian linux on the BBB Oct 19 06:37:02 that's what's supported here Oct 19 06:38:09 through linux you proved the EMMC am i correct Oct 19 06:39:37 "proved" ? eMMC is the primary boot device Oct 19 06:40:08 it's not like it's some kind of obscure peripheral, every beaglebone normally boots from it and stores all data there Oct 19 06:40:14 I mean read write functionality. Oct 19 06:40:44 it's an eMMC, of course it has read-write functionality Oct 19 06:40:51 like, that's what it's for Oct 19 06:41:47 any problems you might be having with eMMC is a TI-RTOS problem, not a BBB problem, hence you should ask TI support Oct 19 06:41:55 how can i test on windows. Oct 19 06:45:06 In BBB using AM335x processor is using MMC1 is connected to EMMC. In widows how to test EMMC. Thats my question actually. Oct 19 06:46:41 you can boot the BBB into linux from SD card and then ssh into it to test the eMMC, or flash linux to eMMC and boot into that Oct 19 06:47:24 did you test on windows . Oct 19 06:47:49 your question doesn't make sense, your host os is irrelevant for what the BBB is doing Oct 19 06:48:03 it's like asking "did you test while wearing an orange t-shirt?" Oct 19 06:48:29 please understand my question. Oct 19 06:48:37 then ask a question that makes sense Oct 19 06:50:23  flashing linux into EMMC and boot into that. Oct 19 06:50:50 i am asking the baremetal test. Oct 19 06:51:37 i.e. you mean ti-rtos, which IS NOT SUPPORTED HERE, ASK ON THE TI FORUM Oct 19 06:52:05 things pass more often when tests are run while wearing a white shirt Oct 19 06:52:09 ;) Oct 19 06:52:26 BBB is designed the BBB or ti  designed the BBB Oct 19 06:52:50 Guest17: TI designed and supports TI-RTOS, which is what your question is about Oct 19 06:53:41 again, eMMC on the BBB works _exactly_ the same as eMMC on ANY OTHER AM335X DEVICE, any questions about how to use eMMC in TI-RTOS are not BBB-related, they're TI-RTOS questions Oct 19 06:54:03 no my question is this beaglebone black board designed by beaglebone am i correct Oct 19 06:54:58 without testing the TI rtos how can you design the BBB . Oct 19 06:55:16 the BBB is designed to run linux Oct 19 06:55:41 additionally, TI (not beagleboard.org) supports running TI-RTOS on the BBB Oct 19 06:55:41 what about the windows system. Oct 19 06:56:04 designing the BBB is trivial... lining things up to purchase the BOM at a usable price is tricky Oct 19 06:56:47 without testing the TI RTOS on BBB you realeased the product Oct 19 06:56:58 Guest17: TI-RTOS is a product by TI supported by TI Oct 19 06:57:01 it is software Oct 19 06:57:27 you might as well as about QNX and your OS of the day Oct 19 06:58:56 Guest17: the beaglebone ships with debian linux, has official debian linux images from beagleboard.org, and supports linux-based development. third parties may also have different software stacks running on the BBB such as openbsd (by volunteers) or TI-RTOS (by TI) but these are not supported by beagleboard.org Oct 19 06:59:33 if you want to use TI-RTOS, ask TI for support Oct 19 07:00:03 they list the BBB as an officially supported development board, therefore any support questions about using TI-RTOS on the BBB should go to TI Oct 19 07:00:33 why is this so hard to understand for you Oct 19 07:01:30 if someone on the TI support forum sent you here, that was simply a mistake by that person Oct 19 08:44:19 is there a way to handle changing /dev/ device names on the BBB or in Linux in general? Oct 19 08:44:34 I keep searching for answers and they all lead to udev. Oct 19 08:50:32 Off to test. I think I have a lead! Oct 19 08:57:50 i believe it's general Oct 19 08:58:04 you find this lookigng at the linux kernel, sources and documentation. Oct 19 08:58:46 There are specifics integrated ie drivers and device tree, some parts are developped specifically, you can see them in the bbb source tree Oct 19 08:59:22 the general answer is indeed udev, specific answers would require a more specific question Oct 19 09:57:56 Hello everyone, Im using this first time, so maybe its not right place to ask, but I would like to find out which manufacturers in Europe are using BeagleBorad,  Is there any chance to get the list or some information... Thank You. Oct 19 10:19:31 hi i don't think you'll find a comprehensive list example if i buy from Farnell and integrate into a product, not necessarily public data Oct 19 10:20:09 you can check although the stock values and get a rough idea of production rate, and peraps monitor the red (industry) which is mostly used by professional i believe Oct 19 10:30:23 Ljubica: what do you mean by "manufacturers using BeagleBoard" ? Oct 19 10:31:35 like, if you mean who are using beagleboard products embedded in their own then obviously that's not information you're going to find since there's no reason for manufacturers to share that information, like jfsimon1981_b said Oct 19 10:31:53 if that's not what you meant then clarify Oct 19 10:32:02 zmatt exactly that is what i would like to know Oct 19 10:32:16 Thank You very much Oct 19 10:32:45 like, the beaglebone is just a component in our product just like any other, why would we mention that anywhere? Oct 19 10:33:06 we also don't publicize where we buy our resistors ;) Oct 19 10:34:42 Yes I understand, Im new in this sector of industry and im trying to get information which i need. I mean, i tried to ask and find out Oct 19 10:34:44 :) Oct 19 10:35:24 typically you'll only find such information public for hobbyist projects Oct 19 10:37:01 is that visible only if I post some project ? Oct 19 10:38:20 ehh I don't mean there's some kind of centralized place that tracks such things, I mean more that hobbyist projects are more likely to write about their project and how it was constructed Oct 19 10:39:06 it's pretty good design, old stable and reliable Oct 19 10:39:13 i believe is a more accurate answer Oct 19 10:39:27 you could browse https://beagleboard.org/p to find other people's projects related to beaglebones Oct 19 10:39:28 though there are subttleties to it for rugged products. Oct 19 10:39:55 I mean, "old" depends on *which* device you're using obviously Oct 19 10:40:14 sure the bb black is a couple years Oct 19 10:40:55 nope. Oct 19 10:41:11 set_: ? Oct 19 10:41:20 Thank you both for sharing time and information with me jfsimon1981_b zmatt Oct 19 10:42:16 welcm Oct 19 10:43:51 https://pastebin.com/sMtZBKKT is the link. Oct 19 10:44:21 I am trying to use udev to handle setting /dev/ device files as what I desire. Oct 19 10:44:44 systemd/systemd on github says "not out bug" Oct 19 10:44:54 out = our Oct 19 10:45:09 and rightly so, why were you bugging them? Oct 19 10:45:22 B/c...I thought they controlled udev in Linux. Oct 19 10:45:31 yes, and? Oct 19 10:45:44 Well, the udev man page(s) are lacking. Oct 19 10:45:47 that rule is nonsensical Oct 19 10:45:51 I know! Oct 19 10:45:53 what on earth are you trying to do?! Oct 19 10:46:22 I am setting a rule to put all sd* device files in /dev/ as /dev/mmcblk* Oct 19 10:46:32 I got close. Oct 19 10:46:39 it makes no sense to want to do that, please stop trying Oct 19 10:46:50 /dev/sd* and /dev/mmcblk* are different kinds of devices Oct 19 10:47:59 syspath parameter missing. <<< That is the error so far. Oct 19 10:48:02 I understand. Oct 19 10:48:14 Fine. Oct 19 10:48:25 this is an XY problems (https://xyproblem.info/) Oct 19 10:48:26 PCI versus scsi. Oct 19 10:48:30 Blah. Oct 19 10:48:47 XY Issues are so '99. Oct 19 10:49:02 fix whatever is motivating you towards this misguided goal Oct 19 10:49:08 Fine. Oct 19 10:49:17 Okay. I will just give up for no reason. Oct 19 10:50:50 I found an older model of what "works." From http://reactivated.net/writing_udev_rules.html#terminology, there is a USB Card Reader example. Oct 19 10:50:51 No go. Oct 19 10:51:13 Card Readers are scsi and not PCI or internal. Blah. That sucks. Oct 19 10:51:17 you don't need to give up on the X in the XY problem, you should give up on the Y (create mmcblk* symlinks for sd*) since this is not the way to solve X whatever it may be Oct 19 10:51:48 Argh. Okay, okay. I will just relenquish my thoughts on this one. Oct 19 10:52:13 It is still fascinating how udev can change the name of devices. Oct 19 10:53:33 w/ my PCI usb card reader, everything just worked like a charm. Oct 19 10:53:52 Now, it is bogus to alter things and make images for fun. Oct 19 10:54:09 It is actually passed bogus and literally impossible. Oct 19 10:55:09 I sold that old computer and USPS lost it. Do you believe it? Oct 19 17:13:46 I have just got the a new BeagleBone AI 64, I am not getting any Display via mini DP port (used DP to HDMI convertor for connecting the monitor), I have connected 5V DC 5 A power supply, keyboard&mouse as per the start up instruction. Please let me know what can be the issue Oct 19 17:20:10 an actual active DP to HDMI converter? Oct 19 17:23:05 note that the bbai64's DP port is *not* a dual-mode DP/HDMI port hence you can't use a passive DP-to-HDMI cable Oct 19 17:47:46 I have used blueRigger mini DP to HDMI active  convertor Oct 19 17:55:01 maybe it's just mislabeled and not an actual active converter? Oct 19 17:57:10 do you have a link to the product you're using? I'm not really finding anything, their website only seems to have a simple mini-DP-to-HDMI cable Oct 19 18:01:03 ah, you mean this thing? https://www.amazon.com/BlueRigger-MiniDisplayPort-Thunderbolt-Compatible-Technology/dp/B01N0LXQD6?ref_=ast_sto_dp Oct 19 18:02:18 it really sucks that the terminology is so vague, since every DP-to-HDMI cable/adapter/converter is technically active, even the ones people generally refer to as "passive" Oct 19 18:07:43 jkridner: ahhhh why oh why did TI implement non-dual-mode DP instead of dual-mode DP /o\ Oct 19 18:08:31 this is going to create a never-ending source of confusion Oct 19 18:17:20 Very true Oct 19 18:17:28 Thank you for the inputs Oct 19 18:17:56 what you want is a converter that's compatible with a non-dual-mode displayport output Oct 19 18:19:22 I figuring out how to use it without tethering  mode - i.e stand alone mode Oct 19 18:20:23 I mean, it's just a linux system like any other... tethering via usb is just a way to establish a network connection to it (but obviously you can also just use ethernet instead) Oct 19 18:23:51 why indeed. :-( maybe royalties? i think their primary use case is eDP. Oct 19 18:28:20 does DVI require royalties? Oct 19 18:28:51 music on me tv please :P Oct 19 18:29:36 fair... I mean, TI has embedded HDMI transmitters before Oct 19 18:30:19 I don't know how much complication dual-mode DP is... I just know that not making the DP dual-mode is going to cause endless confusion and frustration Oct 19 18:30:49 since the ubiquitous DP-to-HDMI cables/adapters won't work Oct 19 18:43:24 zmatt: I use the term "active adapter" as it is Amazon friendly. Oct 19 18:44:30 https://docs.beagleboard.org/latest/boards/beaglebone/ai-64/ch11.html has a note on miniDP adapter Oct 19 18:47:21 https://docs.beagleboard.org/latest/_images/display-adaptors.jpg isn't exactly right.... nothing active required for miniDP to DP. Oct 19 18:48:48 but are they all genuine converters? like I said, technically every DP-to-HDMI is active: https://imgur.com/a/0WZ61Hg Oct 19 18:49:09 they even contain a boost converter to generate 5V from 3.3V :P Oct 19 18:50:05 yeah the image seems misleading, the warning only applies to conversion to HDMI Oct 19 18:51:27 preferably people should use displayport if possible to avoid any worries Oct 19 18:53:45 I guess electrical converter vs protocol converter would be better terms :P Oct 19 19:01:41 jkridner: like, this thing claims to be an active adapter: https://www.amazon.in/BlueRigger-DisplayPort-DisplayPort-Enabled-Projector-Streaming/dp/B07VDL8VKB ... but the product details say "Compliant with VESA Dual-Mode DisplayPort 1.2" which makes me highly suspicious Oct 19 19:05:26 hmmm... no .com equivalent? Oct 19 19:05:34 no idea, it was a google search result Oct 19 19:06:19 (I tried switching country but that just sends you to the amazon homepage so that's pretty useless) Oct 19 19:07:36 I typically used https://smile.amazon.com/iVanky-Active-DisplayPort-Thunderbolt-Adapter/dp/B089GF8M87 Oct 19 19:07:46 s/used/use/ Oct 19 19:07:54 works nicely. Oct 19 19:13:44 you may want to start tracking known-good vs known-bad adapters/cables :) Oct 19 19:50:04 They do this w/ algorithms too instead of using prorpietary Dolby and DTS in boxes. I am not saying this is exactly a match but generally similar. Oct 19 19:52:01 ??? Oct 19 19:52:05 I know my cable it good. mini-DP to DP. Oct 19 19:52:22 I tested it. it works perfectly if you guys need a source of good cabling. Oct 19 19:52:25 if you're using native DP there's no problem, it's just conversion to HDMI that's a problem Oct 19 19:52:33 Oh. Gotcha. Oct 19 19:52:36 Okay. Oct 19 19:52:39 I understood. Oct 19 19:59:25 But yes sir, the mini-DP to DP cables work well. You should have seen my screen glow w/ the Boris. Oct 19 20:05:34 has anyone been using GPS w/ the UART2 recently on the am335x/BBB? I cannot seem to make gpsdclient work any longer. I restarted the services that are available from gpsd.service and .socket but I receive "cannot connect" as output. Oct 19 20:09:39 Is it a kernel 5.10.x issue and I need to research more or is gpsdclient on /dev/ttyS2 no longer a viable option for GPS? Oct 19 20:12:25 I guess it is me. I am not getting how this new specification is working so far. I guess I will stay patient... Oct 19 21:00:23 set_ are you sure you are getting data out from usart2? Oct 19 21:01:22 Have you tried to connect to the port and send out data to see if the approprate pin is connected? Oct 19 21:02:29 A simple way may be to hook up an led between 1.8V (or 3v3) and the tx pin of uart 2 Oct 19 21:02:49 then whenever you send data, the tx should pull low and the led flicker ever so slightly Oct 19 22:26:22 No. Oct 19 22:26:30 No. Oct 19 22:27:02 The other day, I ran the source. it worked w/ the Grove_GPS on uart2, the Grove Connector on the board. Oct 19 22:27:26 I ran it last night/this morning and notta, i.e. erroring out w/ the output "cannot connect." Oct 19 22:27:48 I never knew you could lite up LEDs w/ UART! Oct 19 22:28:00 That is a new one to me. Oct 19 22:28:09 So, use transmit only? Oct 19 22:28:30 Oh! Oct 19 22:29:06 So, somebody w/ this am335x/am5729 Compat. Layer may have switched up the understanding from what it was currently. Oct 19 22:29:19 Of course, I am chatting about pin muxing here. Oct 19 22:30:44 kongn: Sorry. I should have mentioned your name. I am a bit tired right now but up! Oct 19 22:32:13 I just plugged in. The PWR connector on the Grove_GPS is lighting up the LED. Probably from a driver or something. Oct 19 22:41:29 :2947 is already in use. Blah. Oct 19 22:41:48 That is the client address of the socket (I think). Let me double check. Oct 19 22:57:21 I think things are a bit over and passed on my end. I should have paid more attention. Oct 19 22:57:51 GPSd flew by me again b/c I could not get things configured w/ other items of interest. Oct 19 23:05:43 Okay. Oct 19 23:05:51 man! Oct 19 23:09:03 My gpsd.socket is bright red! Okay. break time. Oct 19 23:31:48 Hmm. They say, they say, I did not have the client installed but that the lib. took over my sys. Oct 19 23:31:50 Aw. Oct 19 23:31:57 So close yet... Oct 19 23:34:31 Oh. i remember now. I was going for a biking and running the source. Then, something happened. The source quit on a brother. Oct 19 23:50:11 I never even made it to my bike. Blah. Figuring it out is my fourth name! **** ENDING LOGGING AT Thu Oct 20 02:59:56 2022