Hi William,
can you please elaborate on the purpose for the cape-overlay you have
written.How did you compile and pushed it into the beagleboneblack?Where
did you place the compiled .dtb/.dtbo?
On Thursday, July 28, 2016 at 4:02:40 PM UTC+5:30, William Hermans wrote:
>
> I use sublime text 3.
I use sublime text 3. And no device tree syntax is nothing like python.
On Thu, Jul 28, 2016 at 3:30 AM, Jane wrote:
> Can you name the editor?Is the dt is also like python where the Tabs and
> special character may ruin its compiling?
> Also does dtc compiler checks
Can you name the editor?Is the dt is also like python where the Tabs and
special character may ruin its compiling?
Also does dtc compiler checks for the sanity of the file besides checking
these tabs,syntax,etc.I mean what if it compiles fine but there is an issue
in the dt?
Also can you
Note the structure here form this modified file( Modified from Charles S'
Universal IO overlay 'univ-all' ) This is for a single pin instead of all
pins.
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/univ-all-00A0.dts
IN short here is what is required:
- /dts-v1/;
-
Hi Greg,
Thankyou for the elaborative post and the link you sent.My understanding is
mainly theoretical and inlined with what you wrote..
Yes,I have been scanning across many links on google and stack overflow but
not able to find single one convincing.
I came to conclusion that i will write a
Hi,
I have been following this famous link from Robert Nelson for kernel
building : https://eewiki.net/display/linuxonarm/BeagleBone+Black
I have been reading and trying the concept of Device Tree for a new Driver
i am writing.To start with I tried to build a sample dts
file( leds-ns2.dts)
I'm looking to install node-red-node-beaglebone on 2016-03-27 image. These
instructions seem clear:
cd ~/.node-red (which would be /root/.node-red)
sudo npm install -g --unsafe-perm node-red-node-beaglebone
Although I note that the instructions to edit ~/.node-red/settings.js and
un-comment
> On Oct 27, 2015, at 14:37 , Robert Nelson wrote:
>
> On Tue, Oct 27, 2015 at 4:21 PM, Rick Mann wrote:
>> I was looking to resize the partition on my little SD card so I could use
>> the whole thing. I'm following the instructions here:
>>
>>
Meant to add: but it seems to have worked.
> On Oct 28, 2015, at 03:05 , Rick Mann wrote:
>
>
>> On Oct 27, 2015, at 14:37 , Robert Nelson wrote:
>>
>> On Tue, Oct 27, 2015 at 4:21 PM, Rick Mann wrote:
>>> I was looking
> On Oct 27, 2015, at 14:37 , Robert Nelson wrote:
>
> On Tue, Oct 27, 2015 at 4:21 PM, Rick Mann wrote:
>> I was looking to resize the partition on my little SD card so I could use
>> the whole thing. I'm following the instructions here:
>>
>>
I was looking to resize the partition on my little SD card so I could use the
whole thing. I'm following the instructions here:
http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD
According to mount, my rootfs is:
/dev/mmcblk0p1 on / type ext4
On Tue, Oct 27, 2015 at 4:21 PM, Rick Mann wrote:
> I was looking to resize the partition on my little SD card so I could use the
> whole thing. I'm following the instructions here:
>
>
> http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD
>
I am a bit confused with the BB-SPI1-01-00A0.dts example provided in the
wiki http://elinux.org/BeagleBone_Black_Enable_SPIDEV. In particular, I
don't understand the rationale for the values used in the pin mux
configuration:
0x190 0x33 /* mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3
On Mon, Jun 16, 2014 at 7:53 AM, Michael Coulton mc6...@gmail.com wrote:
Hello
I'm a little confused as to how the SD card , eMMc and the Debian OS work.
I've recently flashed the eMMc card with the Debian OS. Here's my questions
1.) what to I do with the SD card? Leave it in the BB or remove
14 matches
Mail list logo