**** BEGIN LOGGING AT Sat Aug 05 03:00:01 2017
Aug 05 03:07:28 <MrCurious> jkridner: thanks for fixing the blue ros link!!!!
Aug 05 03:07:36 <jkridner> np
Aug 05 03:09:26 <ver|laptop> jkridner: are there schematics out for the Blue .. someone was asking about connector pinouts recently-ish?
Aug 05 03:09:44 <jkridner> https://github.com/beagleboard/beaglebone-blue
Aug 05 03:09:53 <jkridner> also, linked from https://beagleboard.org/blue
Aug 05 03:10:19 <MrCurious> ver|laptop: that was me, found em :) ty
Aug 05 03:11:23 <MrCurious> got motors, servo's, serial all working and wired now to the blue. ros built, just need to link ros with the hardware to drive them. in a good happy place
Aug 05 03:12:38 <ver|laptop> jkridner: d'oh ta, and good stuff MrCurious
Aug 05 03:12:42 <zmatt> NishanthMenon: yo!
Aug 05 03:12:44 <MrCurious> my robot has transitioned from a mechanical/electrical project to a software one
Aug 05 03:12:53 <ver|laptop> progress!
Aug 05 03:13:16 <jkridner> nice pinout diagram: https://groups.google.com/d/msg/beagleboard/ZXSTPIcV4OU/_h241etcAAAJ
Aug 05 03:13:36 <MrCurious> i have been using this one
Aug 05 03:13:37 <MrCurious> https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf
Aug 05 03:15:20 <NishanthMenon> zmatt, hi. I did not know how to attribute the reported-by to you. so, please feel free to respond to https://lists.denx.de/pipermail/u-boot/2017-August/301319.html
Aug 05 03:15:24 <zmatt> NishanthMenon: swpu282af ? we never got that revision from TI :-/
Aug 05 03:16:04 <NishanthMenon> zmatt, yeah, i was handed the TRM on a usb stick :(
Aug 05 03:16:12 <zmatt> .....
Aug 05 03:16:15 <NishanthMenon> zmatt, i was umm.. preplexed
Aug 05 03:16:30 <NishanthMenon> zmatt, it should probably be there somewhere on CDDS or somewhere..
Aug 05 03:17:52 <zmatt> actually we got swpu282y from TI.  I also have swpu282ab because TI accidently made it the public trm on the site for a few days
Aug 05 03:18:54 <NishanthMenon> zmatt, aah you seem to have the newer one then.. you should be able to find references .. though I am pretty sure I have reported a couple of errors in doc. TRM says abb is reserved, actual sample reports abb setup..
Aug 05 03:19:16 * NishanthMenon fighting palladium now :)
Aug 05 03:19:37 <zmatt> uhh, y < ab < af
Aug 05 03:19:57 <zmatt> y and ab are from 2013 and 2014 respectively
Aug 05 03:20:13 <NishanthMenon> zmatt, dang, I am tired...
Aug 05 03:20:20 <NishanthMenon> i should stop opening my mouth anymore..
Aug 05 03:20:45 <zmatt> heh
Aug 05 03:21:20 <zmatt> where did the product page go anyway?  I find it really disturbing that like everything related to omap4/5 has been obliterated from the site
Aug 05 03:22:07 <NishanthMenon> zmatt, i did not dig too deep, i got a contact in actual production support team, so got the latest sample and a board.. so got cracking today
Aug 05 03:22:21 <zmatt> even if the part has been made NRND or inactive, you'd normally expect the docs to remain available still :/
Aug 05 03:22:46 <zmatt> anyway, thanks for the class0 commit!
Aug 05 03:23:17 <NishanthMenon> zmatt, it is not a commit yet :) -> do feel free to review.. been up since 5am.. so my eyes are probably crossed ;)
Aug 05 03:28:53 <zmatt> NishanthMenon: looks okay to me
Aug 05 03:29:00 <NishanthMenon> zmatt, on the list please :)
Aug 05 03:29:25 <NishanthMenon> zmatt, feel free to add your Reported-by: tag as well..
Aug 05 03:29:53 <NishanthMenon> you deserve all the digging to identify this, my side was much easier thanks to your work. it should have right attribution
Aug 05 03:30:10 <zmatt> so, this only sets up ABB right? using the class 0 voltages for the supply rails is still the next step?
Aug 05 03:30:21 <NishanthMenon> zmatt, nope, it sets up both
Aug 05 03:30:33 <NishanthMenon> the avs0 code is already there - thanks to dra7
Aug 05 03:30:36 <zmatt> ahh
Aug 05 03:30:38 <zmatt> right
Aug 05 03:30:47 <NishanthMenon> all i had to really do was tell the code where the efuse regs were
Aug 05 03:31:30 <NishanthMenon> yeah, the voltage dropped to the 1.0v on mpu etc.. nice to finally touch a scope :P
Aug 05 03:35:18 <zmatt> scopework can definitely be fun
Aug 05 03:36:20 <zmatt> I did a fair bit of investigation of power stuff on the beaglebone a while ago... the BBB looked like it was on an intensive care unit or something ;)  https://liktaanjeneus.nl/werk/bbb-pmic-testing.jpg
Aug 05 03:45:14 <NishanthMenon> heh
Aug 05 03:57:38 <zmatt> argh, fun... ddr3 leveling timeouts -.-
Aug 05 04:03:28 <zmatt> ah, lol, I thought I had the cpu board with dual rank memory in here, apparently not
Aug 05 04:37:54 <zmatt> NishanthMenon: okay, I needed to slightly backport it to test it since I'm still using a slightly dated u-boot... it seems to be working
Aug 05 04:38:24 <NishanthMenon> zmatt, neat!
Aug 05 04:38:26 <zmatt> it seems to set mpu and mm voltages 0.01V higher than the efuse values
Aug 05 04:38:37 <NishanthMenon> yeah round up crap
Aug 05 04:38:58 <NishanthMenon> i noticed that as well, 10mV is the step size
Aug 05 04:39:09 <zmatt> how does 1.016 round up to 1.03 ? :-)
Aug 05 04:39:15 <NishanthMenon> regulator driver might be probably having an offby 1
Aug 05 04:39:31 <NishanthMenon> zmatt, 1.016 rounded off to 1.02 +1 step
Aug 05 04:39:34 <zmatt> core voltage is spot-on though curiously
Aug 05 04:39:55 <NishanthMenon> need to check the regulator driver if it is missing something
Aug 05 04:40:13 <zmatt> oh wait never mind
Aug 05 04:40:34 <zmatt> it set the right values, I looked at the wrong spreadsheet column
Aug 05 04:41:19 <NishanthMenon> i thought it had 1 step upstep in measured voltage on my scope,
Aug 05 04:41:33 <NishanthMenon> hmmm... i should have checked the scope against the 5v ref
Aug 05 04:42:25 <zmatt> okay what is this lovely stuff in my boot log... and is it new or not...
Aug 05 04:42:34 <NishanthMenon> ?
Aug 05 04:42:53 <zmatt> async abort during... ahh, I think I can guess
Aug 05 04:44:16 <zmatt> I accidently dumped too many control module registers, and immediately after the region I dumped are some registers that fault on any access
Aug 05 04:44:35 <NishanthMenon> aah
Aug 05 04:44:48 <zmatt> and of course u-boot doesn't bother enabling async aborts, so that remained pending all the way into linux
Aug 05 04:45:18 <NishanthMenon> crap.. i'd have to pull up palmas to see more.. too tired..
Aug 05 04:45:25 <zmatt> oh about palmas
Aug 05 04:46:15 <zmatt> we have the trm and register manual for es2.2, but not the TWL6037B21A1 appnote
Aug 05 04:47:27 <zmatt> we did get the appnote for the ptwl6037ba1 (es2.0 ?), swca145, but that doesn't really quite match the silicon we have
Aug 05 04:48:37 <NishanthMenon> get_offset_code looks interesting
Aug 05 04:49:58 <NishanthMenon> PALMAS_SMPS_BASE_VOLT_UV = 500mV; and start_code is 6
Aug 05 04:51:37 <zmatt> yeah
Aug 05 04:51:56 <zmatt> that agrees with my notes
Aug 05 05:01:06 <NishanthMenon> zmatt, http://pastebin.ubuntu.com/25244889/
Aug 05 05:01:16 <NishanthMenon> ok it does do a round_up only
Aug 05 05:01:35 <NishanthMenon> i was wrong that it had a overstep by 1
Aug 05 05:02:18 <zmatt> yeah it seems to be right
Aug 05 05:03:45 <NishanthMenon> at least the math adds up, i have'nt looked at document to verify if vals still holds good.
Aug 05 05:03:55 <zmatt> do you know if there's a good reason for 500 MHz to be defeatured?  we currently do seem to be using it (once linux takes over)
Aug 05 05:04:11 <NishanthMenon> zmatt, should not be used
Aug 05 05:05:07 <NishanthMenon> zmatt, not really sure about the background.. when I was doing o5, they did want to get opp_low in. but I am guessing product engineering must have overruled marketting
Aug 05 05:05:54 <NishanthMenon> zmatt, typically design goals are set by marketting, designers plan around the range, s/w like me plans around the targets, but final decision lies always with the guys who have to do the mass manufacturing.
Aug 05 05:06:16 <NishanthMenon> i am guessing some temperature range or some reliability constraints might have been the trigger.
Aug 05 05:06:25 <NishanthMenon> if those guys say no, i would not go near it
Aug 05 05:06:37 <NishanthMenon> i thought i kicked it off kernel.org sometime back
Aug 05 05:06:39 * NishanthMenon checks
Aug 05 05:06:40 <zmatt> well apparently it was in es1 but dropped for es2
Aug 05 05:07:25 <NishanthMenon> ok https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap5.dtsi#n45
Aug 05 05:07:27 <NishanthMenon> upstream is clean
Aug 05 05:10:15 <zmatt> heh, I think I've actually been running at 500 MHz almost exclusively so far
Aug 05 05:10:53 <NishanthMenon> zmatt, i am starting to get senile.. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/omap5.dtsi?id=05e7d1a57a268b491d0e24952d219a73c62bd3df
Aug 05 05:11:18 <NishanthMenon> zmatt, it's been 3 years, and i seem to have forgotten why we did it
Aug 05 05:12:52 <zmatt> lack of adequate silicon characterization maybe?  I can imagine that won't have gotten the amount of effort that it would have if TI was still in the mobile market
Aug 05 05:13:26 <NishanthMenon> zmatt, those years were a bit confusing times for all of us.. (cough)
Aug 05 05:13:29 <zmatt> i.e. not sure what the safe voltage would be, therefore just defeature it entirely
Aug 05 05:14:25 <NishanthMenon> zmatt, i'd strongly suggest to drop low..
Aug 05 05:14:40 <zmatt> ok
Aug 05 05:14:57 * NishanthMenon has chased enough of those "out of spec" bugs to know the bugs can be ... umm... painful
Aug 05 05:15:22 <NishanthMenon> just only to hear back "we told you not to use it, did'nt you read the memo"
Aug 05 05:15:30 <zmatt> I guess we'll have to see... people may be willing to incur some stability risk in exchange for battery lifetime
Aug 05 05:15:36 <zmatt> these aren't mission-critical systems :)
Aug 05 05:16:05 <NishanthMenon> zmatt, hehe.. when i was in mobile, my nightmare scenario was "what if my code screwed up when someone was calling 911"
Aug 05 05:16:15 <NishanthMenon> zmatt, now my nightmares are worse though :)
Aug 05 05:16:59 <zmatt> yes I can imagine
Aug 05 05:20:02 <zmatt> I think I actually limited the frequency because these are still the older cpu boards which have slightly iffy PDN resulting in instability at high frequencies
Aug 05 05:20:55 <NishanthMenon> aah i hope you have enough bulk caps at least
Aug 05 05:21:24 <NishanthMenon> there used be some dpll jitter i seem to recollect with less caps and not meeting pdn guidelines
Aug 05 05:23:11 <zmatt> it was deficient in caps :)  there's a pcb revision, but that doesn't help those who currently have prototypes yes
Aug 05 05:23:21 <NishanthMenon> uggh
Aug 05 05:23:25 <zmatt> *yet
Aug 05 05:24:05 <zmatt> we're also still having "fun" with dual-rank memory
Aug 05 05:24:14 <NishanthMenon> heh
Aug 05 05:25:27 <zmatt> and I still need to try to hunt down why that friggin' ABE PLL gets stuck when linux tries to bring it up again after warm reset
Aug 05 05:25:45 <NishanthMenon> that does sound familiar... hmm..
Aug 05 05:26:34 <zmatt> yeah that's what tony said too :)
Aug 05 05:28:06 <NishanthMenon> ARM: OMAP5: Source DPLL_ABE from sys_clk
Aug 05 05:28:45 <NishanthMenon> zmatt, http://gitorious.ti.com/lcpd-agross/omapdrm/commit/b55d24d8b7bcf7bc53261b82de03638daeff91c7
Aug 05 05:29:15 <NishanthMenon> http://gitorious.ti.com/lcpd-agross/omapdrm/commit/21d135673476f98b851a0c4851746cbb18fc1e67 went along with it, i think
Aug 05 05:29:25 <NishanthMenon> at least my x1 search seems to think so
Aug 05 05:30:15 <zmatt> isn't sys_clk the default though?
Aug 05 05:31:01 <zmatt> I'll definitely check that, thanks
Aug 05 05:32:58 <NishanthMenon> http://review.omapzoom.org/#/c/31905/ hmm... seems to have started here
Aug 05 05:33:44 <NishanthMenon> blah blah.. "If I follow correctly 32KHz supplying ABE DPLL was POR for OMAP5. "
Aug 05 05:35:26 <NishanthMenon> http://marc.info/?l=u-boot&m=135961219724289&w=2
Aug 05 05:36:05 <NishanthMenon> zmatt, CONFIG_SYS_OMAP_ABE_SYSCK
Aug 05 05:39:25 <zmatt> thanks for digging this stuff up :)
Aug 05 05:40:04 <NishanthMenon> hey, that topic was easy to search, i think some 200 odd emails popped up on my x1 search
Aug 05 05:40:23 <NishanthMenon> no wonder it still stuck around in my head
Aug 05 05:40:47 <NishanthMenon> brb.. sorry, just got my simvision probes loaded up
Aug 05 05:48:01 <NishanthMenon> back
Aug 05 10:44:31 <alperen> Hi everybody I have one question. I have BBblue and I want to connect my pc. which is my bbblue connect to usb 2.0 or usb 3.0?
Aug 05 20:54:14 <MrCurious> just found this for the BLUE seems super useful https://github.com/kiran4399/bb_blue_api
Aug 06 02:11:53 <sydneythegreat> Hello. I'm new to energia. When I tried to launch it, the splash screen shows up and then disappears. But the program never launches. It was working fine all week. Any suggestions?
**** ENDING LOGGING AT Sun Aug 06 03:00:00 2017