Any ideas on getting the vagrant image working? I assume this is some 
graphics issue in Virtualbox on my system. I run Virtualbox all the time on 
this machine, but it's always a Windows VM on this Linux box. I tried the 
old "nomodeset" in grub on the image but didn't get anywhere with that.

On Sunday, April 21, 2019 at 6:15:49 PM UTC-4, justin White wrote:
>
> That's typically the case with ADC pins because of the hardware ADC in the 
> middle. That does clear up the whole pin thing for the BBB, thanks
>
> A side note from all of that I wanted to get a working environment going 
> but I'm having a little trouble figuring out what gets installed where. The 
> idea at the moment is:
>
> Develop a custom client UI on my AMD64 Linux Mint Desktop
> Run the client UI on an Odroid N2 running Ubuntu Mate, which I realize 
> probably isn't the best place to start since it's a bit under developed as 
> of yet
> Run the Machinekit instance on the DE0/DE10 Nano or BBB
>
> trying to get started with the Odroid, I was looking at the github 
> qtquickvcp and probably started installing the wrong thing on the wrong 
> machine lol. I ran through the whole vagrant setup on the desktop but 
> "vagrant up" just spins up a vbox VM Jessie with no desktop. Tried going 
> into virtualbox and disabling 3d accelleration and deleting the .vagrant 
> folder still no luck.
>
>
>
> On Thursday, April 18, 2019 at 8:22:10 PM UTC-4, Charles Steinkuehler 
> wrote:
>>
>> On 4/17/2019 6:47 PM, justin White wrote: 
>> > I'm still a bit sure of how the modes work because it looks like 
>> > the "BeBoPr Function" for example is using the analog inputs tor a 
>> > thermocouple but analog inputs are only available in mode 0 but GPIO on 
>> > header2 is only available in mode 7. I assumed that the modes were set 
>> for 
>> > the whole header or PRU but now I'm guessing that each pin can be mode 
>> set 
>> > individually? 
>>
>> Yes, each pin has it's own "mode" setting to select among up to 8 
>> independent functions.  All of the digital I/O pins can be GPIO pins, 
>> and each specific pin has various other possible functions (eg: pwm, 
>> uart, i2c, timer, etc). 
>>
>> However, the analog pins are generally dedicated for use as ADC 
>> inputs, so they cannot be arbitrary GPIO pins. 
>>
>> -- 
>> 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