$ cat /etc/dogtag
Machinekit Debian Image 2017-07-26

machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$
 
uname -a
Linux beaglebone 4.4.68-ti-rt-r112 #1 SMP PREEMPT RT Sun Jul 23 12:27:13 
UTC 2017 armv7l GNU/Linux

machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$
 
./run.py
loading cramps2_cape.bbio... P8_07 pinmux file not found!
WARNING: GPIO pin not exported, cannot set direction or value!
sudo: no askpass program specified, try setting SUDO_ASKPASS
Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P8_07_pinmux/state
machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$
 

On Thursday, July 27, 2017 at 5:40:17 PM UTC-4, Daren Schwenke wrote:
>
> It probably does.  It's just hard to configure headless, without a 
> connection, using connman (which I've never done).
> We can come back to that.  It seems to recognize the wilink device fine, 
> so the rest is just mechanics.
>
> In the mean time I've brought up the BBG instead and opened ssh to it. 
>  I'll send the address privately.
>
> On Thursday, July 27, 2017 at 5:24:45 PM UTC-4, Charles Steinkuehler wrote:
>>
>> Are you using the image Robert created? 
>>
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2017-07-26/machinekit/bone-debian-8.9-machinekit-armhf-2017-07-26-4gb.img.xz
>>  
>>
>> ...I'd hope that has the proper setup logic to handle the BBG/BBGW. 
>>
>> On 7/27/2017 3:28 PM, Daren Schwenke wrote: 
>> > Well the ethernet over usb isn't coming up like it should, I can't seem 
>> to get 
>> > wireless configured via connmanctl via scripts, and my serial->usb 
>> thingy has 
>> > gone missing. 
>> > So I've been going back and forth editing the ssd config files booting, 
>> shutting 
>> > down, then reading the logs... this is getting old. 
>> > 
>> > The ethernet over usb appears to configure itself in the logs on the 
>> BBGW, and 
>> > on the PC side they get created as eth6 and eth7, but they don't get an 
>> IP assigned. 
>> > Assigning one manually doesn't work. 
>> > 
>> > On Wednesday, July 26, 2017 at 11:15:21 PM UTC-4, Daren Schwenke wrote: 
>> > 
>> >     I did (cross compiling), but honesty I can't remember what i had 
>> setup. I'll 
>> >     add swap. 
>> > 
>> >     On Jul 26, 2017 21:27, "Charles Steinkuehler" <
>> [email protected] 
>> >     <mailto:[email protected]>> wrote: 
>> > 
>> >         On 7/26/2017 8:15 PM, Daren Schwenke wrote: 
>> >          > Thank you all... 
>> >          > You are doing *me* a favor, not the other way around. 
>> >          > 
>> >          > I'll have a BBGW and BBG loaded up and ssh-able for you 
>> gents as soon 
>> >         as I can 
>> >          > open the ports on my "idiot proof" router. 
>> >          > Likely it will be 2am or tomorrow at this point though, but 
>> still.. 
>> >         Faster. 
>> >          > 
>> >          > Plan is follow Robert's instructions, expand / to fill two 
>> 16gb SD 
>> >         cards, assign 
>> >          > static IP's, and put them on the network. 
>> >          > Given the intent is to make an image, I should probably 
>> ask... 
>> >         Should I even 
>> >          > expand to fill 16gb? 
>> > 
>> >         Partition size (beyond 4G) is not really significant.  The 
>> image needs 
>> >         to be created from original sources, so the important part is 
>> to get 
>> >         things working, then we can figure out how to merge any 
>> required 
>> >         changes into the image build scripts (and the ~4GB images they 
>> use 
>> >         when building from scratch). 
>> > 
>> >          > Anything else specific you need to this goal, speak now. 
>>  (like swap, 
>> >         or a local 
>> >          > i7 cross compiling linux host) 
>> > 
>> >         I always add 1-2 GB of swap (depending on the uSD size), but 
>> it's 
>> >         probably not a huge issue in your case.  Cross compiling is 
>> nice, but 
>> >         likely more trouble than it's worth unless you already have 
>> something 
>> >         setup. 
>> > 
>> >         -- 
>> >         Charles Steinkuehler 
>> >         [email protected] <mailto:[email protected]> 
>> > 
>> >         -- 
>> >         website: http://www.machinekit.io blog: 
>> http://blog.machinekit.io 
>> >         github: https://github.com/machinekit 
>> >         --- 
>> >         You received this message because you are subscribed to a topic 
>> in the 
>> >         Google Groups "Machinekit" group. 
>> >         To unsubscribe from this topic, visit 
>> >         
>> https://groups.google.com/d/topic/machinekit/RrNLUo4ASP4/unsubscribe 
>> >         <
>> https://groups.google.com/d/topic/machinekit/RrNLUo4ASP4/unsubscribe>. 
>> >         To unsubscribe from this group and all its topics, send an 
>> email to 
>> >         [email protected] 
>> >         <mailto:machinekit%[email protected]>. 
>> >         Visit this group at https://groups.google.com/group/machinekit 
>> >         <https://groups.google.com/group/machinekit>. 
>> >         For more options, visit https://groups.google.com/d/optout 
>> >         <https://groups.google.com/d/optout>. 
>> > 
>> > 
>> > -- 
>> > website: http://www.machinekit.io blog: http://blog.machinekit.io 
>> github: 
>> > https://github.com/machinekit 
>> > --- 
>> > You received this message because you are subscribed to the Google 
>> Groups 
>> > "Machinekit" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email 
>> > to [email protected] 
>> > <mailto:[email protected]>. 
>> > Visit this group at https://groups.google.com/group/machinekit. 
>> > For more options, visit https://groups.google.com/d/optout. 
>> > 
>>
>>
>> -- 
>> Charles Steinkuehler 
>> [email protected] 
>>
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to