Shadyman has joined #beagle
vagrantc has quit [Quit: leaving]
<GenTooMan> set_, at least you weren't answering.
<GenTooMan> I've suggested taking notes and carefully noting what didn't work but ... heh :D
<set_> Well, note 1: Nothing works.
<set_> Note 2: Reading is taking place slowly.
<set_> Note 3: I should have not done that...
<set_> I know it is not a joke.
<set_> Like a cow, one must graze to get to the root!
<set_> This is what I do know. cmake is the main compilation tool and upload installs the cmake build(s) onto the BBBlue.
<set_> sorry. Make.
<set_> not cmake.
<set_> So, I think I am going to add some libs. from PX4 onto the Makefile or cmake File and then compile, upload, and test.
<set_> They have plenty of files and some are dedicated to sensors on the BBBlue.
<set_> I am receiving an error on remoteproc state(s) so far. This is conquering some advancement.
<set_> ...
<set_> I shall wait!
<set_> R31_14 and R31_15 are the pru inputs on the BBBlue, right?
<set_> in /pru_firmware/src/pru0-encoder.asm there is a bunch of what seems to be incrementing and decrementing plus shifting of bits to come to a conclusion.
<set_> So, this shared file gets pushed into a loop and never ends or something?
<set_> It just runs constantly at a specified MHz?
<set_> Do I need to know .asm file handling to handle clpru or is that only for pasm?
starblue1 has joined #beagle
starblue has quit [Ping timeout: 245 seconds]
<set_> Hmm. It says this but does that...It is like something has changed. My scope is 1GHz but not multi-channel. I have exactly one channel.
vd has quit [Quit: Client closed]
lucascastro has quit [Ping timeout: 268 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
ikarso has joined #beagle
giort has joined #beagle
samnob has quit [Read error: Connection reset by peer]
samnob has joined #beagle
samnob has quit [Read error: Connection reset by peer]
samnob has joined #beagle
giort has quit [Ping timeout: 265 seconds]
nslu2-log has joined #beagle
Guest17 has joined #beagle
Guest17 has quit [Quit: Client closed]
nslu2-log has quit [Remote host closed the connection]
nslu2-log has joined #beagle
nslu2-log has quit [Remote host closed the connection]
nslu2-log has joined #beagle
florian has joined #beagle
GenTooMan has quit [Ping timeout: 268 seconds]
GenTooMan has joined #beagle
Guest72 has joined #beagle
<Guest72> Hi all, does any one know if I need the BB AI to use opencv to get alerts on figure detection?
<Guest72> I mean that I want to connect a camera and get alerts on human figure detection
<Guest72> I think I saw the BB can only do 1 frame per sec
Shadyman has quit [Remote host closed the connection]
blech has joined #beagle
<blech> Howdy
<blech> I am looking for some support to my BBB. Am I on a right place here?
<blech> On a first look it seems I am on a right place. So I'll start.
<blech> BBB all happy for 6mnts+. Also me being very happy. No problems at all. Steep learning curve. Couple days back my terminal started complaining about attempting an operation on a read-only FS only.
<blech> Restarted BBB and while LEDs indicated booting up and then heart-beat, I couldn't get back tty over wifi, then even USB. All resolved itself by a faulty SD card.
<blech> Now, my question. In an attempt to resolve this I attempted to connect to the serial port as described here: https://elinux.org/EBC_Exercise_21a_Boot_Sequence
<blech> Having checked everything twice - I couldn't see anything on that tty at all. I brought same cable to a friend and the same there (nothing).
<blech> There is a chance that instructions on that EBC_Exercise page are wrong, or my (brand new) FTDI cable is wrong.
<blech> ... or I am missing something completely.
<blech> Would you be able to advise if there is a way to connect to BBB over serial cable and what would be a correct way please? Goal is to be able to monitor BBB closely and also being able to debug some of these problems in a future on my own.
argonautx has joined #beagle
<zmatt> did you connect to the correct port on your computer?
<zmatt> like, that wiki page seems to blindly assume the ftdi serial cable you plugged into your computer is /dev/ttyUSB0 but that doesn't need to be true at all
<zmatt> and of course make sure the cable is plugged in correctly
<zmatt> other than that I have no idea, the serial console should basically always produce output at boot, even if it fails to boot
<zmatt> blech: btw you said BBB but you also mentioned wifi, which the BBB doesn't have... do you mean the BBBW ? (it doesn't matter either way for the serial console but it's generally a good idea to be precise about which device you have)
<zmatt> also make sure it's a 3.3v ftdi cable, a 5v ftdi cable might not work reliable (the serial console port is 5V tolerant (unlike everything else on the BBB) but only outputs 3.3V serial data which might not suffice for a 5V ftdi cable)
otisolsen70 has joined #beagle
lucascastro has joined #beagle
<Guest72> hi zmatt
<zmatt> Guest72: sorry I have no experience with opencv
<Guest72> ok, thnaks
johanhenselmans has quit [Ping timeout: 265 seconds]
sicelo has quit [Ping timeout: 245 seconds]
Guest72 has quit [Quit: Client closed]
lucascastro has quit [Quit: Leaving]
lucascastro has joined #beagle
buzzmarshall has joined #beagle
sicelo has joined #beagle
sicelo has joined #beagle
sicelo has quit [Changing host]
otisolsen70 has quit [Quit: Leaving]
vd has joined #beagle
GenTooMan has quit [Ping timeout: 260 seconds]
akaWolf has quit [Ping timeout: 268 seconds]
Shadyman has joined #beagle
GenTooMan has joined #beagle
giort has joined #beagle
GenTooMan has quit [Ping timeout: 265 seconds]
zmatt has quit [Ping timeout: 245 seconds]
GenTooMan has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
GenTooMan has quit [Ping timeout: 265 seconds]
florian has quit [Quit: Ex-Chat]
argonautx has quit [Quit: Leaving]
GenTooMan has joined #beagle
zmatt has joined #beagle
Guest72 has joined #beagle
<Guest72> hi, is anyone in this time zones, uses the AI version and can tell me if it has any opencv acceleration?
vd has quit [Quit: Client closed]
vd has joined #beagle
charlie5 has quit [Ping timeout: 252 seconds]
GenTooMan has quit [Ping timeout: 240 seconds]
michaelo has quit [Remote host closed the connection]
michaelo has joined #beagle
GenTooMan has joined #beagle
akaWolf has joined #beagle
vd has quit [Quit: Client closed]
GenTooMan has quit [Ping timeout: 260 seconds]
zjason has quit [Read error: Connection reset by peer]
zjason has joined #beagle
GenTooMan has joined #beagle
<blech> Hi zmatt, I've checked that cable and it really is 5V! Let me have another go with 3.3V. Thanks!!
kona has left #beagle [WeeChat 1.9.1]
giort has quit [Ping timeout: 268 seconds]
vd has joined #beagle
giort has joined #beagle
giort has quit [Ping timeout: 252 seconds]
<set_> Guest72: I use the BBAI and openCV.
<set_> Some stuff from OpenCV work, python3-opencv and libopencv-dev. But...I think you may have to cross-compile the examples.
<set_> I get stuck w/ the samples lib. from OpenCV.
<set_> Most of their ideas work so far on the BBAI but I have not got to handling the LCD screen for the BBAI yet.
CrazyEddy has quit [Ping timeout: 260 seconds]
<set_> Now...about acceleration, I am not sure. I am sure if you can unload it on one of the EVE cores or the IPU, yes. Then, acceleration is possible.
<set_> But...I am out-of-date on that front.
<set_> Guest72: Here is a way to get examples on the board... https://docs.opencv.org/master/d0/d76/tutorial_arm_crosscompile_with_cmake.html
<set_> Also...if you figure out how to handle the GPU onboard the AI, it may help.
<set_> 2D-graphics accelerator (BB2D) subsystem && Dual-core PowerVR® SGX544™ 3D GPU
<set_> So...yes. I think it is possible.
<set_> https://learnopencv.com/opencv-transparent-api/ has some examples and info. that may not be available elsewhere.
<set_> For instance...the OpenCL SDK is required for the AI. I am not sure any advancements have been made w/ the SGX544 yet but imagtech. has a dev. account to sign up for currently to get the SDK and they have a good wiki too.