**** BEGIN LOGGING AT Wed Feb 09 02:59:56 2022 Feb 09 03:04:23 Okay...I got a new photo and I think the CLK goes a bit awkward when the CS goes high. Feb 09 03:04:47 Awkward = I am not desribing well what is actually taking place. Feb 09 03:06:19 Anyway, if you are not bored yet: https://imgur.com/a/19M22Yt has three photos. The last file down is the the CLK and CS lines attached. Feb 09 03:18:14 fine tune: https://imgur.com/a/gPhmBhB Feb 09 03:21:58 Is CH2 grounded? Feb 09 03:22:33 i.e. connected to the same ground as CH1 Feb 09 03:23:58 Yes and no. Feb 09 03:24:21 I have CH2 grounded to the BBAI on P9.2 while CH1 is grounded to P9.1. Feb 09 03:31:31 timing is a bit odd on that Feb 09 03:31:36 CS is yellow? Feb 09 03:31:53 or what you are calling CS? Feb 09 03:32:07 that does not seem right Feb 09 03:32:31 increase the per X division time Feb 09 03:32:37 Maybe I used trigger. Feb 09 03:32:38 Okay. Feb 09 03:32:45 CS is yellow. Feb 09 03:32:51 Blue is CLK. Feb 09 03:33:03 Let me retry. Feb 09 03:33:43 CS should stay low while a xfer is in progress Feb 09 03:33:56 I also used 100000 delay. Feb 09 03:34:17 Sorry, 1000000 delay. Feb 09 03:34:40 My lines were a bit off. Off to try. brb. Feb 09 03:35:34 this is w/ CS high and delay at 10000. Feb 09 03:35:37 Brb w/ the photo. Feb 09 03:38:33 ds2: Should I perform the action w/out the CS w/ the -C call on the command line? Feb 09 03:39:38 Here: https://imgur.com/a/Bs2g9U1 Feb 09 03:40:14 So, it seems when CS goes high due to my -C call on the command line, the CLK jumps a bit. Feb 09 03:40:38 Then soon after, goes flat until a bit later. Feb 09 03:50:01 Anyway, here is the command for the driver when I run the source: sudo ./spidev_test -C -d 10000 Feb 09 03:51:21 And...I reset all my variables to default on the o-scope to get this reading: https://imgur.com/cJ7ipxA Feb 09 03:52:09 Anyway...time will tell what I can decipher. It is late now and I need to eat more! BRB or BBL, argh. Feb 09 04:00:53 Also, late night ringer: https://imgur.com/a/C8I0eif must be some noise of some freq. getting caught up in the mix. Feb 09 04:39:35 that is either not CS or something is wrong with it. it should be active when data is clocking Feb 09 05:25:45 am I seeing correctly that these channels are set to 50 mV/div and 100 mV/div respectively? Feb 09 05:26:01 and you're hoping to see anything other than noise? Feb 09 05:28:20 that previous pic is equally sus, showing a signal (or possibly a clock) but it's less than 0.1V in amplitude... do you have a short-circuit / drive-conflict going on or something? Feb 09 05:28:36 https://imgur.com/a/gPhmBhB I mean Feb 09 05:29:40 and your CS seems to be configured active-high, which is very unusual Feb 09 05:48:46 if it was active high CS then why is it predominately high? Feb 09 05:49:46 if the 10x probe setting was wrong, the 50mv/div isn't bad Feb 09 05:50:13 oh, wrong probe setting, right Feb 09 05:50:55 and CS seems high during activity? Feb 09 05:51:09 and he said something about configuring some huge delay, during which cs would be held active as well Feb 09 05:51:59 so https://imgur.com/a/C8I0eif is fully consistent with active-high cs: idle period with CS high (delay at end of previous transfer), brief low between transfers, then high for the next transfer Feb 09 05:53:33 and good call on the probe gain, if the scale is off by a factor of 10 then the blue signal is 3.3V, so that part makes sense too Feb 09 11:45:16 Hi Feb 09 11:46:59 Request you to provide REACH & ROHS3 certificate of Beagleboard # 102110420 Feb 09 11:48:03 Request you to provide REACH & ROHS3 certificate of Beagleboard # 102110420 Feb 09 11:48:39 Please sent these 3 certificates on prasad.Acharekar@TCS.com Feb 09 11:53:05 Guest64: this is a user community chat Feb 09 11:54:51 ask your distributor or the manufacturer (Seeed Technology) Feb 09 11:57:00 Guest64: unless this is what you're looking for: https://www.mouser.com/catalog/additional/Seeed_Studio_EU_DOC_for_102110420_BeagleBone_Black_102110423_BeagleBone_Black_Industrial.pdf Feb 09 13:57:14 I am shorting the MOSI/MISO pins for /dev/spidev1.0. Feb 09 13:59:30 Did you guys think something was incorrect, i.e. ds2 and @zmatt? Feb 09 14:04:22 I also put the single run in a loop, i.e. w/ while(1). Feb 09 14:33:18 Anyway...here is another morning try: https://imgur.com/a/fsvI6tV along w/ window! Feb 09 14:38:33 I will try w/ a SPI Cam or another SPI device to test soon. Feb 09 15:29:24 set_: it looks like you configured the chip-select to be active-high instead of active-low, which is a bit unusual (though obviously doesn't matter if you're doing a loopback test) Feb 09 15:29:30 what's your actual problem/question ? Feb 09 15:30:54 looks like this is the data line being monitored and you're sending all-ones ? Feb 09 16:40:15 btw that scope doesn't detect the probe 1X/10X switch, so you need to set the scale in the menu accordingly Feb 09 19:02:45 No question and yes, hnv, you are right. I have a switch on the probe. Feb 09 19:03:17 I have to set the probe and the MCU on the o-scope to handle 1x or 10x. Feb 09 19:05:14 Molloy's book and source has a driver dedicated to spidev w/ a loopback test. In this test, one can use a -C option on the command line to "announce" a CS High instead of CS being as it were, i.e. active low. Feb 09 19:11:30 okay, but why would you use that option? Feb 09 19:12:07 I've never seen an spi device that used an active-high CS Feb 09 19:13:02 I am just testing to see if it worked or not. Feb 09 19:13:15 it evidently does Feb 09 19:13:29 I have no reasoning to test w/ the -C option. Yes, it works. Feb 09 19:13:54 So, SPI devices never use active high. Okay. Feb 09 19:14:02 Now, I know. Feb 09 19:14:31 I mean, who knows what kind of weird things exist :P but I've personally never encountered one Feb 09 19:14:40 Aw. Feb 09 19:14:56 Okay and that sounds right. Things are awkward at times w/ what exists. Feb 09 19:15:10 Who knows what people will do? Feb 09 19:15:32 ! Feb 09 19:16:11 Well, I will test later for the non -C option on the command line for the SPI on the AI. Feb 09 19:16:19 It is getting interesting. Feb 09 19:16:59 anyway...up, up, and Otay! Feb 09 19:17:04 bbl Feb 09 22:08:06 a device may not use CS (active high) but parts shortages/EE's may force SW to configure things as active high Feb 09 22:08:24 i.e. an inverting level translator Feb 09 22:19:02 that seems really desperate though, since you'd also need to invert the data in software Feb 09 22:46:07 Ooh la la. Zoinks. Feb 09 22:46:40 The SPIDEV devices work! Now, my readings on the other hand will need some work. Feb 09 22:47:28 What device do any of you persons recommend for displaying the use of SPI connectivity to the BBAI (to/from)? Feb 09 22:48:14 I am asking b/c the people on the forums think two SPI devices are not enough for their instances or something. I am not sure exactly what they think. Feb 09 22:49:04 I mean... Feb 09 22:49:38 What are some examples of SPI modules to use, i.e. I found some from Molloy's book and an email popped up as soon as I asked, i.e. imu? Feb 09 22:53:07 Anyway, here: https://forum.beagleboard.org/t/configuring-spi-pins-in-beaglebone-ai/31124?u=silver2row . Feb 09 22:53:34 There is a long list of ideas, some bouncing, and relative conclusions (I think). Feb 09 23:38:12 Anyway, so let me get this correct here: The CS line should go high b/c I am telling it to, which it does, and then the CLK should go low? Feb 09 23:38:37 I need an update to the MCU on the board in this "fancy contraption." Brb. Feb 10 00:06:26 Look at the actual loop back test pin(s) being sourced along w/ the CS line: https://imgur.com/a/wSYXRpB . Feb 10 00:06:39 Wild! Feb 10 00:07:15 looks like you're zoomed out too far Feb 10 00:07:22 horizontally Feb 10 00:07:31 Argh. Feb 10 00:07:35 (and zoomed in too much vertically) Feb 10 00:07:53 Hahah. I cannot describe what actually happened yet. I am studying. Feb 10 00:08:19 I put the channels at 200mV. Feb 10 00:08:40 It was off the screen and i had to put it back once i captured the frequency. Feb 10 00:10:24 Hmm. Feb 10 00:11:48 I got it! Feb 10 00:11:51 Please hold. Feb 10 00:12:12 I still have no idea why you're looking at spi signals with a scope in the first place Feb 10 00:12:18 everything I've seen so far looked fine to me Feb 10 00:13:00 to the (limited) extent this could be determined from your captures Feb 10 00:13:29 it's difficult to examine spi properly with a scope that has only two channels Feb 10 00:13:39 Ha. Please hold for this last capture. I finally got it nailed down. Oh? Feb 10 00:13:41 Okay. Feb 10 00:13:43 No issue. Feb 10 00:13:54 like, why are you doing this? Feb 10 00:15:01 B/c for one, I need to learn things and secondly, if I am going to handle electronics, I need to know they work to the specified instances of the datasheets, right? Feb 10 00:15:40 @zmatt: Will you please look at this last capture? I am feeling needy! Feb 10 00:16:10 I mean, generally you'd assume things work as specified in their datasheets unless you have a specific reason to examine things, e.g. because you're trying to debug a problem Feb 10 00:16:44 Oh. Feb 10 00:17:12 Me on the other hand, right. No, I get it. I get what you are saying. Why me, why would I be doing this now? Feb 10 00:18:25 Well, the BBAI has contenders that do not to this day believe it works, for whatever reason and I am trying to describe it in more ways than just commands, txt files, and explanations. Feb 10 00:19:21 Well, I would not say they believe it is broken/does not work even though I typed it out. I would say people have complications at times w/ hardware and software. Feb 10 00:19:23 plenty of people have spi working just fine on the bbai, and now that cape-universal is supported it should be basically as simple as on the bbb Feb 10 00:19:32 Right! Feb 10 00:19:42 I know and it is outstanding. Feb 10 00:20:28 But, the forum people are not understanding it or not believing me for whatever reason. Anyway, I was spreading good cheer. Feb 10 00:21:24 Does this look better: https://imgur.com/a/wSYXRpB ? Feb 10 00:21:37 I think i got it nailed that time! Feb 10 00:23:59 But this set up is quite different than the last CS line and CLK. This time it is the actual MOSI/MISO connection and the CS line. Feb 10 00:25:13 Would there be any info. to gather from the MOSI/MISO lines during a loopback test for a SPI device on the BBAI? Feb 10 02:04:16 set_: ehm, that capture still uses the same terrible scaling Feb 10 02:05:17 I still have no idea what you're trying to capture or why, but nobody can tell anything from this Feb 10 02:10:35 decrease the time scale (zoom in horizontally) until the signal isn't an amorphous blob anymore and you can actually see anything, reduce the voltage scale (zoom out vertically) for both channels until you can position them to neither go offscreen nor overlap each other Feb 10 02:11:23 if the probe gain is correctly configured I'd expect 1V per division to be appropriate instead of 200 mV Feb 10 02:23:49 Both probes and the scales should be set to x10 Feb 10 02:34:50 Whelp. That did it. Feb 10 02:34:54 Okay. Feb 10 02:35:17 Oh. Feb 10 02:35:22 x10. Okay. Feb 10 02:35:36 I had them at x10 and changed it to x1. Feb 10 02:35:57 Well...I will have to learn more before proceeding. I took a break and handled some Bela stuff. Feb 10 02:36:30 Broke it, flipped it, cracked it, and I only have one string to attach! But, I need to get another string, i.e. as I broke that too. Feb 10 02:36:31 Blah. Feb 10 02:37:52 Sometimes I am so close to "stardom" and then flattened like being under a steamroller. Feb 10 02:38:53 x1 you have an order of magnitude less bandwidth than your scope... x1 may be helpful measuring low amplitude signals, which aren't your case Feb 10 02:40:20 Aw. Okay. Feb 10 02:43:01 Well, I tried this time to do nothing and got somewhere. I small somewhere but somewhere! Feb 10 02:43:21 I = A. Blah. **** ENDING LOGGING AT Thu Feb 10 02:59:56 2022