**** BEGIN LOGGING AT Thu Jan 06 02:59:57 2022 Jan 06 03:19:04 hey is there any channel good to ask about more general stuff, say the espressobin ultra? Im having a really vexing problem building u-boot Jan 06 03:24:21 atf-ntim.txt is some file that's missing. anyways i know im off topic but just trying to get a decent lead on this Jan 06 03:30:50 Hello...I do not know much about uboot but I saw a digikey setup of building uboot. Jan 06 03:31:27 Let me see if I can get the link. This may be useful or not. Please hold. Jan 06 03:32:14 hays: I mean, this isn't really the best place for asking about some random board based on some undocumented Marvell SoC no Jan 06 03:32:16 hays: there are often different channels for different board communities ... i'd guess that to be #marvell(if it exists) Jan 06 03:32:26 vagrantc: lol, doubtful Jan 06 03:32:48 Here: https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967#bootloader-u-boot-5 <<< it is older but can be useful? Jan 06 03:32:58 BBB! Jan 06 03:33:02 hays: have you checked http://wiki.espressobin.net/tiki-index.php?page=Build+From+Source+-+Bootloader Jan 06 03:33:09 Oh. It is for another board. Jan 06 03:33:12 Sorry. Jan 06 03:35:40 zmatt: yeah, that's what im working from. Jan 06 03:36:27 hays: it looks like atf-ntim.txt is an intermediate build output Jan 06 03:36:47 hays: you can see it in the build directory listing they're showing on that page Jan 06 03:37:01 yeah, but for some reason its not being created Jan 06 03:38:34 hays: try their forums? http://espressobin.net/forums/ Jan 06 03:38:46 https://github.com/globalscaletechnologies/A3700-utils-marvell/blob/A3700_utils-armada-18.12.0-gti/script/buildtim.sh this is the build script i believe Jan 06 03:39:18 thanks for looking at it. was hopihg it might be something obvious to someone with more experience Jan 06 03:39:31 I'm not familiar with ATF no Jan 06 03:40:01 hays: i'm more familiar, but marvell's build process is ... painful. Jan 06 03:40:14 and atf-ntim.txt appears specific to marvell armada Jan 06 03:41:20 hays: I suggest grepping the source tree to find the makefile that is supposed to produce it, and from there try to figure out why it isn't doing so Jan 06 03:42:01 heh. yeah let me keep grepping.. i've been grepping Jan 06 03:42:09 ill get more fancy with it Jan 06 03:45:31 I mean, it's in the top-level makefile of the atf-marvell source tree Jan 06 04:53:24 zmatt: yep i found it and fixed it Jan 06 04:53:29 thanks for the help Jan 06 10:17:49 Is anyone using the librobotcontrol library currently (or w/ past knowledge) w/ making the BBBlue fly? Where does the receiver fit in w/ PRU attachment? Where does the UART/DSM port on the BBBlue go into on the receiver? Jan 06 10:26:49 This darn receiver is a "DSM" receiver and has the JST-ZH, three-pin connectors on it. Does anything, anything, from the BBBlue get attached to the receiver in the form of JST-ZH connections? Jan 06 11:23:56 what receiver? (part number) Jan 06 11:24:16 OrangeRX R820X V2 Jan 06 11:25:44 Forget it. Something is wrong w/ the BBBlue now. It will not boot when I put USB to the computer from the BBBlue. Boo! Jan 06 11:32:16 cppm or sbus version? Jan 06 11:32:53 No clue. It does not say. Jan 06 11:39:42 it looks like it doesn't output the protocol for which the dsm2 connector is intended... basically, this thing both receives the signal and converts/splits it, while the dsm2 connector is for simpler devices that merely receive the signal (e.g. OrangeRx R110XL)... such receivers can also plug into the "sat 1"/"sat 2" ports of your R820X, which is why those are the same connectors as the dsm2 port on ... Jan 06 11:39:48 ...the blue Jan 06 11:40:36 I just killed off two BBBlue boards. Dang it. Jan 06 11:41:05 maybe you should stop doing that Jan 06 11:42:26 Right! Jan 06 11:43:55 WHelp, time to reflash. Jan 06 11:44:09 Who knows? It could be something faulty. Maybe they are not fried yet. Jan 06 11:54:15 Anyway... Jan 06 11:54:32 @zmatt: Thank you for the R110XL mention. I will look into it. Jan 06 11:56:30 WHelp, new image and no power. This cannot be good. Jan 06 11:57:45 what did you do? Jan 06 11:58:27 I plugged in the BBBlue into the USB port on the host. Jan 06 11:58:37 I mean, what did you do to fry it? Jan 06 11:58:41 It showed no power. I reflashed and then...oh. Jan 06 11:58:55 how did you reflash it if it "showed no power" ? Jan 06 11:59:07 I plugged in the PRU to Signal on the Receiver. Jan 06 11:59:29 No LEDs lit up at all on one board. The second board is powered now via usb. phew. Jan 06 11:59:41 please say words that actually describe what you did Jan 06 11:59:55 you can't plug anything into "PRU", you can only plug things into connectors that exist on the bbblue Jan 06 12:00:09 I made a cable. Jan 06 12:00:10 and the receiver has a whole bunch of possible of connections Jan 06 12:00:15 from what to what? Jan 06 12:01:50 JST-SH (pru BBBlue) to single wire to female connector for Receiver. The female connector was a single wire w/ a female end on it. Jan 06 12:02:10 It fits on the Eight Pin header on the Receiver, i.e. Signal. Jan 06 12:02:41 I think that the Eight Pin Header on the Receiver is signal but at 5v. Jan 06 12:09:22 I also don't understand why you were doing that in the first place, since librobotcontrol doesn't seem to have support for that protocol (unlike ardupilot) Jan 06 12:09:52 but yes, if that's a 5v signal (which you should have checked) then it's quite likely you fried the beaglebone Jan 06 12:10:31 I tried ardupilot. I got upset three years ago w/out support. When I asked for support, one "head honcho" stated they would flag me as SPAM. I grew furious. I just moved on. Jan 06 12:11:28 lol Jan 06 12:11:41 I know. he must have powers on the forums. Jan 06 12:11:42 Blah. Jan 06 12:12:10 not everything is going to have the level of patience with you that I often show you Jan 06 12:12:14 *not everyone Jan 06 12:12:58 Everyone/Everything...Blah. I did not post for two years and then I came back made two posts. SPAM is set_. Ya, ya. All day. Blah. Jan 06 12:13:26 I understand you have patience w/ technical stuff. I am thankful. Jan 06 12:13:43 Two years and two posts and I am spam. That is garbage. Jan 06 12:14:05 And... Jan 06 12:14:10 I mean, it depends a bit on what you posted :P Jan 06 12:14:31 They stopped servicing the BBBlue. I mean, they will not have support for it any longer. Jan 06 12:15:03 They are heading towards STm chips for people to make their own distros of ArduPilo. Jan 06 12:17:22 https://ardupilot.org/rover/docs/common-autopilots.html#common-autopilots Jan 06 12:17:50 number two in the list Jan 06 12:18:25 same for copter: https://ardupilot.org/copter/docs/common-autopilots.html#common-autopilots Jan 06 12:18:41 I see it. If you scroll down on that link and click a link, you end up here: https://discuss.ardupilot.org/t/beaglebone-blue-released-linux-enabled-autopilot-for-80/15772 Jan 06 12:18:55 Let me get the link real quickly that states what I am discussing. Jan 06 12:21:15 Hmm. See. He removed his posts that were against me and my wants involving the Build on the BBBlue and blah, blah, blah. Jan 06 12:21:30 Now, I am making things up. Argh! Jan 06 12:25:15 Anyway, I tried w/ ardupilot. Chatted w/ a bunch of "people" and got nowhere. Jan 06 12:25:39 It was a time. The time was interrupted by things not working well for me. Jan 06 12:26:21 The only time ardupilot worked for me was when I pushed the mode button on the BBBlue and had librobotcontrol work! Jan 06 12:29:09 and ... : https://discuss.ardupilot.org/c/hardware-discussion/linux-autopilots/111 seems a bit absent. Jan 06 12:31:16 @zmatt: Anyway, let me get ready for this glorious day. I get to play in dirt again! Yay and yah! Jan 06 12:32:13 So, dumbing it down is what I do. You are patient w/ this fact but I have to play this way or I get ramshafted into doing less than dirt work, i.e. if that is possible. Jan 06 12:32:32 no sleep and ramshaft dirt work here I come! Jan 06 13:47:09 hi Jan 06 13:47:14 i have problem Jan 06 13:47:49 i set setenv serverip 192.168.27.1 Jan 06 13:48:10 and setenv ipaddr 192.168.27.2 Jan 06 13:48:28 i can ping the server from u-boot Jan 06 13:48:48 but the server can't ping beaglebone Jan 06 13:49:11 so what should i do Jan 06 13:49:12 ? Jan 06 13:49:13 ? Jan 06 13:49:14 ? Jan 06 13:49:15 ? Jan 06 13:59:50 ? Jan 06 14:38:38  what commands are you using? at both ends Jan 06 15:20:01 I don't think u-boot is pingable Jan 06 15:20:42 I don't think it even acquire an ip address until it actually attempts to do the tftp boot Jan 06 15:22:09 I could be wrong Jan 06 15:26:04 hmm, maybe I spoke too soon, looks like it ought to be pingable once network is up Jan 06 15:26:24 oh he left anyway Jan 06 19:26:03 you know, when a feature is added to a peripheral or subsystem I think you can usually take a decent guess why it was deemed a useful thing to add Jan 06 19:28:10 ... but I'm really having a lot of trouble with coming up with any ideas why on earth in PRUSS IEP (a timer/capture peripheral or sorts) they added a read-only view to the capture timestamp registers which... bit-reverses every byte Jan 06 20:23:18 hi guys, quick question, i would like one of my systemd service not to start untill /dev/pwm/ehrpwm1a is present. I pretty sure the way to do it is ENV{SYSTEMD_WANTS}="powersaving.service" in udev, but i don't know in which file i do need to uperate. any suggestion Jan 06 20:24:15 i am running in BB-AI, pwm is loaded by this in uEnv: uboot_overlay_addr1=/boot/dtbs/4.19.94-ti-r70/overlays/BONE-PWM2.dtbo Jan 06 20:24:56 ok forget the string "pwersaving.service" this is just a string that remained there Jan 06 20:25:29 there are two ways to do that actually, you can indeed have an udev rule request your system service to be started, or alternative you can add a dependency on the device in your system service file Jan 06 20:26:55 better the second, so i keep the config in just one file. Let me see googling .... because i think i tried that another time and it did not work Jan 06 20:27:57 hmm, looks like the device doesn't get tagged by default, so a bit of udev will be needed regardless Jan 06 20:29:15 hold on, let me test something Jan 06 20:30:05 okis ! thanks zmatt Jan 06 20:43:44 nmingotti: https://pastebin.com/byzebjj6 Jan 06 20:44:41 nmingotti: this makes each pwm visible as a systemd unit, e.g. "dev-pwm-ehrpwm1a.device", on which you can add a dependency Jan 06 20:45:46 cool ! thank you again, let me study it and make some test :) Jan 06 20:45:46 I don't quite know how systemd handles that, since it can't know in advance that such a device will even appear, but iirc it does in fact work... hopefully I don't misremember Jan 06 20:47:25 systemd for me is black magic, i never had time to dig into how it works. it is very useful, i use it, but really: blackbox Jan 06 20:50:39 yeah, this is the magic: "devices are exposed in systemd as .device units. They exist primarily to order stuff properly at boot, for example so that we can fsck/mount a block device only after it has shown up. As such device units are primarily useful as a synchronization concept: you enqueue a job for a device which isn't around yet, and the job will succeed as soon as it shows up" Jan 06 20:52:22 so adding Wants=dev-pwm-ehrpwm1a.device and After=dev-pwm-ehrpwm1a.device will create a start-job for dev-pwm-ehrpwm1a.device (unless one is already in progress) and orders the start of your service after it Jan 06 20:53:49 even though systemd doesn't know anything about that device yet, it allows this anyway and the job will sit in the queue until either 1. udev discovers the device and tells systemd to create the actual device unit (which completes the start job) or 2. the start job times out Jan 06 20:54:47 that's not *that* magical I think Jan 06 20:56:51 or at least, it's exactly the right amount of magical to make device units actually useful ;) Jan 06 21:06:43 thank you for the description ;) I mean when i was using cron, rc.local and init scripts it was all much easier to understand. Now it is more powerful, but also considerably more complex. And the feeling, to be honest, at time, is that i don't have full control of the machine. Since once I had to write code, to write the logic, not i have to write Jan 06 21:06:44 declarative configurations. well ... it works well, so i will not complain much ;) Jan 06 21:19:03 I honestly didn't find the old pile of shell scripts much clearer Jan 06 21:21:29 I mean, I don't see the distinction you're making... even sysv init scripts had some declarative syntax for the purpose of declaring dependencies, it was just really crude Jan 06 21:22:34 it's also kinda like a makefile Jan 06 21:23:51 though it does have a rather large amount of options, which is great if you need those specific pieces of functionality, but it can definitely be overwhelming Jan 06 21:25:36 btw, if you ever get confused by what's happening, don't forget you can change the log level of systemd on the fly (and also at boot time using a kernel cmdline parameter) to see in more detail what it's doing e.g. with job management Jan 06 21:27:16 about 15 years ago we were using mostly rc.local to config servers, it was really easy and we knew for sure the order in which things will happen. Of course, this was useful for servers since the bootup time is mostly irrelevant. But for a phone or a multimeter the bootup phase must be quick, so, our simple approach is really unfit. But as i said, Jan 06 21:27:16 i don't dislike the new system. Jan 06 21:27:31 config the boot process, of course Jan 06 21:28:27 and it was working mostly cross platform, i remember we had serveral Debian, ScientificLinux, FreeBSD and OpenBSD Jan 06 21:29:51 ok, i will look into che kernel parameter for systemd log details, seems interesting Jan 06 21:41:23 systemd.log_level=debug Jan 06 21:42:53 hmm, current systemd also has "systemctl log-level" to get/set systemd's loglevel, but it appears the systemd on debian buster is too old to have that Jan 06 21:43:28 but you can send systemd SIGRTMIN+22 to change its loglevel to debug and SIGRTMIN+23 to restore the loglevel to its configured value Jan 06 21:45:28 e.g. sudo kill -RTMIN+22 1 Jan 06 21:49:32 those udev rules show up doing systemd-analyze? Jan 06 21:49:48 all units show up in systemd-analyze Jan 06 23:37:24 hey zmatt, i got it working, finally the fan cape turn on only when temperature is > 75 and shuts down most of the time. The service start happily at boot with systemd, so finally my problem with the FanCape is solved :) without your assistance this would have been impossible, thanks again Jan 06 23:39:06 the BB-AI is now silent, i can happily work near it and i don't risk it shuts down for overheating (it was happening often) Jan 07 00:19:18 I missed everything! Dirt in my lungs. Yay! Jan 07 00:19:28 BBB. Sorry. Jan 07 00:31:37 set_, it is a subject started days ago, before the 30 Dec i guess ;) Jan 07 00:32:05 long story short, i also have the BBB since a long time, now trying the BB-AI which is more powerful but also heats a LOT Jan 07 00:32:43 bought FanCape, problem it is super noisy => impossible to reach the author is in holiday => i made my pwm to control the FanCape fan speed Jan 07 00:33:17 => needed to run the script that control it via systemd at boot, that required help from udev, this is the part i made today Jan 07 00:34:05 Nice! Jan 07 00:34:27 Does it work? Jan 07 00:34:30 now time to bed for me, in Moscovian holiday it is late night and if my wife wakes up she will be pretty much furious Jan 07 00:34:37 YES :) working Jan 07 00:34:46 Nice! Double Nice. Jan 07 00:34:49 Okay. Jan 07 00:34:56 Well, if you have to go, I must go too. Jan 07 00:35:07 Dirt is not going to make itself. Jan 07 00:35:13 okis, c u ! Jan 07 00:35:17 Dang it. Sorry. Still cloudy! Jan 07 00:35:18 bye all Jan 07 00:36:10 nmingotti just liked me. It was awesome. Jan 07 00:36:15 I feel it, man. Jan 07 00:36:18 I feel it. Jan 07 02:12:10 For when you get around to it, @zmatt, were you being serious about that odd piece of add-on to the OrangeRX, i.e. R110XL? Jan 07 02:12:34 B/c...I will try it. GenTooMan knows Jan 07 02:56:04 * GenTooMan wonders what set_ is frying. Jan 07 02:57:15 zmatt: thanks for the help the other day. is it ok if I occasionally ask questions here or would you prefer i take them elsewhere Jan 07 02:58:33 Hamburgers! Jan 07 02:59:27 Fried cheese alawishious! I am building my squad up, toughness. BBB style. I just typed that out. Yes sir! **** ENDING LOGGING AT Fri Jan 07 02:59:57 2022