[beagleboard] Driver beagleboard win 7 64 bits

Bonjour à tous, J'ai deux PC dont un portable, tous les deux avec WIN7 SP1 64 bits sur le PC Bureau pas de problèmes tout fonctionne parfaitement, sur le portable win 7 ne veux pas installer les drivers pour la BBB, rien à faire j'ai tout essayer ??? quelqu'un peut-il m'aider?? -- For more op

Re: [beagleboard] Re: How to make a python program start on boot? May need to use sudo.

For debugging u can redirect the output into a file, eg: * * * * * root /usr/bin/python /home/debian/Desktop/SimB.py >> /home/debian/err.txt 2>&1 (write this all in one line) However, if your program is an X program the error will be something like: "cannot open display" But: All Window Managers

Re: [beagleboard] Driver beagleboard win 7 64 bits

You might get an answer if you translate this On 4/17/2016 4:48 AM, Constant François wrote: > Bonjour à tous, > > J'ai deux PC dont un portable, tous les deux avec WIN7 SP1 64 bits sur > le PC Bureau pas de problèmes tout fonctionne parfaitement, sur le > portable win 7 ne veux pas installer les

[beagleboard] Re: Beaglebone and Chromebook connection

I can confirm that when I connect the beaglebone to the chromebook and power up the chromebook, the network never comes up, but if I get an update on the chromebook and can 'soft' reboot it without shutting down the beaglebone, when the chromebook comes back up, the network is up. If there was

Re: [beagleboard] Re: How to make a python program start on boot? May need to use sudo.

Really good idea evilwulfie. That, xwindows, sounds like the problem. Now I'm thinking that I should put a startup icon on the Debian desktop to start my program, since I know that I can start it with the terminal program with sudo python myProgram.py. That has always worked, whereas I cannot

Re: [beagleboard] Re: How to make a python program start on boot? May need to use sudo.

random infos http://stackoverflow.com/questions/637005/x-server-running On 4/16/2016 8:35 PM, John Baker wrote: > Really good idea evilwulfie. That, xwindows, sounds like the problem. > > Now I'm thinking that I should put a startup icon on the Debian > desktop to start my program, since I know

Re: [beagleboard] Re: How to make a python program start on boot? May need to use sudo.

I just now discovered the problem requiring sudo to start my python program. It's related to PyBBIO library code to write to the PWM interface on the BBB. I am trying to find out if there is a way around this requirement (to run the code as root) but I may be stuck with it. :-( I get a permiss

Re: [beagleboard] Re: Beaglebone and Chromebook connection

The trick is creating a network route to the USB gadget. If you are familiar with a unix style command line, the tools are there to mount the 192.168.7.x network in the Chrome OS terminal. I am travelling and don't have access to my BBB, but I'll try later when I have physical access, rather than

Re: [beagleboard] How to make a python program start on boot? May need to use sudo.

OK, so you need to learn about unix groups. In essence, you need to create a group, say “cape” and then make your userid a member of this group. After that, do the following: sudo chown root:cape /sys/devices/bone_capemgr.9/slots Now, as a member of the group “cape”, you are permitted to write

Re: [beagleboard] Using Connman for WiFi AP/tether...

On Sat, Apr 16, 2016 at 5:35 PM, Jason Kridner wrote: > > > On Wednesday, March 9, 2016 at 2:05:47 PM UTC-5, Brian Anderson wrote: >> >> >> >>> >> Drop dnsmasq/create_ap, add back udhcpd >>> >> >> Just curious, why udhcpd rather than dnsmasq? Isn't dnsmasq supposed to >> be "light weight"? Err,

[beagleboard] Re: Super Advanced audio / media system using Beaglebone Black

We have now added info for hooking up the CODEC to the Beaglebone, its pretty easy. But one must use our linux software thats soon to be provided to the BBB comunity by us. On Saturday, April 2, 2016 at 1:44:42 PM UTC-4, J dog wrote: > > > > We have added some additional info on software topo

Re: [beagleboard] BBB Battery shutdown

So no one has any idea ? I'm looking for the module, that traps power events, and shuts down the BBB. All I need is a file name. It's pretty hard making sense of the mess that is /drivers/mfd, and the documentation does not seem to be helpful either. Documentation/power/regulator/charger-managemen

Re: [beagleboard] BBB Battery shutdown

Oops, I mistyped: Documentation/power/charger-management.txt. Sorry about that. Regards, John > On Apr 17, 2016, at 2:37 PM, William Hermans wrote: > > So no one has any idea ? I'm looking for the module, that traps power events, > and shuts down the BBB. All I need is a file name. It's pre

Re: [beagleboard] BBB Battery shutdown

>From /kernel/power/poweroff.c /* * When the user hits Sys-Rq o to power down the machine this is the * callback we use */ do_poweroff() Which then call the following sequence: kernel_power_off() //kernel/reboot.c machine_power_off() //kernel/reboot.c pm_power_off() omap_rtc_power_off() //d

Re: [beagleboard] BBB Battery shutdown

So in the TPS65217 datasheet, Section 9.3.7, it says in interrupt is generated when pushbutton is pressed/released and USB and AC voltage status change. Look at the interrupt handler and see how this is implemented. Regards, John > On Apr 17, 2016, at 2:37 PM, William Hermans wrote: > > So

Re: [beagleboard] BBB Battery shutdown

The best person to ask would be Nishanth Menon mailto:n...@ti.com>> or Anilkumar Ch On Apr 17, 2016, at 2:37 PM, William Hermans wrote: > > So no one has any idea ? I'm looking for the module, that traps power events, > and shuts down the BBB. All I need is a file name. It's pretty hard making

Re: [beagleboard] BBB Battery shutdown

Never mind, I found it. drivers/mfd/tps65217.c line 164 Regards, John > On Apr 17, 2016, at 2:37 PM, William Hermans wrote: > > So no one has any idea ? I'm looking for the module, that traps power events, > and shuts down the BBB. All I need is a file name. It's pretty hard making > sens

Re: [beagleboard] BBB Battery shutdown

I guess I should have read your explanation more closely. OK the interrupt routing issues a key input which replicates the power button being pushed. Not sure if this is what you want, or if you want to stop this from happening when when the AC power is removed. Regards, John > On Apr 17, 2

Re: [beagleboard] BBB Battery shutdown

https://github.com/torvalds/linux/blob/master/drivers/mfd/tps65217.c#L164 Nothing there at line 164, then on line 165 starts a function. Which contains the code I linked to yesterday. Which is the power push button code. Which again, is not helping . . . So let's walk through that function. Which

Re: [beagleboard] BBB Battery shutdown

OK, I see the problem. The file I was looking at is different to the one you linked to. I am using the 4.1.13-ti-r33 kernel, which means that you are missing a patch. Build your own kernel and then look at this file again. Regards, John > On Apr 17, 2016, at 3:55 PM, William Hermans wrote:

Re: [beagleboard] BBB Battery shutdown

I have to say, this code is very painful reading. Every single bit I've read so far is circular code in nature. I've yet to find a bit of code that actually does anything obvious. Meaning, someone has attempted to be clever by creating function, after function that calls yet more functions written

Re: [beagleboard] BBB Battery shutdown

I'll *NOT* be using a TI kernel, period. On Sun, Apr 17, 2016 at 4:02 PM, John Syne wrote: > OK, I see the problem. The file I was looking at is different to the one > you linked to. I am using the 4.1.13-ti-r33 kernel, which means that you > are missing a patch. Build your own kernel and then l

Re: [beagleboard] BBB Battery shutdown

The patched code is easier to read Regards, John > On Apr 17, 2016, at 3:55 PM, William Hermans wrote: > > https://github.com/torvalds/linux/blob/master/drivers/mfd/tps65217.c#L164 > > > Nothing there at line 164,

Re: [beagleboard] BBB Battery shutdown

static irqreturn_t tps65217_irq(int irq, void *irq_data) { struct tps65217 *tps = irq_data; unsigned int int_reg = 0, status_reg = 0; tps65217_reg_read(tps, TPS65217_REG_INT, &int_reg); tps65217_reg_read(tps, TPS65217_REG_STATUS, &status_reg); if (status_reg

Re: [beagleboard] BBB Battery shutdown

Apply this patch: >From 51b4d415971bb052a26938791337d1050bf94748 Mon Sep 17 00:00:00 2001 From: Robert Nelson Date: Mon, 26 Oct 2015 11:42:13 -0500 Subject: [PATCH 8/9] tps65217: Enable KEY_POWER press on AC loss / PWR_BUT This is an adaption to v3.14.x of the original patch by Andrew Bradford

Re: [beagleboard] BBB Battery shutdown

Yeah I recognize that code from source code not written by TI employees. The file is called tps65217_charger.c, and is written by an employee of another company. Anyway, I think we're going to blow this off. The idea was to wait around without power for 5 minutes, to see if power comes back up. Be

Re: [beagleboard] BBB Battery shutdown

The real reason why our source trees do not match up. My source tree is based on 4.1.x, and yours seems to be 3.8.x. The patch you showed above would probably botch up my source tree . . . On Sun, Apr 17, 2016 at 4:33 PM, William Hermans wrote: > Yeah I recognize that code from source code not w

[beagleboard] mcasp0

Say you want to use the mcasp0 interface but you don't want to use all the pins P9_25 GPIO3_21Allocated mcasp0_pinsAUDIO DIGITAL IN P9_28 SPI1_CS0Allocated mcasp0_pinsAUDIO DIGITAL OUT P9_29 SPI1_D0 Allocated mcasp0_pinsAUDIO FSK P9_31 SPI1_SCLK Allocated mca

Re: [beagleboard] BBB Battery shutdown

Nope, mine is based on 4.1. This patch was adapted by Robert from code that was written for 3.8. Regards, John > On Apr 17, 2016, at 4:52 PM, William Hermans wrote: > > The real reason why our source trees do not match up. My source tree is based > on 4.1.x, and yours seems to be 3.8.x. Th

Re: [beagleboard] BBB Battery shutdown

Yep, it is in the BB kernel: https://github.com/RobertCNelson/bb-kernel/blob/am33x-v4.1/patches/beaglebone/dts/0006-tps65217-Enable-KEY_POWER-press-on-AC-loss-PWR_BUT.patch

Re: [beagleboard] BBB Battery shutdown

Sorry, that should have read line 75 in the patch file, line 164 in the source code. BTW, this was something I was going to work on but thanks to you I now have a handle on this. Regards, John > On Apr 17, 2016, at 4:52 PM, William Hermans wrote: > > The real reason why our source trees do

Re: [beagleboard] BBB Battery shutdown

Interesting. Too bad if you want the battery to act as a UPS it cant some how notify the kernel that AC has been removed and have a routine to just chill a while to see if power comes back. Be nice to have a variable that is user settable for the time between loss of AC and shutdown. As it is no

Re: [beagleboard] BBB Battery shutdown

Yep, you need a hardware state machine to monitor the power source. I don’t use batteries as I use supercaps which are just big enough to power the board during shutdown. When the power returns, I restart the board. There are a few corner cases that occur, such as when the power comes back on du

Re: [beagleboard] BBB Battery shutdown

One more thing, the power down sequence uses the RTC framework (described earlier in this thread), so it will be possible to set a timer for the shutdown and the wait for the power to return event to cancel the timer. If the power on event does not occur, the shutdown will occur. Regards, John

Re: [beagleboard] BBB Battery shutdown

Where in the code do you set that timer ? On 4/17/2016 7:50 PM, John Syne wrote: > One more thing, the power down sequence uses the RTC framework > (described earlier in this thread), so it will be possible to set a > timer for the shutdown and the wait for the power to return event to > cancel t

Re: [beagleboard] BBB Battery shutdown

Look at drivers/rtc/rtc-omap.c omap_rtc_power_off_program() Regards, John > On Apr 17, 2016, at 10:25 PM, evilwulfie wrote: > > Where in the code do you set that timer ? > > > On 4/17/2016 7:50 PM, John Syne wrote: >> One more thing, the power down sequence uses the RTC framework (describ

Re: [beagleboard] BBB Battery shutdown

There is no timer in that code. The timer would have to be added, and careful consideration would have to be given to exactly how that was implemented. So in other words, you would, or should write a completely new kernel module, that is meant to replace what already exists - As an option. On Sun