**** BEGIN LOGGING AT Wed Oct 18 03:00:01 2017 **** BEGIN LOGGING AT Wed Oct 18 07:36:32 2017 Oct 18 08:16:43 Hi everybody Oct 18 08:16:56 I have a question about uEnv Oct 18 08:17:37 (1) if i press S2 on boot then uEnv is loaded from SD card Oct 18 08:18:14 (2) If i reboot still uEnv, is loaded from SD Oct 18 08:18:52 (3) if i remove energy to the BBB then, uEnv, on next boot, is loaded from eMMC (internal memory BBB) Oct 18 08:18:58 if you hold S2 down during *power-up* (not reboot), then u-boot will be loaded from SD for every boot Oct 18 08:19:16 nope, i just tested, see point (3) Oct 18 08:19:30 until next power-up Oct 18 08:19:41 the S2 button state is sampled at power on Oct 18 08:20:25 So, my question is, is there some way to make BBB take uEnv permanently from the SD card ? Oct 18 08:20:40 you keep saying uEnv when you mean u-boot Oct 18 08:21:08 u-boot loads the uEnv from the linux system it boots Oct 18 08:21:17 sorry for sloppy language, I am not a guru of BBB, i read part of Molloy book, that'all Oct 18 08:21:31 and yes, wiping eMMC or at least the u-boot that resides there will do the trick Oct 18 08:22:22 sudo dd if=/dev/zero of=/dev/mmcblk1 seek=256 count=1 should suffice Oct 18 08:22:58 if you want to wipe eMMC entirely, that can be done with sudo blkdiscard /dev/mmcblk1 Oct 18 08:23:19 zmatt, you are really a master !! Oct 18 08:25:07 :) Oct 18 08:25:31 or, i could write my SD card into eMMC Oct 18 08:25:59 . Oct 18 08:26:42 do you have a link to guide me through this ? I saw Molloy page but it says i need to download a flasher image. Is there another way? I have already a nice image redy;) Oct 18 08:26:42 yes, you can turn the SD card into a flasher which will reflash eMMC Oct 18 08:27:27 https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC Oct 18 08:27:53 ok, let me check ! Thank you ! Oct 18 08:28:20 note that after this the card will no longer boot as a normal system, it will always reflash eMMC. to undo this you'd need to edit the /boot/uEnv.txt that resides the card again (using some other linux system) Oct 18 08:28:57 be sure to check (e.g. with df -h / ) that there isn't too much data on the card to fit eMMC Oct 18 08:36:57 from "df" I read : /dev/mmcblk0p1 3.3G 2.2G 871M 72% / Oct 18 08:36:57 Oct 18 08:37:12 ok, good! Oct 18 08:37:25 eMMC can contain 4G, correct ? Oct 18 08:38:21 4 marketing-GB, so about 3.5G Oct 18 08:40:25 you should write a book ! I would buy it:) Oct 18 08:40:35 I suck at writing documentation Oct 18 08:41:13 Hey, i could write, problem is, I am not native eng. speaker;P Oct 18 08:42:01 ok, 3 2 1 ... i try the flashing Oct 18 08:43:27 what should i send via i2c2 to get the data of a cape? Oct 18 08:43:54 leds are flashing in "supercar" (Kinght Riders) way Oct 18 08:44:03 Parduz: "the data" ? Oct 18 08:44:08 nmingott: then it's flashing Oct 18 08:44:56 @zmatt: yes, the content of the EEPROM which identifies a Cape Oct 18 08:45:18 oh, you should be able to inspect that via sysfs Oct 18 08:45:35 check /sys/bus/nvmem/devices/ maybe Oct 18 08:46:51 no... i need to test the i2c2 communication, and i have the cape as a ready "slave" Oct 18 08:47:19 so my question is "what message (command, address, etc) should i send to get an answer" Oct 18 08:50:36 check datasheet of the eeprom? the address will also depend on address lines of the eeprom Oct 18 08:52:05 Maybe i'm not understanding how it works.... to have the data sent back from the cape, is'nt the BBB sending "something" to it at the boot? Oct 18 08:52:52 uhh, well every i2c transaction involves a request from the BBB Oct 18 08:53:23 I don't know the four addresses it checks for CAPE eeproms off the top of my head, but you can find that in the SRM Oct 18 08:54:43 ...going looking at it again, then.... Oct 18 09:10:29 zmatt: it worked ! Oct 18 09:10:54 yay \o/ Oct 18 09:27:04 I have another question, can i plug in the SD card when BBB is running ? Oct 18 09:27:16 sure Oct 18 09:27:38 be sure to unmount before removing though Oct 18 09:28:04 ok, I wanted to be sure not to damage the BBB Oct 18 09:28:45 so, now i can go commenting out the flasher config. in uEnv Oct 18 09:29:06 thank you a lot for your help zmat ! c u Oct 18 09:29:06 yes Oct 18 09:29:21 @zmatt: maybe i'm missing something, but the SRM talks about addresses of the eeprom (the whole chapter 8.2) but still i don't get how to retrieve them via i2c... Oct 18 09:30:24 sorry ... how to retrieve the data having the address Oct 18 09:32:45 if you connect it to a BBB you can use the kernel driver and access the eeprom via /sys/bus/nvmem, if you want to know the actual i2c transaction format you should check the eeprom datasheet to be certain, but I'm pretty sure it's a write of the 2-byte address followed (using repeated START-condition) by a read of as many bytes as you want Oct 18 09:35:09 ah.... that is perhaps what i'm missing. I was thinking that i needed some sort of "command" (like in a protocol) to get the data.... Oct 18 09:35:30 i'm too much used to high-level programming. Going to try it now. Oct 18 09:35:33 thanks Oct 18 09:35:58 well, the particular i2c transactions required to read and write the eeprom form a protocol Oct 18 09:36:08 it's just a really simple one since the eeprom's "API" is really simple Oct 18 09:36:51 true. :) Oct 18 09:38:08 for i2c memories it's common to use write{ offset, data } for writes and write{ offset }, read{ data } for reads Oct 18 09:38:26 also for the register space of many other i2c devices Oct 18 09:39:29 offset is often 1-byte in the latter case, but the eeprom is bigger than 256 bytes and needs a 16-bit offset Oct 18 09:41:42 ok.... i'm learning from you, right now .... one question: what's the START condition you mentioned? Oct 18 09:41:56 might want to read up on i2c in general Oct 18 09:43:06 guess so : Oct 18 09:43:08 every i2c read or write consists of a START, then 7-bit slave address + read/write bit, ack bit from slave, then zero or more { data byte, ack bit } Oct 18 09:43:09 :) Oct 18 09:43:43 finally either a STOP, which releases the bus, or again a START to immediately perform a second transfer Oct 18 09:44:23 START and STOP are particular ways of toggling the lines that isn't like a data bit Oct 18 09:45:02 this is more low-level than you actually need to worry about in linux userspace though :) Oct 18 09:45:45 /sys/bus/i2c/devices/1-0050/eeprom FTW! Oct 18 09:46:17 that or the related /sys/bus/nvmem/devices/*/nvmem Oct 18 09:46:47 iirc the former is only readable by root by default while the latter can be read by anyone Oct 18 09:46:49 yeah Oct 18 09:47:23 um no, i think its only root writeable Oct 18 09:47:34 both are only root writeable of course Oct 18 09:48:05 just checked, you're right. by default eeprom is 600 Oct 18 09:48:45 I have to drive an old custom keyboard with leds. It is a keymatrix read by an ATMEGA; i need to learn how to get the pressed keycodes and how to switch the leds, via i2c. So perhaps i need to go deep in the i2c. Oct 18 09:49:17 i2c isn't very complicated Oct 18 09:49:31 (unless you have timestretching) Oct 18 09:49:40 then... everything is complicated :P Oct 18 09:49:46 :) Oct 18 09:49:46 that still isn't complicated from a software point of view :P Oct 18 09:49:57 hrhr Oct 18 09:50:34 even without clock stretching, i2c controllers are a popular peripheral to get fucked up by hardware designers Oct 18 09:50:55 TI's is buggy, broadcom's is buggy, ST's is buggy Oct 18 09:52:14 TI's is okay to deal with as long as you only use it in master mode Oct 18 09:54:08 broadcom's (on the rpi) is the only one I know of that really fucks up in the face of clock stretching Oct 18 11:19:22 off air 192.168.7.1 Oct 18 11:19:39 off air 192.168.7.2 Oct 18 11:21:47 Who can help me? Oct 18 11:22:05 192.168.7.2 off air Oct 18 11:23:23 http://www.catb.org/esr/faqs/smart-questions.html Oct 18 11:25:15 192.168.7.2 does not enter Oct 18 11:33:49 192.168.7.2 off air Oct 18 11:36:13 can you help me Oct 18 11:37:34 souzamembro: once you manage to ask a meaningful question, somebody probably will. until then - no. Oct 18 11:42:25 help Oct 18 11:43:29 HEELP Oct 18 11:43:38 Help Oct 18 11:44:11 192.168.7.2 off air Oct 18 11:44:16 souzamembro: last warning. please ask a meaningful question, or be silent Oct 18 11:45:08 hi is it necessary to disable emmc on bbb if i need to use spi1? Oct 18 11:45:55 only if the pins conflict with the eMMC pins Oct 18 11:47:39 bg: looks more like you need to disable HDMI to use SPI1 Oct 18 11:47:46 Hi, how do I access the ip 192.168.7.2 / Oct 18 11:47:49 spi0 should work directly Oct 18 11:48:16 souzamembro: 192.168.7.2 is the ip that the bbb exposes when you use usb networking Oct 18 11:48:19 souzamembro: which beagle do you have? Oct 18 11:48:40 i already disable hdmi, but the spidev1 is not loaded during boot Oct 18 11:50:21 please do not privmsg people! Oct 18 11:50:37 hi there i just sended a message but i'm not sure it has been send becaus i had a problem... Oct 18 11:50:59 beagle bone black rev A Oct 18 11:51:30 souzamembro: which linux distribution / image is the BBB running? Oct 18 11:52:45 also i'm booting on emmc, do i need to be in microSD? before i can use spidev? Oct 18 11:54:02 bg: no, but did you modify uenv to load the SPI1 virtual cape? Oct 18 11:54:18 yeah, i already did. Oct 18 11:55:01 tbr: it's taking too long to get in Oct 18 11:55:17 souzamembro: do the LEDs blink? Oct 18 11:55:43 i'm using the v4.4.91 kernel and this the line were I enable the spidev1 cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1 Oct 18 11:55:51 am i missing somthing here? Oct 18 11:55:52 tbr: yes Oct 18 11:56:27 souzamembro: is the BBB attached by USB to a computer? Oct 18 11:56:53 tbr: yes Oct 18 11:56:54 So i got a problem with my beagle, she starts within 30 secs if she is connected with an RJ45 cable but it takes 1 min 30 secs to boot without any RJ45 connected... i took both kern logs with and without RJ45 connected: with: https://pastebin.com/KVAdvSC9 and without: https://pastebin.com/YmxGziGA Oct 18 11:57:14 souzamembro: which OS is that computer running? Oct 18 11:59:03 tbr: windows 8.1 Oct 18 11:59:30 Gignjrome: the answer is not in the kernlog but in the system logs. So most likely in systemd journal. Oct 18 12:01:48 :tbr Ok i'll look inside those logs... thank you for this answer! i'll come back if don't find anything! Oct 18 12:02:01 souzamembro: well, now there are two questions 1) which distribution is the BBB running 2) did you install the drivers for the BBB? Oct 18 12:04:06 tbr: 1) element14 2)yes Oct 18 12:06:31 tbr: Can you access the 192.168.7.2 ? Oct 18 12:06:35 element14 is a company. I was asking about the linux distribution aka IMAGE Oct 18 12:07:08 does the windows PC recognize the BBB and show additional network devices? Oct 18 12:09:40 tbr: I can not access the internet ip 192.168.7.2 by browser Oct 18 12:10:06 that does not answer my question Oct 18 12:10:59 tbr: yes Oct 18 12:11:00 and that's not an internet IP, that's a local network IPv4 address. This address is local to the BBB *if* it's running connected via USB to a computer. Oct 18 12:12:37 tbr: OK Oct 18 12:16:07 tbr:when access 192.168.7.2 says it took too long to respond Oct 18 12:16:23 12:07:08< tbr> does the windows PC recognize the BBB and show additional network devices? Oct 18 12:17:10 tbr: Yes Oct 18 12:20:34 souzamembro: then check the status of those devices, make sure they are active and check if they have IPv4 addresses assigned Oct 18 12:20:50 169.254.x.x/16 is invalid Oct 18 17:08:44 evnin'....(o; Oct 18 17:09:37 just received my bbbw today and its kernel crashes after booting up.... Oct 18 17:09:50 regardless booting debian 9.1 amor eMMC or microSD card... Oct 18 17:10:15 s/amor/from/ Oct 18 17:16:29 eh, that's not how it's sp'osed to be :D Oct 18 17:16:40 i can imagine (o; Oct 18 17:16:47 long time i used a bob.... Oct 18 17:16:53 the rev c Oct 18 17:16:59 and this worked perfectly... Oct 18 17:17:53 do you have UART output from it? Oct 18 17:17:58 somewhere i have the output of it.... Oct 18 17:18:14 i've used part only so far.... Oct 18 17:19:18 https://pastebin.com/zd976LAW Oct 18 17:21:02 * davorin downloading the 9.2 iot image now.... Oct 18 18:02:32 hmm, that looks like the kernel blows up hard Oct 18 18:03:11 hmm...running now on 9.2-iot Oct 18 18:03:12 wlcore: ERROR SW watchdog interrupt received! starting recovery. Oct 18 18:03:22 but so far no kernel crash after a minute Oct 18 18:03:36 the 9.1 image was with x11 Oct 18 18:03:49 ah now it freezes Oct 18 18:03:54 usr0 led stopped Oct 18 18:06:04 no joy... Oct 18 18:06:10 hardware is fecked... Oct 18 18:11:09 hmm...now booted fmor emmc again...so far no crash (o; Oct 18 18:18:10 still running.... Oct 18 18:18:24 i think i know what is was... Oct 18 18:21:26 how are you supposed to use connmanctl and connect to an SSID with a space in it? Oct 18 18:23:25 ah stupid me... Oct 18 18:44:40 ah stupid farnell... Oct 18 18:44:55 shipped a cc2640 launchpad instead of ti dlp evm Oct 18 18:45:13 or ti fecked it up, as it is labelled dlp evm on top, and cc2640 on bottom... Oct 18 19:13:38 davorin: that's next level of "special"... Oct 18 19:13:57 that's why i ordered the bbbw Oct 18 19:14:06 as the dlp evm plugs directly onto it...bugger... Oct 18 19:14:16 davorin: you could always poke RCN and jkridner about the crashes Oct 18 19:14:24 ah..crashes gone (o; Oct 18 19:14:28 you know what it was? Oct 18 19:14:32 sounds stupid... Oct 18 19:14:40 stupid reasons are the bestest Oct 18 19:14:41 the bbbw comes with two short wires as antennas Oct 18 19:14:48 they were to close to the pcb ;-) Oct 18 19:14:58 ah, EMI :) Oct 18 19:15:09 probably same cause as i got first some flaky hdmi output Oct 18 19:15:23 * tbr tries to memorize that for the next time it comes up Oct 18 19:15:28 now booter form sd card and reflashed 9.2 onto emmc Oct 18 19:15:36 well, the BBB is not the best design on earth regarding EMI Oct 18 19:15:41 it's rather noisy Oct 18 19:15:42 (o; Oct 18 19:15:53 there is soon a new member? Oct 18 19:15:57 like rpi zero? Oct 18 19:16:15 small and good iot modules are hard to find... Oct 18 19:16:43 especially when you want to avoid unsupported allwinner/mediatek platforms (o; Oct 18 19:17:01 and openwrt gives me the shiver... Oct 18 19:17:15 * davorin works in iot business... Oct 18 19:17:53 you forgot rockchip Oct 18 19:18:01 (o; Oct 18 19:18:40 sadly most "IoT" or rather "embedded" is pretty much fire-and-forget-and-also-never-ever-update-again Oct 18 19:19:09 right... Oct 18 19:19:25 or contain a soc, which hardware watchdog has a bug....like carambola2 Oct 18 19:19:36 and support says: use an external watchdog (o; Oct 18 19:19:48 poke any embedded linux and you're sure to find a zoo. heartbleed, krack, kernel RCEs, etc Oct 18 19:20:30 hey, there are 4-bit micro-controllers that are dirt cheap and could to that watchdog thing :D Oct 18 19:20:38 right ;-) Oct 18 19:20:42 ne555 as well Oct 18 19:20:55 right, no need to actually be digital Oct 18 19:22:02 are there still 4-bit controllers like the old cop400? Oct 18 19:23:23 I think there's *one*. some funky japanese part, but dirt cheap. I don't remember the details right now Oct 18 19:23:33 (o; Oct 18 19:24:24 could be the epson S1C60 Oct 18 19:26:18 what are you using bbb for? Oct 18 19:27:30 at the moment my ancient BeagleBoneWhite is running as a 6LoWPAN-to-Ethernet router Oct 18 19:27:42 remarkably well actually Oct 18 19:28:02 ah...also using wsn? Oct 18 19:28:13 started now with riot-os.... Oct 18 19:28:43 I hacked up some stuff based on the old contiki fork for CC2530 Oct 18 19:29:08 running on batteries? Oct 18 19:29:48 we have an offer fmor a company charging 400k for a wsn based on msp430 and cc1101 Oct 18 19:29:53 s/fmor/from/ Oct 18 19:29:58 the max voltage on those was a bit weird, so I resolved to just run them off 3.3V regulators. Most of them fed by a 5V wall-wart Oct 18 19:30:09 ah right... Oct 18 19:30:26 seems all wsn projects are hard to tweak for low power Oct 18 19:30:48 well the older 8051 based CC25xx stuff was weird anyway Oct 18 19:31:02 the cc2538 was the first ARM M3 Oct 18 19:31:31 the CC2630 is an M3 and a saner design, but I didn't get around to play with it, at all Oct 18 19:32:31 think there is cc2538 support in riot-os Oct 18 19:32:50 no radio support for cc2650/cc1350 yet... Oct 18 19:33:16 but for stm32 nucleo boards and microchip miwi modules Oct 18 19:33:39 it's a shame ST killed the STM32W Oct 18 19:34:56 also fun tidbit: the silicon for all CC26xx is identical. CC2650 has all fuses open, all the "lower" parts have various restriction fuses blown to limit bluetooth, 802.15.4, rffoo, etc Oct 18 19:35:18 interesting (o; Oct 18 19:36:27 kinda like the stm32 series now....also as chepa boards are available... Oct 18 19:36:45 2morrow i should receive some max32625 mini boards...or pico, how maxim calls them Oct 18 19:37:02 they claim, as all manufacturers calim, ultra-low-power with high performance (o; Oct 18 19:37:27 maxim, ewww, that should be a firing offense to design in ;) Oct 18 19:37:39 but has a similar controller with more security features added ... Oct 18 19:37:46 hey, maxim still send sfree samples (o; Oct 18 19:37:54 yes, great for hobby Oct 18 19:38:25 wonder how much arm makes in license fees a year (o; Oct 18 19:38:35 sure not the same figure as oracle (o; Oct 18 19:40:02 my bbbw still runs (o; Oct 18 19:42:47 hey also renesas does 4-bit micros Oct 18 19:47:01 ah right... Oct 18 19:47:12 dunno know much about renesas though.. Oct 18 19:47:31 arent't they used mainly in plcs? Oct 18 20:51:50 Hi, Beagle/Programming Idiot here. Have goggled and fiddled around a while. I have the BB Blue and the EDuMIP robot kit and am working with my grandson as a project I can and have: connected to wifi flashed image to SD card and can boot up can use cloud 9 to some degree can use the LED.py and flash.py to control the onboard LEDs so I know i have some level of communication I cannot control motors, neither the motors.py, encoder.py or Oct 18 20:52:55 I cannot control motors, neither the motors.py, encoder.py or balance.py do anything the error I am receiving is: ---------------------------------------------------- Your code is running at http://localhost. Important: use os.getenv(PORT, 8080) as the port and os.getenv(IP, 0.0.0.0) as the host in your scripts! Process exited with code: 0 ------------------------------------------------------- I do not know how to change port or Oct 18 20:53:22 I do not know how to change port or host, i have looked at https://wiki.debian.org/HowTo/ChangeHostname but not sure that is the way to go Thanks for any input and abuse Oct 19 01:04:29 https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#i_take_full_responsibility_for_knowing_my_beagle_is_now_insecure Oct 19 01:04:30 ... Oct 19 01:04:47 This should let us know about how to make sure we have no passwords, right? Oct 19 01:04:51 ... Oct 19 01:05:23 I wanted to make sure b/c I just directed someone here, to that site, that needs to not have a password on boot. Oct 19 01:17:33 Does anyone use pusher w/ their Bone? I am asking to see if people are collecting data and if so, what type of data would be nice to collect w/ this "IoT" instance in Python? Oct 19 01:18:18 For instance... Oct 19 01:18:59 Blah. Oct 19 01:19:21 I am going to try and collect temp. data. Oct 19 01:20:44 ... Oct 19 01:21:01 Has anyone sold temp. data before or used it in another application? Oct 19 02:39:30 Could I get some help enabling UART4 on the beaglebone? Oct 19 02:40:45 or any other uart, really, I just want an exposed uart port. Oct 19 02:41:13 kernel version 4.9.56-ti-r70 Oct 19 02:42:12 seems like there's a while bunch of outdated info? or I'm not sorting through it properly. **** ENDING LOGGING AT Thu Oct 19 03:00:01 2017