**** BEGIN LOGGING AT Thu Jul 20 03:00:02 2017 Jul 20 03:01:21 Doing it w/ my BBB! Jul 20 03:01:47 I got that darn TMP36 sensor to read me some temps. Jul 20 03:01:48 Boy! Jul 20 03:02:20 It took an older kernel but I got it. Jul 20 03:03:58 I tried it on the BBGW and a 4GB BBB. I had to use the 2GB BBB and kernel 4.4.x. Jul 20 03:04:29 That BBGW got my TMP36 sensor so hot, it "had done" burned me. Jul 20 03:04:33 Yikes is right. Jul 20 03:04:49 ... Jul 20 03:09:37 Now...onto the 4.9.x kernel. Enjoy! Jul 20 03:54:40 Does the 2GB work with the 4.9.x kernel? Jul 20 03:56:16 I saw there was a Stretch console image. I got it downloaded and used the Etcher to write the image to my Micro SD card. Jul 20 03:56:45 I put that SD card in the 2GB BBB and it has done nothing so far. Jul 20 03:56:54 I have been waiting 45 minutes or more. Jul 20 03:57:40 I will try the flasher image later or something... Jul 20 04:01:58 what do you mean "it has done nothing so far" .. it probably just booted fine Jul 20 04:02:09 I have not unplugged it yet. Jul 20 04:02:33 It just uses one LED onboard to blink and my computer has not found it. Jul 20 04:02:48 The BBB usually shuts down first. Jul 20 04:02:53 ? Jul 20 04:03:02 Okay... Jul 20 04:03:18 you realize it's not a flasher right? Jul 20 04:03:27 Yes. Jul 20 04:03:34 What should I expect to happen? Jul 20 04:03:37 to boot Jul 20 04:03:54 So, it is done and I need to unplug it? Jul 20 04:04:00 done with what? Jul 20 04:04:23 I do not know. My desktop computer has not recognized my BBB yet. Jul 20 04:04:39 hmm, via usb you mean? Jul 20 04:04:44 Yes. Jul 20 04:05:32 I thought that was enabled on console images, but I'm not entirely sure since console images are very minimalistic Jul 20 04:06:06 Okay. No issue. I can unplug it and see what happens. Keep in mind, this is the 2GB version. Jul 20 04:06:07 is trying ethernet an option? Jul 20 04:06:16 that shouldn't matter Jul 20 04:06:23 I have ethernet plugged in. Jul 20 04:06:25 especially since it's not a flasher Jul 20 04:07:00 I remember a boot button was part of this equation a while back. Jul 20 04:07:06 so maybe check if it shows up in the table here -> http://beagleboard.org/getting-started#step2 Jul 20 04:07:14 Okay. Jul 20 04:07:28 right, if you have really ancient crap on eMMC then that might be causing boot failure Jul 20 04:07:36 try powering on with the S2 button held down Jul 20 04:07:54 (to force eMMC to be ignored) Jul 20 04:07:59 Okay. Jul 20 04:08:20 It says the site cannot be reached. Jul 20 04:08:30 I will try the S2 button. Jul 20 04:08:32 uhh what? Jul 20 04:08:39 the site is working fine for me Jul 20 04:09:21 The site is there but when I try to go to the board, it says the site is down (meaning my BBB is not recognized). Jul 20 04:09:41 zmatt: How long should I hold down the S2 button? Jul 20 04:10:05 you can let go a few miliseconds after the power led turns on Jul 20 04:10:27 Okay. Jul 20 04:11:05 Well shit hombre. That done did it! Thank you again. Jul 20 04:11:18 maybe wipe your eMMC if there's nothing there you care about Jul 20 04:11:27 How can I do that? Jul 20 04:11:59 Well, none of my LEDs are lit. Dang it. Jul 20 04:12:25 why did you say "That done did it!" then? Jul 20 04:12:50 My computer recognized the BBB and set it up. Jul 20 04:12:58 that sounds promising Jul 20 04:13:06 But...the LEDs are not blinking at all. Jul 20 04:13:08 in fact, that means it has booted Jul 20 04:13:16 oh wait Jul 20 04:13:22 how does it show up exactly? Jul 20 04:13:51 USB serial device. Jul 20 04:14:27 I think I may need to hold the boot button down longer. Jul 20 04:14:45 uh no, it sounds like it booted Jul 20 04:14:58 if it's showing up as USB serial device Jul 20 04:15:05 I just tried to sign on to my board. Jul 20 04:15:12 I am not getting a sign on screen. Jul 20 04:15:27 I am using PuTTY. Jul 20 04:15:27 did the leds do anything at all after power-on ? Jul 20 04:15:33 No. Jul 20 04:15:52 Not when I held down the Boot button. Jul 20 04:16:17 that sounds like the card is just not bootable. are you sure it showed up as usb serial device? Jul 20 04:16:26 Yep. Jul 20 04:16:44 so, those two things make absolutely zero sense in combination Jul 20 04:16:51 Okay. Jul 20 04:17:02 I will try a new SD card. Jul 20 04:17:30 if it's unbootable it may show up as usb network device, but not as usb serial device Jul 20 04:17:40 Hey man. Jul 20 04:17:57 I unplugged it and held the boot button again while I plugged it in. Jul 20 04:18:06 I am getting LED input. Jul 20 04:18:28 The "heartbeat" pattern. Jul 20 04:19:36 that sounds promising Jul 20 04:19:49 It works. I guess things needed to do stuff. Jul 20 04:19:53 Dang! Jul 20 04:20:27 wiping eMMC is done with sudo blkdiscard /dev/mmcblk1 Jul 20 04:20:35 Okay. Jul 20 04:20:37 Thank you. Jul 20 04:21:04 hello Jul 20 04:21:20 after that it should also boot from card if you power on normally, without S2 button Jul 20 04:21:30 Okay. Jul 20 04:22:08 chirag: What projects are you working on? Jul 20 04:22:21 (note: S2 button is only sampled at power-on, not at reboot. the altered boot order is in effect until you power off and on again) Jul 20 04:23:19 Okay so, I can reboot and power down correctly. This will ensure the boot sequence is down correctly for now on. Jul 20 04:25:29 if you power off and on again then the boot order will be { eMMC, μSD, uart, usb } again, but if eMMC has been wiped then it will find no u-boot there and always move on to μSD Jul 20 04:25:52 Awesome! Jul 20 04:26:12 That means whatever is on my SD will be there instead of my eMMC info/data. Jul 20 04:26:15 Cool! Jul 20 04:26:25 Thank you for that bash input. Jul 20 04:27:25 hey zmatt: How can I find out if my eMMC has been deleted? Jul 20 04:27:25 yeah normally it always loads u-boot from eMMC, and u-boot will try to boot linux from μSD first and eMMC second, which is why you can normally boot from card without needing the S2 button... Jul 20 04:27:30 but Jul 20 04:27:40 newer images need a newer u-boot to work correctly Jul 20 04:27:58 so then you get trouble if there's an old u-boot on eMMC Jul 20 04:28:07 did you run the blkdiscard command? Jul 20 04:28:15 So, oh yea. I ran that command. Jul 20 04:28:19 did it give an error? Jul 20 04:28:23 no. Jul 20 04:28:26 then eMMC is wiped Jul 20 04:28:29 Yea... Jul 20 04:28:47 But, how can I see it on my prompt? Jul 20 04:29:15 Like...I know. I saw it in a book I was reviewing earlier today. Jul 20 04:29:32 I was reading this Packtpub.com book. Jul 20 04:29:34 there's not really any simple way to recognize whether eMMC is completely blank, that would require scanning all of it Jul 20 04:29:40 Oh. Jul 20 04:30:21 although if there's no bootloader and no partition table then that's a pretty good hint I guess Jul 20 04:30:54 sudo dd if=/dev/mmcblk1 bs=1M count=1 | hexdump -C Jul 20 04:30:55 I guess Jul 20 04:31:25 Oh. I saw something different. I would have to find it. That would be a while from now. Jul 20 04:31:30 (that does a hexdump of the first 1 MB) Jul 20 04:32:05 Forget I mentioned it. I will trust you. Jul 20 04:32:49 also, since it's not partitioned there will be no /dev/mmcblk1p1 Jul 20 04:33:25 Oh. Jul 20 04:34:22 (but note that blkdiscard itself will not make /dev/mmcblk1p1 go away if it previously existed, for that you need to poke the kernel to reexamine the (now gone) partition table) Jul 20 04:34:37 I guess I was reading that info. a while back. I just reviewed what I read earlier but it was on another subject. Jul 20 04:34:38 Oh. Jul 20 04:35:23 it'll be gone after reboot of course Jul 20 04:35:33 I rebooted. Jul 20 04:35:42 No mas. Jul 20 04:35:44 then mmcblk1p1 should be done Jul 20 04:36:50 so, sudo blkdiscard /dev/mmcblk1p1? Jul 20 04:37:38 Since I have two, right? Jul 20 04:40:05 *gone Jul 20 04:40:15 no, that is not what I said Jul 20 04:40:26 06:20 < zmatt> wiping eMMC is done with sudo blkdiscard /dev/mmcblk1 Jul 20 04:40:53 note the suffix :) Jul 20 04:40:55 or lack of! Jul 20 04:41:45 mornin' veremit Jul 20 04:41:52 moanin' Jul 20 04:43:16 Oh...okay. Jul 20 04:54:20 I just partitioned my BBB to make the SD Card usable. Jul 20 04:54:32 8GB! Jul 20 04:54:41 Look out software! Jul 20 05:41:59 \o/ Jul 20 09:39:52 Hi Jul 20 09:40:18 can sm1 help me? Jul 20 09:42:13 whois sm1 -> 11:42 [freenode] -!- There is no such nick sm1 Jul 20 09:42:26 so probably no, sm1 can not help you. Jul 20 09:43:28 for all others, maybe try to give a meaningful description of your problem? Jul 20 09:52:50 great Jul 20 09:52:55 Hello all, I have a Beaglebone black and installed with Debian IoT image. I'm running few python applications in it. I want to make a new Image with the existing image that should include my python applications and install this image in 100 new BBBs... And few things like ifconfig settings (set a static IP), internet settings and installation of python libraries should be automatically done while the image installation is in progress Jul 20 09:57:57 so basically ask for a way to roll your existing prototype into an installable image, right? Jul 20 10:07:48 exactly Jul 20 10:08:48 Exactly Mr.Josef Jul 20 10:09:30 hehe. no mr needed, and my nickname is just fine. but i'm not the one that is competent to comment on that. Jul 20 10:10:02 ok Jul 20 10:36:23 hi. playing with my new bb green wifi. after boot all four user leds are blinking pairwise. how can i stop that, where does it come from? Jul 20 11:32:13 improper: thats a node.js script Jul 20 11:37:48 improper: can't remember where it lives off hand (I hated it too). It gets launched when node does. Jul 20 11:40:27 improper: along with other node based things like nodeRed Jul 20 11:54:09 hi all, the microsd connector of BBB is obsolete, can someone tell me if the Card Detect line is active high or low? Jul 20 11:54:16 It is called CD Jul 20 11:57:24 it should be apparent from the schematics ... Jul 20 12:16:29 freemor: thanks Jul 20 12:17:20 yw Jul 20 12:17:59 Don't know why they did that.. the default blink functions are much more useful Jul 20 12:31:34 Can anyone suggest a tool to debug spi ? i want to write and read from some address Jul 20 12:59:35 up, up, and far-pay! Jul 20 13:18:15 ver|laptop: cd polarity is also configurable in DT so it doesn't actually matter Jul 20 13:42:03 zmatt: this may interest you, as we've talked about NXP i.MX6's security recently https://blog.quarkslab.com/vulnerabilities-in-high-assurance-boot-of-nxp-imx-microprocessors.html Jul 20 13:47:40 i can't get i2c to work via bonescript. opening the port fails with "Kernel does not include CapeMgr module". see https://gist.github.com/anonymous/ae84340990b96c0f49ffe72254487990 -- what can i do? Jul 20 14:31:14 improper: let's see.. Jul 20 14:31:17 gquere: thanks! Jul 20 14:32:20 :) Jul 20 14:35:08 improper: my first feeling would be an issue in bonescript... try doing i2cget -y 1 0x21 0x0c b Jul 20 14:36:29 (in particular open error suggests a version-incompatibility between kernel and bonescript) Jul 20 14:39:17 gquere: excellent demo of "complexity is the enemy of security" Jul 20 14:40:11 an X.509 certificate parser is not something that belongs in secure bootrom Jul 20 14:41:04 ASN1 parser even Jul 20 14:42:47 in fact the code that implements the root of trust should be absolutely minimal. it actually doesn't even need public-key crypto, that could be deferred to the next stage (which could be replaced in new products if a crippling bug is found in it) Jul 20 14:43:38 all ARM TZ implementations are based on this IIRC Jul 20 14:44:10 hash(pubkey) in eFuse Jul 20 14:44:35 feed cert + signature + image to the bootloader Jul 20 14:44:48 secure boot and TZ are not really related things, you don't need TZ for secure boot Jul 20 14:45:08 but yeah I'm sure it's a common way to implement secure boot Jul 20 14:45:11 that doesn't make it a good idea Jul 20 14:45:37 Heh Jul 20 14:45:53 ah yes ofc, got mixed up in names Jul 20 14:46:04 I really wish I could find someone who'd document a useful implementation of dm-verity Jul 20 14:46:04 thought TZ included TEE + secure boot Jul 20 14:46:10 ( Speaking of secure boot) Jul 20 14:46:21 Because I find the manuals to be lacking at times. Jul 20 14:46:30 gquere: TZ is really just a sort of virtualization Jul 20 14:46:47 yes I remember now, TZ is just the TEE part Jul 20 14:46:56 microkernel and stuff Jul 20 14:47:24 actually coded some stuff on ARM TZ fresh out of school Jul 20 14:47:27 microkernel? Jul 20 14:48:06 IIRC it's a secure microkernel running in // of the normal world (eg android), sharing timeslices Jul 20 14:48:12 no Jul 20 14:49:01 and bus accesses are secured based on which 'kernel' is running atm Jul 20 14:49:44 TZ itself is just the hardware support for having two contexts on the cpu, implemented by having two copies of various registers (e.g. mmu context), a bit in cache tags and such, and included with bus transactions Jul 20 14:50:23 so, in terms of privilege you have secure privileged > secure user and secure privileged > public privileged > public user Jul 20 14:50:37 (secure privileged essentially acts like the hypervisor) Jul 20 14:51:09 there might be some standard "secure monitor" code from ARM also, but at the very least TI isn't using it Jul 20 14:52:39 not sure what the chip was, but I think it was a TI chip Jul 20 14:52:48 TI also seems to have bolted on some stuff to further isolate secure world, so it's more like secure monitor > secure privileged > secure user and secure monitor > public privileged > public user Jul 20 14:53:24 iirc ARM adopted a similar scheme in ARMv8 Jul 20 14:54:08 in plain ARMv7 however secure privileged code has full control of the processor Jul 20 15:44:40 zmatt: yes, it works with i2cget... Jul 20 15:46:10 improper: okay. I don't really know much about bonescript, but my guess would be that you're using an old version of bonescript with a new kernel or vice versa Jul 20 15:49:46 zmatt: using the latest bb green wifi image without any modifications. Jul 20 15:52:27 improper: can you check: apt list bonescript Jul 20 15:52:58 (after doing apt-get update actually) Jul 20 15:56:50 zmatt: bonescript/now 0.5.0-0rcnee17~bpo80+20160709+1 armhf [installed,local] Jul 20 15:57:17 the board did not have an internet connection so far, i might try an apt-get upgrade. Jul 20 15:57:26 latest is 0.6.1-something Jul 20 15:59:27 anyone here used gentoo as a host for initial connection and know if i need more than the instructions here http://elinux.org/BeagleBone_Usb_Networking ? i'm unable to connect with the 192.168.7.2 ip address. Jul 20 15:59:45 what network manager do you use? Jul 20 15:59:51 openrc Jul 20 16:00:51 its the one for their init-script system. Jul 20 16:01:10 let me rephrase: if the usb network interface shows up as link, make sure that the interface is brought up and an ip is acquired via dhcp Jul 20 16:01:39 some network manager will do that automatically by default (e.g. gnome network manager), others might need configuration Jul 20 16:04:22 zmatt: thank you. my mistake. Jul 20 16:05:56 zmatt: and now it works. thank you. Jul 20 18:18:22 Join Jul 20 18:18:35 Hi all Jul 20 18:19:34 Any one have successfully interfaced external RTC with BBB? Jul 20 18:23:59 sure, no problem. never had to wait 5 minutes to get help huh? Jul 20 19:08:12 Hi All, how do i debug spi interface, is there any command line tool for this? or i must code something..? Jul 20 19:18:26 13:59:11 < tbr> http://lmgtfy.com/?q=how+to+use+spidev+from+the+command+line Jul 20 19:25:05 zmatt: tried that, it wasn't too helpfull.. i didn't got an example on this spi-tools stuff Jul 20 19:25:24 also tried to see if someone used it , didn't find any.. Jul 20 19:25:36 i was able to echo something and i've veified it's OK , but how do i read back some value Jul 20 19:30:37 * zmatt tries it Jul 20 19:32:16 it seems to work... not really convenient though Jul 20 19:33:28 I read the id from an spi flash, which is a 2-byte transfer (command byte 0x9f, then a byte during the id is returned), Jul 20 19:33:37 echo -ne '\x9f\x00' | src/spi-pipe -d /dev/spi/flash -b 2 | hexdump -C Jul 20 19:33:55 okay, that's a good example thanks Jul 20 19:34:14 the -b 2 is to get a 2-byte transfer Jul 20 20:23:06 zmatt: if i'm connecting a diffrent PHY (100Mb MII & MDIO ofcourse...) should i change anything in cpsw driver/dt/etc? or i can use the same configuration as with BBB Jul 20 21:10:07 usually not I think **** ENDING LOGGING AT Fri Jul 21 03:00:01 2017