**** BEGIN LOGGING AT Thu Apr 19 03:00:06 2018 Apr 19 07:14:57 hiiii team Apr 19 07:15:32 i need help regarding selecting board to buy Apr 19 07:18:07 is their any buddy ? Apr 19 07:19:13 mani__: once you ask a menaingful question, there might be an answer. :) Apr 19 08:00:42 hiii Apr 19 08:01:01 i want to buy a beagle bone, which one u suggest ? Apr 19 08:09:40 whichever one most suits your needs Apr 19 08:10:04 (as long as it's not the beaglebone green wireless. don't get that one.) Apr 19 10:56:53 Hello to all. I would like to ask if someone have experience with AM335X module with no TI SDK? Apr 19 11:02:53 most people here probably have no clue what the "TI SDK" is Apr 19 11:02:59 so, yes Apr 19 12:00:52 tbr, Thanks for answer.. Sorry I wrong formulated the question. I was meaning if there is someone that used one of the AM335X modules, with TI Linux SDK, not beaglebone distribution. I would like to understand if the kernel and the libraries are well supported and have experienced using high level languages interfacing with physical pheriperials like serial, usb, GPIO, Ethernet Apr 19 12:13:09 so the opposite Apr 19 12:13:19 I don't think there are many people here Apr 19 12:14:17 and if you want to know about TI SDK features, you probably best ask your FAE or sales contact at TI Apr 19 12:29:56 tbr, Yes, local reseller doesn't have enaught deep knowledge in the domain I'm asking for. I'm searching someone that already developed on this platform and could give some feedback on the learning curve and possible difficulties for high level packages to interface downstream. Apr 19 12:30:52 TI SKD have proprietary system and a Linux SDK available. i'm interested in the latter. Apr 19 12:33:28 if Linux, why TI SDK? I can't think of a value proposition. Apr 19 12:35:47 TI offer a Linux SDK where you can find kernel, os and libraries, plus different tools that help development on their modules. Apr 19 12:45:59 apparently not that much help, since you're asking here ;) Apr 19 12:58:09 zmatt, yes.. I know this IRC is beaglebone topic, but is the nearest related to Sitara processor in the IRC server... AFIK Apr 19 13:00:38 LucaVanzin: seriously that sounds very much like "TI handed us this super cool SDK and claimed it offers kernel, os, libs, everything. But we have no idea on how to use it, and TI is not being helpful, neither is our distributor." Apr 19 13:00:55 LucaVanzin: but in the end, thats their job, as you supposedly pay them. Apr 19 13:04:23 see, they even have a wiki page: http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Getting_Started_Guide Apr 19 13:05:30 LetoThe2nd, honestly this is your interpretation, in mymind it sounds like asking to people to kindly share their experiences. A reseller is a businness man and unless you buy a hundred boards is difficult they give you more information that the one you find yourself in the datasheet. Anyway that was just to ask for someone that have already hands on. Apr 19 13:08:58 LucaVanzin: well. fact is, that you're not even asking a specific question. like "we totally want to use haskell as a high level language to provide a http api", but only vague "we want to interface to peripheral from high level languages." so thats not gonna buy you any help in an IRC channel. second is, like you mentioned yourself: this is the beagleboard channel, and our focus is 99.9% the debian Apr 19 13:09:04 distribution that is recommended to use ... Apr 19 13:09:06 ... with it. and theres a reason it is recommended: there are people that can help you with it. Apr 19 13:09:55 LucaVanzin: so while i totally understand that the situation is frustrating for you, the chances that anybody here will step up to do the initial support and handholding that TI is supposed to do are close to 0. Apr 19 13:11:10 and if that doesn't fit your needs, maybe rethink using the sitara and ti sdk stuff. Apr 19 13:11:27 LetoThe2nd, Yes I came here already aware of this, but it was worthing a try before to buy a dev kit. And yes I'm referring to my self because I have any organisation behind myself. Apr 19 13:12:09 well then the advice is totally super clear: don't use it, get a run off the mill beagle and use debian on it. Apr 19 13:15:36 well there may be reasons for using it, but the information basis is a little thin right now ;) Apr 19 13:17:12 LetoThe2nd, thanks for your advice. I tried already different platforms like raspberry PI and EspressoBin. Now I want to try TI processors but I also would like to have a more robust hardware and some pheriperial that beaglebone doens't provide. I found some board that can fit my needs, and where you can plug TI SOM. Apr 19 13:17:30 LucaVanzin: you're being super vague again. Apr 19 13:18:24 the missing link is: what are you actually trying to do Apr 19 13:18:35 LucaVanzin: if you would only say "i want to use the fooboofrizll peripheral", then maybe somebody could tell about its support state in linux Apr 19 13:19:05 LetoThe2nd, for example screw supply connector and 9-36V range. mPCIE connector with sim socket, UART with RS232 level... Apr 19 13:21:09 the mpcie should be a geneirc thing, and the rest is not even software related. Apr 19 13:23:36 so sorry, but should we read you question as "how can i interface to a 9-36V power supply connector from a high level language? and to a rs232 port?" Apr 19 13:24:14 is related to what i want to do and to my initial question. I think this irc channel is not excluusively software related, but since you use a hardware board, you sure have some hardware related topics Apr 19 13:25:18 the closest thing that i can see is the am5728 based idk by ti. which in turn ist just a beagle-x15 with some fancy industrial peripherals. Apr 19 13:25:34 so i basically have to assume that you are talking about that. Apr 19 13:25:37 LetoThe2nd, not much fair your comment.., you are just putting together pieces of the discussion... Apr 19 13:27:07 LucaVanzin: it might sound sarcastic, but i'm actually just trying to pull some relevant information out of your nose. we're still at "high level language an peripherals", and the only peripherals that you actually mentioned are not in the least software related, hence doesn't matter if ti sdk or something else. Apr 19 13:27:32 but then ... *shrug* Apr 19 13:31:47 let thanks for the link. I'll look for it. Apr 19 13:32:00 LetoThe2nd, thanks for the link. I'll look for it Apr 19 14:24:30 hi i enabled all the gpio pins . but serial communication is not happening Apr 19 14:24:53 UART communication is not working can you help me Apr 19 14:41:08 Nagarjuna: Tell us more about what you did exactly? Apr 19 15:03:27 i did enabled all gpio purpose in my boot file uncomment to the eMMC line Apr 19 15:04:44 now beaglebone os is running in SD card . than after in boot file enable all uart services Apr 19 15:04:58 uboot_overlay_addr4=/lib/firmware/BB-UART4-00A0.dtbo uboot_overlay_addr5=/lib/firmware/BB-UART5-00A0.dtbo Apr 19 15:06:11 like that way after rebooting serial communication is working but gpio pins are not working P8_7,P8_9, and some of the pins Apr 19 15:08:06 when i was #uboot_overlay_addr4=/lib/firmware/BB-UART4-00A0.dtbo Apr 19 15:08:09 #uboot_overlay_addr5=/lib/firmware/BB-UART5-00A0.dtbo Apr 19 15:09:31 this way gpio pins are working but i was uncomment to that lines than after gpio pins are not working but serial communication is working fine at that time Apr 19 15:11:46 Nagarjuna: If you enable any overlays in uEnv.txt, the "universal cape overlay" is no longer loaded, since it would conflict. So you either need to do everything in overlays, or do everything using the universal overlay (e.g. using config-pin) Apr 19 15:12:17 Nagarjuna: I believe that the UARTs are enabled by default by the universal overlay, and you only need to configure their pins to uart mode to make them work (e.g. using config-pin) Apr 19 15:12:50 I'm a complete idiot and cannot figure out how to load a cape that will enable RTS/CTS on UART2. Can anyone walk me through this. I think half my issue is that 90% of the beaglebone information and how to's are obsolete. Apr 19 15:14:14 #cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-UART2 after comment also its not working Apr 19 15:16:39 grossman83: You could try configuring the pins using "config-pin", that *might* be enough. If actual device-tree changes are needed to the UART module itself, you'll need to build a custom dt overlay (which breaks config-pin, since that needs the universal cape overlay, which conflicts with other overlays) Apr 19 15:16:59 Nagarjuna: bone_capemgr is deprecated with current image versions Apr 19 15:17:43 kk and one more thing is uboot_overlay_addr1=/lib/firmware/BB-UART1-00A0.dtbo is shall i do comment or uncomment Apr 19 15:18:01 there is a .dtbo in /firmware named BB-UART2-RTSCTS-00A0.dtbo that should do what I want I just cannot figure out how to get it loaded Apr 19 15:19:51 I've edited the uEnv.txt file ... particularly this line ###Custom Cape dtb_overlay=/lib/firmware/BB-UART2-RTSCTS-00A00.dtbo Apr 19 15:20:11 naturally the dtb_overlay line is not commented out with the ###'s Apr 19 15:20:40 there is all this talk about slots all over the internet, but it doesn't seem that they're used anymore Apr 19 15:52:33 so where would I find the latest kernel for the beagle black? Apr 19 15:57:38 TonyTheL1on: there are various kernel series Apr 19 15:58:27 hmmm Apr 19 15:58:37 iirc you can update to the latest kernel within the series you're using with: sudo /opt/scripts/tools/update_kernel.sh Apr 19 15:58:46 ah ok Apr 19 15:58:47 you can also pass it arguments to select a different series Apr 19 15:59:00 is there a reason to switch series? Apr 19 15:59:52 well if you want "the latest" then you don't want to stick with a particular series forever Apr 19 16:00:06 e.g. from 4.9-ti to 4.14-ti Apr 19 16:00:08 ah i see Apr 19 16:00:37 so I have 4.9-ti, but I want to go to 4.14-t (which I assume is the latest) Apr 19 16:00:43 so what args do I pass to that scritp? Apr 19 16:00:43 but such a switch incurs some risk of incompatible changes, hence it won't upgrade to a newer series by default Apr 19 16:00:52 oh Apr 19 16:00:57 maybe then its not such a great idea Apr 19 16:01:08 I'll just upgrade to the latest in my series for now Apr 19 16:01:11 4.9-ti to 4.14-ti is pretty minor though I think Apr 19 16:01:39 I'm using 4.14 anyway (though 4.14-bone actually... or more specifically a 4.14-bone with custom patches and custom config, but I digress) Apr 19 16:03:15 for now I'll stick to 4.9-ti Apr 19 16:03:18 latest of that Apr 19 16:03:57 if you want to switch at some point, the option is --lts-4_14 Apr 19 16:04:20 note that you can switch back just as easily with --lts-4_9 so there isn't really any risk in trying 4.14 Apr 19 16:04:41 I might just try it then Apr 19 16:05:25 upgrading to the latest 4.9 was only a small patch Apr 19 16:22:55 zmatt: I note that the 4 Apr 19 16:23:04 4.14 kernel is not PREEMPT Apr 19 16:39:10 eh? that sounds implausible Apr 19 16:40:23 zmatt: its not in the startup message anymore, just says SMP now Apr 19 16:40:26 huh wth Apr 19 16:40:41 how/when/why did that happen o.O Apr 19 16:40:45 also its kinda slower than the 4.9 (at least vim is) Apr 19 16:41:53 disabling PREEMPT might affect user interface responsiveness. I'm trying to see if I can figure out what happened with the PREEMPT Apr 19 16:42:52 huh, it doesn't seem to be a recent thing Apr 19 16:42:58 I'll mail rcn to ask what's up with that Apr 19 16:44:31 same for 4.14-bone ... how odd Apr 19 16:45:22 mail sent Apr 19 16:45:29 ok thanks, let me know what they tell you Apr 19 16:45:32 i'm curious too now Apr 19 16:45:42 I never noticed since I use my own config anyway Apr 19 16:46:11 so you compiled your own kernel for this? Apr 19 16:46:13 there are of course the -rt kernels, but that's kinda excessive for most applications (and decreases efficiency) Apr 19 16:46:45 sure, using rcn's convenient scripts which create the patched kernel source tree, compiles it, and builds debian packages Apr 19 16:47:18 nice Apr 19 16:57:05 have an app where i'll need PREEMPT (audio processing with jack). Apr 19 16:57:15 hard rt isn't necessary tho Apr 19 17:02:54 PREEMPT is normally enabled on beaglebone kernels, I'm puzzled why it isn't on the 4.14 series... it might just be an accident Apr 19 18:06:33 Question: Is there an industrial version of the PocketBeagle? Specifically i'm looking for one that's rated for -40C operating temperature Apr 19 18:56:56 Has anyone modified u-boot to read initrd, vmlinuz, etc. off of an attached SSD drive? Apr 19 18:57:33 Or knows how to boot a beagleboard-x15 off an SSD drive? Apr 19 19:48:16 I'd like to start experimenting with the PRU Apr 19 19:48:32 go for it! Apr 19 19:48:33 Where do I start? All the documentation seems outdated and not a single example will work Apr 19 19:49:07 What driver is the way to go? UIO, remoteproc or friends? Apr 19 19:49:14 you can choose between using uio-pruss or remoteproc-pru, you need to enable one or the other in /boot/uEnv.txt Apr 19 19:49:37 Are the driver readily available on the default Debian image or do they require separate compiling? Apr 19 19:50:30 they're part of the standard beaglebone kernels (remoteproc-pru is only in -ti kernels, uio-pruss in both -ti and -bone kernels) Apr 19 19:51:06 for uio-pruss I've made a python library to load programs onto pru and interact with them, along with a bunch of examples: https://github.com/mvduin/py-uio/#uio_pruss Apr 19 19:51:27 (it can load both plain binaries produced by pasm and ELF executables produced by clpru) Apr 19 19:52:37 Which driver do you prefer? Apr 19 19:53:00 uio-pruss obviously Apr 19 19:53:06 What made you choose for UIO for Py-UIO Apr 19 19:54:49 py-uio wasn't initially made for pruss at all, so that question doesn't make sense. I wanted a python library for uio, so there's no choice between uio and anything else in that case :) Apr 19 19:55:21 as for uio-pruss vs remoteproc-pru, uio-pruss gives more control and less hassle Apr 19 19:55:50 Oh, thanks! Apr 19 19:56:14 remoteproc-pru might be useful e.g. if you want to make some combination of a kernel driver + pru firmware that interacts with it Apr 19 20:17:52 Have u experimented already with DMA between main processor and PRU>? Apr 19 20:53:57 you mean DMA between ddr3 memory and pruss memory? Apr 19 20:54:30 (or probably more specifically from ddr3 memory to pruss memory, since the other direction isn't very useful) Apr 19 20:54:43 no I haven't Apr 19 20:59:55 afk for a bit **** ENDING LOGGING AT Fri Apr 20 03:00:01 2018