<Guest17>
i alredy contacted with the TI support. they suggested to contact with beaglebone support team
<zmatt>
they're wrong to suggest that
<zmatt>
can you link to the e2e thread where they suggested that?
<Guest17>
can you tell me how to test the EMMC on beagle bone with TI Rtos
<zmatt>
no, I know nothing about TI-RTOS
<Guest17>
so how can you test the eMMC on BBB.
<zmatt>
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
<zmatt>
people generally use debian linux on the BBB
<zmatt>
that's what's supported here
<Guest17>
through linux you proved the EMMC am i correct
<zmatt>
"proved" ? eMMC is the primary boot device
<zmatt>
it's not like it's some kind of obscure peripheral, every beaglebone normally boots from it and stores all data there
<Guest17>
I mean read write functionality.
<zmatt>
it's an eMMC, of course it has read-write functionality
<zmatt>
like, that's what it's for
<zmatt>
any problems you might be having with eMMC is a TI-RTOS problem, not a BBB problem, hence you should ask TI support
<Guest17>
how can i test on windows.
<Guest17>
In BBB using AM335x processor is using MMC1 is connected to EMMC. In widows how to test EMMC. Thats my question actually.
<zmatt>
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
<Guest17>
did you test on windows .
<zmatt>
your question doesn't make sense, your host os is irrelevant for what the BBB is doing
<zmatt>
it's like asking "did you test while wearing an orange t-shirt?"
<Guest17>
please understand my question.
<zmatt>
then ask a question that makes sense
<Guest17>
flashing linux into EMMC and boot into that.
<Guest17>
i am asking the baremetal test.
<zmatt>
i.e. you mean ti-rtos, which IS NOT SUPPORTED HERE, ASK ON THE TI FORUM
<ds2>
things pass more often when tests are run while wearing a white shirt
<ds2>
;)
<Guest17>
BBB is designed the BBB or ti designed the BBB
<zmatt>
Guest17: TI designed and supports TI-RTOS, which is what your question is about
<zmatt>
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
<Guest17>
no my question is this beaglebone black board designed by beaglebone am i correct
<Guest17>
without testing the TI rtos how can you design the BBB .
<zmatt>
the BBB is designed to run linux
<zmatt>
additionally, TI (not beagleboard.org) supports running TI-RTOS on the BBB
<Guest17>
what about the windows system.
<ds2>
designing the BBB is trivial... lining things up to purchase the BOM at a usable price is tricky
<Guest17>
without testing the TI RTOS on BBB you realeased the product
<zmatt>
Guest17: TI-RTOS is a product by TI supported by TI
<ds2>
it is software
<ds2>
you might as well as about QNX and your OS of the day
Guest17 has quit [Quit: Client closed]
<zmatt>
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
<zmatt>
if you want to use TI-RTOS, ask TI for support
<zmatt>
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
<zmatt>
why is this so hard to understand for you
<zmatt>
if someone on the TI support forum sent you here, that was simply a mistake by that person
<set_>
is there a way to handle changing /dev/ device names on the BBB or in Linux in general?
<set_>
I keep searching for answers and they all lead to udev.
otisolsen70 has joined #beagle
<set_>
Off to test. I think I have a lead!
set_ has quit [Remote host closed the connection]
<jfsimon1981_b>
i believe it's general
<jfsimon1981_b>
you find this lookigng at the linux kernel, sources and documentation.
<jfsimon1981_b>
There are specifics integrated ie drivers and device tree, some parts are developped specifically, you can see them in the bbb source tree
<zmatt>
the general answer is indeed udev, specific answers would require a more specific question
florian has joined #beagle
Ljubica has joined #beagle
<Ljubica>
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.
<jfsimon1981_b>
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
<jfsimon1981_b>
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
ft has quit [Quit: leaving]
<zmatt>
Ljubica: what do you mean by "manufacturers using BeagleBoard" ?
<zmatt>
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
<zmatt>
if that's not what you meant then clarify
<Ljubica>
zmatt exactly that is what i would like to know
<Ljubica>
Thank You very much
<zmatt>
like, the beaglebone is just a component in our product just like any other, why would we mention that anywhere?
<zmatt>
we also don't publicize where we buy our resistors ;)
<Ljubica>
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
<Ljubica>
:)
<zmatt>
typically you'll only find such information public for hobbyist projects
<Ljubica>
is that visible only if I post some project ?
<zmatt>
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
<jfsimon1981_b>
it's pretty good design, old stable and reliable
<jfsimon1981_b>
i believe is a more accurate answer
<zmatt>
you could browse https://beagleboard.org/p to find other people's projects related to beaglebones
<jfsimon1981_b>
though there are subttleties to it for rugged products.
<zmatt>
I mean, "old" depends on *which* device you're using obviously
<jfsimon1981_b>
sure the bb black is a couple years
set_ has joined #beagle
<set_>
nope.
<zmatt>
set_: ?
<Ljubica>
Thank you both for sharing time and information with me jfsimon1981_b zmatt
<set_>
Card Readers are scsi and not PCI or internal. Blah. That sucks.
<zmatt>
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
<set_>
Argh. Okay, okay. I will just relenquish my thoughts on this one.
<set_>
It is still fascinating how udev can change the name of devices.
<set_>
w/ my PCI usb card reader, everything just worked like a charm.
<set_>
Now, it is bogus to alter things and make images for fun.
<set_>
It is actually passed bogus and literally impossible.
<set_>
I sold that old computer and USPS lost it. Do you believe it?
Ljubica has quit [Quit: Client closed]
xet7 has joined #beagle
GenTooMan has joined #beagle
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #beagle
lucascastro has joined #beagle
lucascastro has quit [Quit: Leaving]
lucascastro has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 268 seconds]
Guest617 has joined #beagle
buzzmarshall has joined #beagle
brook has joined #beagle
alan_o has quit [Quit: Leaving]
alan_o has joined #beagle
lucascastro has quit [Remote host closed the connection]
balrog has quit [Ping timeout: 268 seconds]
balrog has joined #beagle
brook has quit [Remote host closed the connection]
Guest617 has quit [Quit: Client closed]
brook has joined #beagle
kongn has joined #beagle
Guest3 has joined #beagle
<Guest3>
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
<zmatt>
an actual active DP to HDMI converter?
<zmatt>
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
CrazyEddy has joined #beagle
florian has quit [Quit: Ex-Chat]
<Guest3>
I have used blueRigger mini DP to HDMI active convertor
<zmatt>
maybe it's just mislabeled and not an actual active converter?
<zmatt>
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
<zmatt>
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"
<zmatt>
jkridner: ahhhh why oh why did TI implement non-dual-mode DP instead of dual-mode DP /o\
<zmatt>
this is going to create a never-ending source of confusion
<Guest3>
Very true
<Guest3>
Thank you for the inputs
<zmatt>
what you want is a converter that's compatible with a non-dual-mode displayport output
<Guest3>
I figuring out how to use it without tethering mode - i.e stand alone mode
<zmatt>
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)
<jkridner>
why indeed. :-( maybe royalties? i think their primary use case is eDP.
<zmatt>
does DVI require royalties?
<NishanthMenon>
music on me tv please :P
<zmatt>
fair... I mean, TI has embedded HDMI transmitters before
<zmatt>
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
<zmatt>
since the ubiquitous DP-to-HDMI cables/adapters won't work
alan_ has joined #beagle
Guest3 has quit [Quit: Client closed]
alan_ has quit [Remote host closed the connection]
alan_o has quit [Remote host closed the connection]
<jkridner>
zmatt: I use the term "active adapter" as it is Amazon friendly.
<zmatt>
you may want to start tracking known-good vs known-bad adapters/cables :)
ft has joined #beagle
vagrantc has joined #beagle
<set_>
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.
<zmatt>
???
<set_>
I know my cable it good. mini-DP to DP.
<set_>
I tested it. it works perfectly if you guys need a source of good cabling.
<zmatt>
if you're using native DP there's no problem, it's just conversion to HDMI that's a problem
<set_>
Oh. Gotcha.
<set_>
Okay.
<set_>
I understood.
<set_>
But yes sir, the mini-DP to DP cables work well. You should have seen my screen glow w/ the Boris.
<set_>
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.
<set_>
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?
buckket has quit [Remote host closed the connection]
xet7 has quit [Remote host closed the connection]
<set_>
I guess it is me. I am not getting how this new specification is working so far. I guess I will stay patient...
buckket has joined #beagle
lucascastro has joined #beagle
buckket has quit [Quit: buckket]
buckket has joined #beagle
alan_o has joined #beagle
<kongn>
set_ are you sure you are getting data out from usart2?
<kongn>
Have you tried to connect to the port and send out data to see if the approprate pin is connected?
<kongn>
A simple way may be to hook up an led between 1.8V (or 3v3) and the tx pin of uart 2
<kongn>
then whenever you send data, the tx should pull low and the led flicker ever so slightly
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 268 seconds]
brook has joined #beagle
lucascastro has quit [Ping timeout: 268 seconds]
otisolsen70 has quit [Quit: Leaving]
<set_>
No.
<set_>
No.
<set_>
The other day, I ran the source. it worked w/ the Grove_GPS on uart2, the Grove Connector on the board.
<set_>
I ran it last night/this morning and notta, i.e. erroring out w/ the output "cannot connect."
<set_>
I never knew you could lite up LEDs w/ UART!
<set_>
That is a new one to me.
<set_>
So, use transmit only?
<set_>
Oh!
<set_>
So, somebody w/ this am335x/am5729 Compat. Layer may have switched up the understanding from what it was currently.
<set_>
Of course, I am chatting about pin muxing here.
<set_>
kongn: Sorry. I should have mentioned your name. I am a bit tired right now but up!
<set_>
I just plugged in. The PWR connector on the Grove_GPS is lighting up the LED. Probably from a driver or something.
<set_>
:2947 is already in use. Blah.
<set_>
That is the client address of the socket (I think). Let me double check.
<set_>
I think things are a bit over and passed on my end. I should have paid more attention.
<set_>
GPSd flew by me again b/c I could not get things configured w/ other items of interest.
brook has quit [Remote host closed the connection]
<set_>
Okay.
<set_>
man!
<set_>
My gpsd.socket is bright red! Okay. break time.
brook has joined #beagle
<set_>
Hmm. They say, they say, I did not have the client installed but that the lib. took over my sys.
<set_>
Aw.
<set_>
So close yet...
<set_>
Oh. i remember now. I was going for a biking and running the source. Then, something happened. The source quit on a brother.
<set_>
I never even made it to my bike. Blah. Figuring it out is my fourth name!