[beagleboard] Re: Is BBB possible display in 1920x1080@60Hz at Bare Metal???

[Karl Karpfen]

I think it does not has anything to do with bare metal 
programming/available computing power but with the HDMI chip. According 
to http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI#Supported_Resolutions 
1920x1080@60 Hz is not possible.

Am Samstag, 14. November 2015 14:35:23 UTC+1 schrieb fox lin:
>
> Deay Guys:
>
> These days, I encounter a struggle question which is in BBB bare metal 
> display!
>
> Following are my condition and question:
>
> 1. I design a raster display for mobile LCM which work in 800x1200@60Hz. 
> (In bare metal)
> --> I use TTL 24Bits (RGB) + Hsync + Vsync + PCLK +  DE for display 
> timing.
> --> I write several pattern on the LCM and it works normally.
>
> 2. Today, I got a 1080x1920 LCM and just want to light on it. But the 
> screen is abnormal.
> But I reduce the resolution to 960x1920 and display is success!
>
> 3. Is that the DMA size mis-match? If is so...How to modify it? Some body 
> could guide to me?
> or
> BBB NOT support resolution which exceed 960x1920?
>
> Have a nice day~
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: shrink emmc for backup

[Fohnbit]

Hello Joe,

I need to backup eMMC from BBB1 and restore it on eMMC on BBB2.
I have 2 BBB. One of the BBB has a different eMMC Chip and can´t copy the 
image from BBB1 to BBB2, because of insufficient space on BBB2.

So I want to decrease the Image of BBB1.

But not sure if it work with dd ?


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] SPI low level driver

[Gianfranco Rosso]

I'm writing a SPI driver for the PRU on BBB.

Mux settings for pins is done by config-pin: P9.29, P9.30 and P9.31 are 
configured as "spi" for SPI1_D0, SPI1_D1 and SPI1_SCLK, while P8.27, P8.29 
and P9.28 are configured as gpio output as 3 chip select (to be manually 
managed).

Chip select pin are ok but I can't transmit/receive anything by the spi.

1) The PRU code checks register CM_PER_SPI1_CLKCTRL to verify if the module 
is enabled (interface and functional clocks provided to).
2) in case it enable the module and wait for fully functional status.

3) Then MCSPI_SYSCONFIG register is set to 0x030A (clocks always present, 
idle requests rejected, no autoidle plus module soft reset).
4) The initialization continues only when register MCSPI_SYSSTATUS confirm 
that reset is completed.

5) follows the setting of:

MCSPI_MODULCTRL to 0x0003 (no delay before first tx, functional mode, 
master, SPIEN not used, SINGLE mode)

MCSPI_CH0CONF to 0x200107BC (1clk clock granularity, FIFOs non enabled, no 
turbo mode, Tx on SPI1_D1, Rx on SPI1_D0, 16bit word, CLKD=15, mode0)

MCSPI_CH0CTRL to 0x1E01 (EXTCLK=30, channel 0 enabled)

Initialization is done.
With EXTCLK and CLKD settings I'm expecting a 100kHz spi clock (48MHz/(CLKD 
+ 1 + EXTCLK*16)=100kHz)

But when I write to register MCSPI_TX0, there's no activity at all on the 
spi pins, while I'm expecting the transmission/reception starts just after 
the writing into TX0 register...

Reading MCSPI_CH0STAT give me 0x00: EOT=0 (shift register sill loaded with 
data), TXS=0 (TX0 register full), RXS=0 (RX0 register empty).


Am I missing something?

Gianfranco

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Is BBB possible display in 1920x1080@60Hz at Bare Metal???

[CEinTX]

It does not have anything to do with the HDMI chip either. It is quite 
capable of handling 1080p @ 60 Hz.
The problem, according to other threads is that the LCD clock cannot work 
at the needed ~150Mhz needed for that interface.
The other issue is that since memory is a 16-bit interface, bandwidth 
becomes an issue as well.
We have run the interface at 1080p @ 24 & 30 Hz without too much issue as 
these only need a ~74Mhz clk.
We have also done 1360x768 @ 60 Hz with an 85Mhz clk.
We have not been able to figure out how to do 1080i as the LCD controller 
does not appear to have native support for interlacing.
Manually doing that would be a real pain. Might as well use the 24 or 30 Hz 
- essentially the same as far a bandwidth.

So bare metal or not, by all accounts, you are not going to get 1080p @ 60 
Hz.

Hope that helps,
Matt


On Tuesday, November 17, 2015 at 2:05:14 AM UTC-6, Karl Karpfen wrote:
>
> I think it does not has anything to do with bare metal 
> programming/available computing power but with the HDMI chip. According to 
> http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI#Supported_Resolutions 
> 1920x1080@60 Hz is not possible.
>
> Am Samstag, 14. November 2015 14:35:23 UTC+1 schrieb fox lin:
>>
>> Deay Guys:
>>
>> These days, I encounter a struggle question which is in BBB bare metal 
>> display!
>>
>> Following are my condition and question:
>>
>> 1. I design a raster display for mobile LCM which work in 800x1200@60Hz. 
>> (In bare metal)
>> --> I use TTL 24Bits (RGB) + Hsync + Vsync + PCLK +  DE for display 
>> timing.
>> --> I write several pattern on the LCM and it works normally.
>>
>> 2. Today, I got a 1080x1920 LCM and just want to light on it. But the 
>> screen is abnormal.
>> But I reduce the resolution to 960x1920 and display is success!
>>
>> 3. Is that the DMA size mis-match? If is so...How to modify it? Some body 
>> could guide to me?
>> or
>> BBB NOT support resolution which exceed 960x1920?
>>
>> Have a nice day~
>>
>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How do I get my Aptina camera (mt9m114) to work in kernel 3.14?

[Sergi D]

Hi again,
The custom device tree configuration produce some errors on boot up. The 
most significant errors are:



[2.360604] mtdoops: mtd device (mtddev=name/number) must be supplied
[2.719239] slave hdmi: could not get i2c
[3.279978] omap_vout:Could not register Video driver
[3.292445] sr_init: platform driver register failed for SR
[3.847739] systemd[1]: Failed to enumerate cgroup controllers: No such 
file or directory
[   15.711163] systemd[1]: Failed to start Load Kernel Modules.
[   19.921960]  remoteproc0: failed to load am335x-pm-firmware.elf
[   20.097918]  remoteproc0: request_firmware failed: -2
[   20.103564] wkup_m3 44d0.wkup_m3: rproc_boot failed
[   25.486841] libphy: PHY 4a101000.mdio:01 not found
[   25.492142] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   97.760166] omap_i2c 4819c000.i2c: controller timed out
[   98.761749] omap_i2c 4819c000.i2c: controller timed out
[   99.760158] omap_i2c 4819c000.i2c: controller timed out
[  100.760159] omap_i2c 4819c000.i2c: controller timed out

The problem seems to be related with I2C communication. The camera cape is 
an i2c soc_camera and interacts through i2c-2 (bus 2).

Testing that bus communication I get a "controlled timed out" error. Is not 
responding.

root@beaglebone:~# i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  [10856.560130] omap_i2c 4819c000.i2c: controller timed out
-- [10857.560188] omap_i2c 4819c000.i2c: controller timed out
-- [10858.580154] omap_i2c 4819c000.i2c: controller timed out
-- [10859.600173] omap_i2c 4819c000.i2c: controller timed out

So, now I'm trying to wake up that i2c bus in order to activate the 
communication with the camera cape. To do so I'm modifying the device tree 
attached in the first comment. 

Also added a 'new' cape instance in "am335x-bone-i2c2-cape-eeprom.dtsi" 
with  the sensor's information and deleted from the custom device tree.

cape_cam0: cape_vddn_cam@58 {
compatible = "aptina, mt9m114";
reg = <0x58>;
#address-cells = <1>;
#size-cells = <0>;
/* dummy pll flags m, n, p1-7, PLL hardcoded in Driver */
/*flags = <0>;
pll-divider = <0 0 0 0 0 0 0 0 0>;*/
};

Any help will be appreciated!
Sergi.

El viernes, 13 de noviembre de 2015, 8:19:56 (UTC+1), Sergi D escribió:
>
> Yes. In kernel 3.8 worked perfectly.
>
> El viernes, 13 de noviembre de 2015, 5:06:42 (UTC+1), lisarden escribió:
>>
>> Did this sensor work in 3.8?
>> 11 Ноя 2015 г. 14:08 пользователь "Sergi D"  написал:
>>
>>> Hi All,
>>>
>>> I am trying to get work my Aptina camera MT9M114 
>>>  in the 3.14 
>>> kernel for a Beaglebone Black.
>>>
>>> I'm using the RobertCNelson github 
>>> 's kernel and also the 
>>> dtb-builder. But I had no lucky because working on I realized that there's 
>>> no driver for that sensor in the kernel. I tried to import it from kernel 
>>> 3.8. I copied the files and modified the Kconfig and Makefile. I obtained 
>>> the corresponding menu entry in menuconfig. I'm able to select the driver 
>>> as module or built-in. 
>>>
>>> Anyone knows if the sensor driver is compatible with my actual kernel 
>>> version? There are other drivers compatible with the mt9m114 sensor?
>>>
>>> I'm trying to create a device tree include (dtsi) based on the 
>>> BB-BONE-VVDN-00A0.dts but making it static and not with overlays to add as 
>>> include in am335x-boneblack.dts. (attached file: 
>>> am335x-bone-cam-vvdn-00a0.dtsi)
>>>
>>> The kernel, modules and dtbs compiles without errors but when I install 
>>> all in the BBB nothing related to /dev/video0 or media/i2c appears during 
>>> the boot or dmesg.
>>>
>>> Porting from 3.8 to 3.14 may create pin conflicts? It is possible that 
>>> device tree is not calling the driver? 
>>>
>>> Any help will be appreciated!
>>> Sergi.
>>>
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to beagleboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
/*
 * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
 *
 * 

Re: [beagleboard] How do I get my Aptina camera (mt9m114) to work in kernel 3.14?

[Sergi D]

Hi again,
The custom device tree configuration produce some errors on boot up. The 
most significant errors are:

[2.360604] mtdoops: mtd device (mtddev=name/number) must be supplied
[2.719239] slave hdmi: could not get i2c
[3.279978] omap_vout:Could not register Video driver
[3.292445] sr_init: platform driver register failed for SR
[3.847739] systemd[1]: Failed to enumerate cgroup controllers: No such 
file or directory
[   15.711163] systemd[1]: Failed to start Load Kernel Modules.
[   19.921960]  remoteproc0: failed to load am335x-pm-firmware.elf
[   20.097918]  remoteproc0: request_firmware failed: -2
[   20.103564] wkup_m3 44d0.wkup_m3: rproc_boot failed
[   25.486841] libphy: PHY 4a101000.mdio:01 not found
[   25.492142] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   97.760166] omap_i2c 4819c000.i2c: controller timed out
[   98.761749] omap_i2c 4819c000.i2c: controller timed out
[   99.760158] omap_i2c 4819c000.i2c: controller timed out
[  100.760159] omap_i2c 4819c000.i2c: controller timed out


The problem seems to be related with I2C communication. The camera cape is 
an i2c soc_camera and interacts through i2c-2 (bus 2).

Testing that bus communication I get a "controlled timed out" error. Is not 
responding.

root@beaglebone:~# i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  [10856.560130] omap_i2c 4819c000.i2c: controller timed out
-- [10857.560188] omap_i2c 4819c000.i2c: controller timed out
-- [10858.580154] omap_i2c 4819c000.i2c: controller timed out
-- [10859.600173] omap_i2c 4819c000.i2c: controller timed out


So, now I'm trying to wake up that i2c bus in order to activate the 
communication with the camera cape. To do so I'm modifying the device tree 
attached in the first comment. 

Also added a 'new' cape instance in "am335x-bone-i2c2-cape-eeprom.dtsi" 
with  the sensor's information and deleted from the custom device tree.

cape_cam0: cape_vddn_cam@58 {
compatible = "aptina, mt9m114";
reg = <0x58>;
#address-cells = <1>;
#size-cells = <0>;
/* dummy pll flags m, n, p1-7, PLL hardcoded in Driver */
/*flags = <0>;
pll-divider = <0 0 0 0 0 0 0 0 0>;*/
};



Any help will be appreciated!
Sergi.

El viernes, 13 de noviembre de 2015, 8:19:56 (UTC+1), Sergi D escribió:
Yes. In kernel 3.8 worked perfectly.

El viernes, 13 de noviembre de 2015, 5:06:42 (UTC+1), lisarden escribió:
Did this sensor work in 3.8?
11 Ноя 2015 г. 14:08 пользователь "Sergi D"  написал:
Hi All,

I am trying to get work my Aptina camera MT9M114 in the 3.14 kernel for a 
Beaglebone Black.

I'm using the RobertCNelson github's kernel and also the dtb-builder. But I 
had no lucky because working on I realized that there's no driver for that 
sensor in the kernel. I tried to import it from kernel 3.8. I copied the 
files and modified the Kconfig and Makefile. I obtained the corresponding 
menu entry in menuconfig. I'm able to select the driver as module or 
built-in. 

Anyone knows if the sensor driver is compatible with my actual kernel 
version? There are other drivers compatible with the mt9m114 sensor?

I'm trying to create a device tree include (dtsi) based on the 
BB-BONE-VVDN-00A0.dts but making it static and not with overlays to add as 
include in am335x-boneblack.dts. (attached file: 
am335x-bone-cam-vvdn-00a0.dtsi)

The kernel, modules and dtbs compiles without errors but when I install all 
in the BBB nothing related to /dev/video0 or media/i2c appears during the 
boot or dmesg.

Porting from 3.8 to 3.14 may create pin conflicts? It is possible that 
device tree is not calling the driver? 

Any help will be appreciated!
Sergi.

El viernes, 13 de noviembre de 2015, 8:19:56 (UTC+1), Sergi D escribió:
>
> Yes. In kernel 3.8 worked perfectly.
>
> El viernes, 13 de noviembre de 2015, 5:06:42 (UTC+1), lisarden escribió:
>>
>> Did this sensor work in 3.8?
>> 11 Ноя 2015 г. 14:08 пользователь "Sergi D"  написал:
>>
>>> Hi All,
>>>
>>> I am trying to get work my Aptina camera MT9M114 
>>>  in the 3.14 
>>> kernel for a Beaglebone Black.
>>>
>>> I'm using the RobertCNelson github 
>>> 's kernel and also the 
>>> dtb-builder. But I had no lucky because working on I realized that there's 
>>> no driver for that sensor in the kernel. I tried to import it from kernel 
>>> 3.8. I copied the files and modified the Kconfig and Makefile. I obtained 
>>> the corresponding menu entry in menuconfig. I'm able to select the driver 
>>> as module or built-in. 
>>>
>>> Anyone knows if the sensor driver is compatible with my actual kernel 
>>> version? There are other drivers compat

Re: [beagleboard] Re: Is BBB possible display in 1920x1080@60Hz at Bare Metal???

[Gerald Coley]

No. 1920x1080 at 24HZ is the best the HW can support inside the processor.

Gerald


On Tue, Nov 17, 2015 at 8:39 AM, CEinTX  wrote:

> It does not have anything to do with the HDMI chip either. It is quite
> capable of handling 1080p @ 60 Hz.
> The problem, according to other threads is that the LCD clock cannot work
> at the needed ~150Mhz needed for that interface.
> The other issue is that since memory is a 16-bit interface, bandwidth
> becomes an issue as well.
> We have run the interface at 1080p @ 24 & 30 Hz without too much issue as
> these only need a ~74Mhz clk.
> We have also done 1360x768 @ 60 Hz with an 85Mhz clk.
> We have not been able to figure out how to do 1080i as the LCD controller
> does not appear to have native support for interlacing.
> Manually doing that would be a real pain. Might as well use the 24 or 30
> Hz - essentially the same as far a bandwidth.
>
> So bare metal or not, by all accounts, you are not going to get 1080p @ 60
> Hz.
>
> Hope that helps,
> Matt
>
>
> On Tuesday, November 17, 2015 at 2:05:14 AM UTC-6, Karl Karpfen wrote:
>>
>> I think it does not has anything to do with bare metal
>> programming/available computing power but with the HDMI chip. According to
>> http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI#Supported_Resolutions
>> 1920x1080@60 Hz is not possible.
>>
>> Am Samstag, 14. November 2015 14:35:23 UTC+1 schrieb fox lin:
>>>
>>> Deay Guys:
>>>
>>> These days, I encounter a struggle question which is in BBB bare metal
>>> display!
>>>
>>> Following are my condition and question:
>>>
>>> 1. I design a raster display for mobile LCM which work in 800x1200@60Hz.
>>> (In bare metal)
>>> --> I use TTL 24Bits (RGB) + Hsync + Vsync + PCLK +  DE for display
>>> timing.
>>> --> I write several pattern on the LCM and it works normally.
>>>
>>> 2. Today, I got a 1080x1920 LCM and just want to light on it. But the
>>> screen is abnormal.
>>> But I reduce the resolution to 960x1920 and display is success!
>>>
>>> 3. Is that the DMA size mis-match? If is so...How to modify it? Some
>>> body could guide to me?
>>> or
>>> BBB NOT support resolution which exceed 960x1920?
>>>
>>> Have a nice day~
>>>
>>>
>>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Taceant Omnes]

On 16 November 2015 at 16:47, Taceant Omnes  wrote:

> I am using now a newish rev. C BBB that I got a few weeks ago. I did
> what you suggested and pressed the boot button on the BBB to force the
> BBB to used the uboot in the MicroSD card instead of the uboot in the
> eMMC. However I still got the same problem as before, i. e., it hangs
> at the last line of the log with the asterisks moving and the time
> being incremented.
>
> I am also puzzled why your boot log looks so different from mine. For
> example I get the message below and you don't, and I don't get any
> timestamp starting at [0.00]:
>
> [FAILED] Failed to start Load Kernel Modules.
>
> Boot log:
> https://paste.debian.net/333095/
>
> Any ideas? Maybe you have something in uEnv.txt that I don't? Mine is 
> unchanged.
>
> /rootfs/uEnv.txt
> https://paste.debian.net/333104/
>
> /rootfs/boot/uEnv.txt
> https://paste.debian.net/333106/

Hi Robert,

I found how to get the kernel timestamps starting at [0.00]:
(by removing the "quiet" option in /rootfs/boot/uEnv.txt).

If I compare my boot log with yours there are a number of differences.
One is that the entries about PRU, starting with "pruss-rproc
4a30.pruss: 8 PRU interrupts parsed" appear at 11.6 seconds in my
log and at 25.8 seconds in yours. Something is taking a lot of time in
your boot.

One of the last log entries in my log says "Timed out waiting for
device dev-ttyGS0.device." . Any idea about what that is, and why
don't you get that error?

In any case, I reverted to the bone10 kernel by changing the line
about uname_r in /rootfs/boot/uEnv.txt so my BBB boots again.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Nuno Gonçalves]

On Friday, November 13, 2015 at 5:50:23 PM UTC, RobertCNelson wrote:
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/7df6a18cbcd567712edd1e1a4a774742d510dbe3


Under low loads this patch (or something else at 4.1.13-ti-r30), have 
caused a dramatic power decrease on the BBB.

Disabling state1 brings it back to the same board temperature, which makes 
it sound like that cpuidle was not working previously. (I was not sure it 
it was only the /sys interface that was not available).

I still couldn't fully determine how this affect real time latencies, but 
hope to provide data soon.

Thanks

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Nuno Gonçalves]

I might not made obvious that I'm talking about eletric power consumption 
(and temperature), so this is a good thing.

Thanks,
Nuno

On Tuesday, November 17, 2015 at 4:28:18 PM UTC, Nuno Gonçalves wrote:
>
>
>
> On Friday, November 13, 2015 at 5:50:23 PM UTC, RobertCNelson wrote:
>>
>>
>> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/7df6a18cbcd567712edd1e1a4a774742d510dbe3
>
>
> Under low loads this patch (or something else at 4.1.13-ti-r30), have 
> caused a dramatic power decrease on the BBB.
>
> Disabling state1 brings it back to the same board temperature, which makes 
> it sound like that cpuidle was not working previously. (I was not sure it 
> it was only the /sys interface that was not available).
>
> I still couldn't fully determine how this affect real time latencies, but 
> hope to provide data soon.
>
> Thanks
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Taceant Omnes]

On 17 November 2015 at 16:28, Nuno Gonçalves  wrote:
>
>
> On Friday, November 13, 2015 at 5:50:23 PM UTC, RobertCNelson wrote:
>>
>>
>> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/7df6a18cbcd567712edd1e1a4a774742d510dbe3
>
>
> Under low loads this patch (or something else at 4.1.13-ti-r30), have caused
> a dramatic power decrease on the BBB.
>
> Disabling state1 brings it back to the same board temperature, which makes
> it sound like that cpuidle was not working previously. (I was not sure it it
> was only the /sys interface that was not available).
>
> I still couldn't fully determine how this affect real time latencies, but
> hope to provide data soon.

Good to know, thanks.

I am trying to bring power down, and have been measuring the current
going into the BBB through the 5V socket with no USB cable connected.

In my first measurement kernel idle was 300 mA. Then I installed
cpufreputils and that brought the current down to 230 mA because -
unexpectedly - just installing the Debian package changed the CPU mode
to "on-demand". Today I managed to bring the current down a further 20
mA (to about 210 mA) by disabling HDMI in boot/uEnv.txt.

I am curious now to see how much power cpuidle will save - once I have
a kernel with it.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Robert Nelson]

> Good to know, thanks.
>
> I am trying to bring power down, and have been measuring the current
> going into the BBB through the 5V socket with no USB cable connected.
>
> In my first measurement kernel idle was 300 mA. Then I installed
> cpufreputils and that brought the current down to 230 mA because -
> unexpectedly - just installing the Debian package changed the CPU mode
> to "on-demand". Today I managed to bring the current down a further 20
> mA (to about 210 mA) by disabling HDMI in boot/uEnv.txt.

We enable 'performance' by default... The thought, boot as fast as we
can, by the time the rootfs loads (and cpufrequtils) we've gotten
mostly up, so safe to switch to on-demand..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: An issue about spidev1.0

[Mian Tang]

>
> Is there anyone can tell me whether "/dev/spidev1.0" occupies SPI1, CS0?
>

If it is, how could I remove it? Is it necessary that I need to recompile 
the kernel?

Thanks a lot.
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cpuidle

[Taceant Omnes]

On 17 November 2015 at 16:47, Robert Nelson  wrote:
>> Good to know, thanks.
>>
>> I am trying to bring power down, and have been measuring the current
>> going into the BBB through the 5V socket with no USB cable connected.
>>
>> In my first measurement kernel idle was 300 mA. Then I installed
>> cpufreputils and that brought the current down to 230 mA because -
>> unexpectedly - just installing the Debian package changed the CPU mode
>> to "on-demand". Today I managed to bring the current down a further 20
>> mA (to about 210 mA) by disabling HDMI in boot/uEnv.txt.
>
> We enable 'performance' by default... The thought, boot as fast as we
> can, by the time the rootfs loads (and cpufrequtils) we've gotten
> mostly up, so safe to switch to on-demand..

Thanks for explanation.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Windows 8 (64bit) driver install problems

[theobouwman98]

Hello,

I have new BeagleBone Black.
And tried to install the drivers, i'm running mac os 10.11.1, but when i 
tried to install the serial drivers i get an error with "Installation 
failed, there's no software that can be installed"

Anyone who knows the issue?

Let me know

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Windows 8 (64bit) driver install problems

[evilwulfie]

title says windows 8 drivers and your installing them on a mac ?

uhhh


On 11/17/2015 10:55 AM, theobouwma...@gmail.com wrote:
> Hello,
>
> I have new BeagleBone Black.
> And tried to install the drivers, i'm running mac os 10.11.1, but when
> i tried to install the serial drivers i get an error with
> "Installation failed, there's no software that can be installed"
>
> Anyone who knows the issue?
>
> Let me know
> -- 
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] SPI low level driver

[Jason Kridner]

Are you reading back all the registers to make sure all your writes work OK?

Have you tried enabling the mux on one of the CS signals? I don't have
any real reason to believe it is necessary, but I'd want you to try in
as normal a mode as possible to get things working before tweaking.

Have you tried out Starterware and the Starterware steps to try to
generate a known-good configuration from the PRU?
http://processors.wiki.ti.com/index.php/StarterWare_McSPI


On Tue, Nov 17, 2015 at 9:25 AM, Gianfranco Rosso
 wrote:
> I'm writing a SPI driver for the PRU on BBB.
>
> Mux settings for pins is done by config-pin: P9.29, P9.30 and P9.31 are
> configured as "spi" for SPI1_D0, SPI1_D1 and SPI1_SCLK, while P8.27, P8.29
> and P9.28 are configured as gpio output as 3 chip select (to be manually
> managed).
>
> Chip select pin are ok but I can't transmit/receive anything by the spi.
>
> 1) The PRU code checks register CM_PER_SPI1_CLKCTRL to verify if the module
> is enabled (interface and functional clocks provided to).
> 2) in case it enable the module and wait for fully functional status.
>
> 3) Then MCSPI_SYSCONFIG register is set to 0x030A (clocks always present,
> idle requests rejected, no autoidle plus module soft reset).
> 4) The initialization continues only when register MCSPI_SYSSTATUS confirm
> that reset is completed.
>
> 5) follows the setting of:
>
> MCSPI_MODULCTRL to 0x0003 (no delay before first tx, functional mode,
> master, SPIEN not used, SINGLE mode)
>
> MCSPI_CH0CONF to 0x200107BC (1clk clock granularity, FIFOs non enabled, no
> turbo mode, Tx on SPI1_D1, Rx on SPI1_D0, 16bit word, CLKD=15, mode0)
>
> MCSPI_CH0CTRL to 0x1E01 (EXTCLK=30, channel 0 enabled)
>
> Initialization is done.
> With EXTCLK and CLKD settings I'm expecting a 100kHz spi clock (48MHz/(CLKD
> + 1 + EXTCLK*16)=100kHz)
>
> But when I write to register MCSPI_TX0, there's no activity at all on the
> spi pins, while I'm expecting the transmission/reception starts just after
> the writing into TX0 register...
>
> Reading MCSPI_CH0STAT give me 0x00: EOT=0 (shift register sill loaded with
> data), TXS=0 (TX0 register full), RXS=0 (RX0 register empty).
>
>
> Am I missing something?
>
> Gianfranco
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: shrink emmc for backup

[Jason Kridner]

It would be helpful to know how far you are off. That is, can you just
resize the partition or do you need to remove some content first? If
you really need to do a block-by-block copy, the debian resize2fs tool
can be used to shrink the partition ahead of updating the partition
table.[2] You'd need a bootable microSD card (non-flasher!!) to
perform the resize operation.

Typically, if you are working from an image that has
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh[1],
then you'd simply want to run that script on BBB1 to write the image
to a microSD card and then boot that microSD card on BBB2 to write to
the eMMC. This copies the appropriate files, but partitions and
formats the destination eMMC rather than doing a block-by-block copy
that could be why your image doesn't fit.

[1] 
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
[2] http://lmgtfy.com/?q=shrink+partition+resize2fs

On Tue, Nov 17, 2015 at 6:06 AM, Fohnbit  wrote:
> Hello Joe,
>
> I need to backup eMMC from BBB1 and restore it on eMMC on BBB2.
> I have 2 BBB. One of the BBB has a different eMMC Chip and can´t copy the
> image from BBB1 to BBB2, because of insufficient space on BBB2.
>
> So I want to decrease the Image of BBB1.
>
> But not sure if it work with dd ?
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: shrink emmc for backup

[William Hermans]

I'd just use tar . . .

On Tue, Nov 17, 2015 at 11:44 AM, Jason Kridner 
wrote:

> It would be helpful to know how far you are off. That is, can you just
> resize the partition or do you need to remove some content first? If
> you really need to do a block-by-block copy, the debian resize2fs tool
> can be used to shrink the partition ahead of updating the partition
> table.[2] You'd need a bootable microSD card (non-flasher!!) to
> perform the resize operation.
>
> Typically, if you are working from an image that has
>
> /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh[1],
> then you'd simply want to run that script on BBB1 to write the image
> to a microSD card and then boot that microSD card on BBB2 to write to
> the eMMC. This copies the appropriate files, but partitions and
> formats the destination eMMC rather than doing a block-by-block copy
> that could be why your image doesn't fit.
>
> [1]
> https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
> [2] http://lmgtfy.com/?q=shrink+partition+resize2fs
>
> On Tue, Nov 17, 2015 at 6:06 AM, Fohnbit  wrote:
> > Hello Joe,
> >
> > I need to backup eMMC from BBB1 and restore it on eMMC on BBB2.
> > I have 2 BBB. One of the BBB has a different eMMC Chip and can´t copy the
> > image from BBB1 to BBB2, because of insufficient space on BBB2.
> >
> > So I want to decrease the Image of BBB1.
> >
> > But not sure if it work with dd ?
> >
> >
> > --
> > For more options, visit http://beagleboard.org/discuss
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "BeagleBoard" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to beagleboard+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB Bootloaders and Flash Tools

[Bharath R]

Hello BBB Community, 

May I know where I can find a MLO source code? I don't need pre-built 
image, but I need the source code of it.

And similar to SAM-BA tool provided by Atmel for their controllers, to 
flash the images, is there a tool which is used to flash the images(MLO, 
U-Boot) onto the BBB's eMMC?

Regards,
Bharath

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB Bootloaders and Flash Tools

[Robert Nelson]

On Tue, Nov 17, 2015 at 1:06 PM, Bharath R  wrote:
> Hello BBB Community,
>
> May I know where I can find a MLO source code? I don't need pre-built image,
> but I need the source code of it.

MLO = file generated in u-boot, otherwise called "U-Boot SPL"

https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot

> And similar to SAM-BA tool provided by Atmel for their controllers, to flash
> the images, is there a tool which is used to flash the images(MLO, U-Boot)
> onto the BBB's eMMC?

So you want to do it via usb:

https://github.com/ungureanuvladvictor/BBBlfs

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Windows 8 (64bit) driver install problems

[theobouwman98]

I didn't saw Windows at the topic

Op dinsdag 17 november 2015 19:27:43 UTC+1 schreef Wulf Man:
>
> title says windows 8 drivers and your installing them on a mac ?
>
> uhhh 
>
>
> On 11/17/2015 10:55 AM, theobo...@gmail.com  wrote:
>
> Hello,
>
> I have new BeagleBone Black.
> And tried to install the drivers, i'm running mac os 10.11.1, but when i 
> tried to install the serial drivers i get an error with "Installation 
> failed, there's no software that can be installed"
>
> Anyone who knows the issue?
>
> Let me know
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Setting up cross compiler under OS X 10.11 / El Capitan

[theobouwman98]

Dear Joe,

I see you are running os 10.11, me too.
I'm not getting the BBB to be recognized by my mac.
And when i'm trying to install the Serial driver, i get an error
Can you help me?

Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
>
> I've found some great resources out there that help us Mac folk out with 
> building an arm toolchain on the OS X platform. Here they are if any others 
> stumble across this thread looking for the same:
>
> http://www.benmont.com/tech/crosscompiler.html
> http://will-tm.com/cross-compiling-mac-os-x-mavericks/
> http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html 
>  (this one is the most detailed)
>
>
> I've gotten through a few of the stumbling blocks but I'm currently stuck. 
> I get this far:
>
> [INFO ]  Performing some trivial sanity checks
>
> [INFO ]  Build started 20151023.200552
>
> [INFO ]  Building environment variables
>
> [00:03] /
>
>
> So, after that, if I look at the activity monitor, bash is around 100% 
> processor utilization on one of the cores. I figure "great, it's doing 
> something". I left it to do its thing and after an hour, I killed the 
> process. I changed a few settings... ran it again... same thing. Okay... 
> maybe it just takes a really long time. I left it overnight. This morning 
> it was still near 100% processor utilization and nothing had changed in the 
> build.log file. Here's the last few lines from the build log:
>
>
> [DEBUG]  =
>
> [DEBUG]  Checking that we can run gcc -v
>
> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-v' 
>
> [DEBUG]Configured with: 
> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
>
> [DEBUG]Apple LLVM version 7.0.0 (clang-700.1.76)
>
> [DEBUG]Target: x86_64-apple-darwin15.0.0
>
> [DEBUG]Thread model: posix
>
> [DEBUG]  Checking that we can run gcc -v: done in 0.00s (at 00:03)
>
> [DEBUG]  =
>
> [DEBUG]  Checking that gcc can compile a trivial program
>
> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-O2' '-g' 
> '-pipe' 
> '/Volumes/CaSe/.build/arm-JoesBeaglebone-linux-gnueabi/build/test.c' '-o' 
> '/Volumes/CaSe/.build/arm-unknown-linux-gnueabi/build/.gccout' 
>
> [DEBUG]  Checking that gcc can compile a trivial program: done in 0.00s 
> (at 00:03)
>
> [EXTRA]  Installing user-supplied crosstool-NG configuration
>
> [DEBUG]  ==> Executing: 'mkdir' '-p' '/Volumes/CaSe/prefix/bin' 
>
> [DEBUG]  ==> Executing: 'install' '-m' '0755' 
> '/usr/local/Cellar/crosstool-ng/1.21.0/lib/ct-ng.1.21.0/scripts/
> toolchain-config.in' 
> '/Volumes/CaSe/prefix/bin/arm-unknown-linux-gnueabi-ct-ng.config' 
>
> [ERROR]  
>
> [ERROR]  >>
>
> [ERROR]  >>  Build failed in step '(top-level)'
>
> [ERROR]  >>
>
> [ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@216]
>
> [ERROR]  >>called from: main[scripts/crosstool-NG.sh@564]
>
> [ERROR]  
>
> [ERROR]  (elapsed: 756:57.00)
>
>
> Any suggestions on how to debug this? Obviously it's attempting to do 
> something given the processor utilization but... what the heck is it hung 
> up on?
>
>
> One thing worth noting... early in the process the build log had an error 
> with regards to not being able to find the ginstall tool. Since this was at 
> the beginning of the test process I figured it hadn't gotten to building 
> anything yet and as such, ct-ng clean was not needed (maybe I'm wrong). As 
> part of running ct-ng build it creates a directory structure (running clean 
> deletes this structure and all the tools included) at 
> /YourCaseSensitiveDirectory/.build/tools/bin. My solution was to just cp 
> install ginstall, and that got me past that error. Not sure if that's 
> contributing to anything but I thought it worth mentioning. Is there 
> another way around the missing ginstall problem?
>
>
> Cheers, Joe
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Windows 8 (64bit) driver install problems

[Gerald Coley]

[beagleboard] Windows 8 (64bit) driver install problems

On Tue, Nov 17, 2015 at 12:53 PM,  wrote:

> I didn't saw Windows at the topic
>
> Op dinsdag 17 november 2015 19:27:43 UTC+1 schreef Wulf Man:
>>
>> title says windows 8 drivers and your installing them on a mac ?
>>
>> uhhh
>>
>>
>> On 11/17/2015 10:55 AM, theobo...@gmail.com wrote:
>>
>> Hello,
>>
>> I have new BeagleBone Black.
>> And tried to install the drivers, i'm running mac os 10.11.1, but when i
>> tried to install the serial drivers i get an error with "Installation
>> failed, there's no software that can be installed"
>>
>> Anyone who knows the issue?
>>
>> Let me know
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Setting up cross compiler under OS X 10.11 / El Capitan

[Robert Nelson]

On Tue, Nov 17, 2015 at 12:53 PM,   wrote:
> Dear Joe,
>
> I see you are running os 10.11, me too.
> I'm not getting the BBB to be recognized by my mac.
> And when i'm trying to install the Serial driver, i get an error
> Can you help me?

test builds here:

https://github.com/jwise/HoRNDIS/issues/42

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PREBOOT delay. Is it possible to reduce it?

[andky1991]

I have tried run defferent images from SD:

1.Debian 2015-07-28 console with *u-boot v2015.01* writed to unallocated 
space in front of first partition -* 2 second delay remains*
2.Jessie Snapshot console with *u-boot v2015.10* writed to unallocated 
space in front of first partition -* 2 second delay remains*
3. Angstrom v2012.12 (kernel 3.8.13) with *u-boot 2013.04-dirty* writed to 
FAT32-MLO BOOT partition - *start immediately after plug in power supply*


So, I assumed that the problem is in the method of placing the loader. But 
if replace u-boot v2015.01 with u-boot v2013.04, then delay disappears. The 
new version has something that leads to a pause. What could it be?


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PREBOOT delay. Is it possible to reduce it?

[Robert Nelson]

On Tue, Nov 17, 2015 at 1:37 PM,   wrote:
>
> I have tried run defferent images from SD:
>
> 1.Debian 2015-07-28 console with u-boot v2015.01 writed to unallocated space
> in front of first partition - 2 second delay remains
> 2.Jessie Snapshot console with u-boot v2015.10 writed to unallocated space
> in front of first partition - 2 second delay remains
> 3. Angstrom v2012.12 (kernel 3.8.13) with u-boot 2013.04-dirty writed to
> FAT32-MLO BOOT partition - start immediately after plug in power supply
>
>
> So, I assumed that the problem is in the method of placing the loader. But
> if replace u-boot v2015.01 with u-boot v2013.04, then delay disappears. The
> new version has something that leads to a pause. What could it be?

migration to driver model

http://git.denx.de/?p=u-boot.git;a=tree;f=doc/driver-model;hb=HEAD

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Setting up cross compiler under OS X 10.11 / El Capitan

[Joe Ciarcia]

I gave up on using OS X El Cap and Xcode for development on the Beaglebone. 
I posted to the crosstool-ng list to see if anyone could help with the 
errors I was seeing and I didn't get any responses (even though it's a 
pretty active list, I just suspect very few people are trying to do cross 
platform development for the arm on a Mac). I ended up installing Debian 
Jessie on an old Macbook (the original one actually, version 1,1) and 
everything just works great with it. After playing around a bit on the Mac 
I decided to buy a new Dell XPS 13 for development (warning there... you'll 
need to run Debian unstable with the 4.3 experimental kernel in order to 
support the new Skylake architecture but figuring all that out was MUCH 
easier than trying to build a cross compiler toolchain for Xcode). As for 
getting get the USB working... I never did but it looks like there's been 
some progress in the past few weeks. Check out Robert's post. 

As for connecting to it via ethernet (which is pretty easy)... you can 
either connect it directly to the ethernet port on your Mac, or you can 
connect it to your router. To log in all you have to do is open a terminal 
and ssh in...

ssh root@beaglebone.local

You don't have to fool around with IP addresses etc. as most of the 
tutorials indicate. Much easier that way. Once you're in though, create a 
new user so that you're not using root all the time.

If you want to go the Debian route, I highly recommend this video from 
Derek Molloy to get things started. It will show you how to get the Eclipse 
IDE up and running which will allow you to do cross compilation, remote 
deployment of your binaries, and remote debugging. It's pretty slick!

https://www.youtube.com/watch?v=T9yFyWsyyGk

Cheers, Joe

On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5, theobo...@gmail.com 
wrote:
>
> Dear Joe,
>
> I see you are running os 10.11, me too.
> I'm not getting the BBB to be recognized by my mac.
> And when i'm trying to install the Serial driver, i get an error
> Can you help me?
>
> Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
>>
>> I've found some great resources out there that help us Mac folk out with 
>> building an arm toolchain on the OS X platform. Here they are if any others 
>> stumble across this thread looking for the same:
>>
>> http://www.benmont.com/tech/crosscompiler.html
>> http://will-tm.com/cross-compiling-mac-os-x-mavericks/
>> http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html 
>>  (this one is the most detailed)
>>
>>
>> I've gotten through a few of the stumbling blocks but I'm currently 
>> stuck. I get this far:
>>
>> [INFO ]  Performing some trivial sanity checks
>>
>> [INFO ]  Build started 20151023.200552
>>
>> [INFO ]  Building environment variables
>>
>> [00:03] /
>>
>>
>> So, after that, if I look at the activity monitor, bash is around 100% 
>> processor utilization on one of the cores. I figure "great, it's doing 
>> something". I left it to do its thing and after an hour, I killed the 
>> process. I changed a few settings... ran it again... same thing. Okay... 
>> maybe it just takes a really long time. I left it overnight. This morning 
>> it was still near 100% processor utilization and nothing had changed in the 
>> build.log file. Here's the last few lines from the build log:
>>
>>
>> [DEBUG]  =
>>
>> [DEBUG]  Checking that we can run gcc -v
>>
>> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-v' 
>>
>> [DEBUG]Configured with: 
>> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/usr/include/c++/4.2.1
>>
>> [DEBUG]Apple LLVM version 7.0.0 (clang-700.1.76)
>>
>> [DEBUG]Target: x86_64-apple-darwin15.0.0
>>
>> [DEBUG]Thread model: posix
>>
>> [DEBUG]  Checking that we can run gcc -v: done in 0.00s (at 00:03)
>>
>> [DEBUG]  =
>>
>> [DEBUG]  Checking that gcc can compile a trivial program
>>
>> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-O2' 
>> '-g' '-pipe' 
>> '/Volumes/CaSe/.build/arm-JoesBeaglebone-linux-gnueabi/build/test.c' '-o' 
>> '/Volumes/CaSe/.build/arm-unknown-linux-gnueabi/build/.gccout' 
>>
>> [DEBUG]  Checking that gcc can compile a trivial program: done in 0.00s 
>> (at 00:03)
>>
>> [EXTRA]  Installing user-supplied crosstool-NG configuration
>>
>> [DEBUG]  ==> Executing: 'mkdir' '-p' '/Volumes/CaSe/prefix/bin' 
>>
>> [DEBUG]  ==> Executing: 'install' '-m' '0755' 
>> '/usr/local/Cellar/crosstool-ng/1.21.0/lib/ct-ng.1.21.0/scripts/
>> toolchain-config.in' 
>> '/Volumes/CaSe/prefix/bin/arm-unknown-linux-gnueabi-ct-ng.config' 
>>
>> [ERROR]  
>>
>> [ERROR]  >>
>>
>> [ERROR]  >>  Build failed in step '(top-level)'
>>
>> [ERROR]  >>
>>
>> [ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@216]
>>
>> [ERROR]  >>called from: main[scripts/crosstool-NG.sh@564]
>>
>> 

Re: [beagleboard] PREBOOT delay. Is it possible to reduce it?

[Rick Mann]

> On Nov 17, 2015, at 11:57 , Robert Nelson  wrote:
> 
> On Tue, Nov 17, 2015 at 1:37 PM,   wrote:
>> 
>> I have tried run defferent images from SD:
>> 
>> 1.Debian 2015-07-28 console with u-boot v2015.01 writed to unallocated space
>> in front of first partition - 2 second delay remains
>> 2.Jessie Snapshot console with u-boot v2015.10 writed to unallocated space
>> in front of first partition - 2 second delay remains
>> 3. Angstrom v2012.12 (kernel 3.8.13) with u-boot 2013.04-dirty writed to
>> FAT32-MLO BOOT partition - start immediately after plug in power supply
>> 
>> 
>> So, I assumed that the problem is in the method of placing the loader. But
>> if replace u-boot v2015.01 with u-boot v2013.04, then delay disappears. The
>> new version has something that leads to a pause. What could it be?
> 
> migration to driver model
> 
> http://git.denx.de/?p=u-boot.git;a=tree;f=doc/driver-model;hb=HEAD

Robert, do you mean that U-Boot is migrating to driver model during that delay? 
Or the delay is the result of U-boot having updated to the new driver model?

If the latter, what's it doing during those two seconds? Is there any way to 
speed that up? Eventually, I'd like to have a very fast-booting BBB.

Thanks,

-- 
Rick Mann
rm...@latencyzero.com


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PREBOOT delay. Is it possible to reduce it?

[Robert Nelson]

>> migration to driver model
>>
>> http://git.denx.de/?p=u-boot.git;a=tree;f=doc/driver-model;hb=HEAD
>
> Robert, do you mean that U-Boot is migrating to driver model during that 
> delay? Or the delay is the result of U-boot having updated to the new driver 
> model?
>
> If the latter, what's it doing during those two seconds? Is there any way to 
> speed that up? Eventually, I'd like to have a very fast-booting BBB.

For me, it was around the initial driver model merge that we got that
slight delay.

Of course, it might also be newer ddr timing init..

The slow down didn't really bug me so i never looked too deeply in it..

But if you guys want speed, switch to u-boot's falcon mode:

MLO -> kernel

vs:

MLO -> u-boot.img -> kernel

it might not be 100% evident, but you'll need to hardcode a lot of
stuff in MLO that u-boot.img currently reads from uEnv.txt

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PREBOOT delay. Is it possible to reduce it?

[Robert Nelson]

On Tue, Nov 17, 2015 at 4:15 PM, Robert Nelson  wrote:
>>> migration to driver model
>>>
>>> http://git.denx.de/?p=u-boot.git;a=tree;f=doc/driver-model;hb=HEAD
>>
>> Robert, do you mean that U-Boot is migrating to driver model during that 
>> delay? Or the delay is the result of U-boot having updated to the new driver 
>> model?
>>
>> If the latter, what's it doing during those two seconds? Is there any way to 
>> speed that up? Eventually, I'd like to have a very fast-booting BBB.
>
> For me, it was around the initial driver model merge that we got that
> slight delay.
>
> Of course, it might also be newer ddr timing init..
>
> The slow down didn't really bug me so i never looked too deeply in it..
>
> But if you guys want speed, switch to u-boot's falcon mode:
>
> MLO -> kernel
>
> vs:
>
> MLO -> u-boot.img -> kernel
>
> it might not be 100% evident, but you'll need to hardcode a lot of
> stuff in MLO that u-boot.img currently reads from uEnv.txt

For other speed up's, look into the am335x_evm board/mux files, you'll
notice it relies on reading an eeprom over i2c.. A lot of that can be
factored out if you know exactly what board you have. (i2c can be
slow)...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PREBOOT delay. Is it possible to reduce it?

[Rick Mann]

> On Nov 17, 2015, at 14:18 , Robert Nelson  wrote:
> 
> On Tue, Nov 17, 2015 at 4:15 PM, Robert Nelson  
> wrote:
 migration to driver model
 
 http://git.denx.de/?p=u-boot.git;a=tree;f=doc/driver-model;hb=HEAD
>>> 
>>> Robert, do you mean that U-Boot is migrating to driver model during that 
>>> delay? Or the delay is the result of U-boot having updated to the new 
>>> driver model?
>>> 
>>> If the latter, what's it doing during those two seconds? Is there any way 
>>> to speed that up? Eventually, I'd like to have a very fast-booting BBB.
>> 
>> For me, it was around the initial driver model merge that we got that
>> slight delay.
>> 
>> Of course, it might also be newer ddr timing init..
>> 
>> The slow down didn't really bug me so i never looked too deeply in it..
>> 
>> But if you guys want speed, switch to u-boot's falcon mode:
>> 
>> MLO -> kernel
>> 
>> vs:
>> 
>> MLO -> u-boot.img -> kernel
>> 
>> it might not be 100% evident, but you'll need to hardcode a lot of
>> stuff in MLO that u-boot.img currently reads from uEnv.txt
> 
> For other speed up's, look into the am335x_evm board/mux files, you'll
> notice it relies on reading an eeprom over i2c.. A lot of that can be
> factored out if you know exactly what board you have. (i2c can be
> slow)...

Awesome, thanks. Yeah, in my application, it's an appliance that will have very 
well-understood configurations.

-- 
Rick Mann
rm...@latencyzero.com


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Setting up cross compiler under OS X 10.11 / El Capitan

[John Syne]

Hi Joe,

Yeah, I came to the same conclusion. It seems easier to just install 
Debian/Ubuntu under Parallels and avoid all the confusion. BTW, MacPorts or 
HomeBrew (I don’t remember which) did manage to get ARM cross compilers to work 
under OSX, but they are now outdated. 

Regards,
John




> On Nov 17, 2015, at 12:26 PM, Joe Ciarcia  wrote:
> 
> I gave up on using OS X El Cap and Xcode for development on the Beaglebone. I 
> posted to the crosstool-ng list to see if anyone could help with the errors I 
> was seeing and I didn't get any responses (even though it's a pretty active 
> list, I just suspect very few people are trying to do cross platform 
> development for the arm on a Mac). I ended up installing Debian Jessie on an 
> old Macbook (the original one actually, version 1,1) and everything just 
> works great with it. After playing around a bit on the Mac I decided to buy a 
> new Dell XPS 13 for development (warning there... you'll need to run Debian 
> unstable with the 4.3 experimental kernel in order to support the new Skylake 
> architecture but figuring all that out was MUCH easier than trying to build a 
> cross compiler toolchain for Xcode). As for getting get the USB working... I 
> never did but it looks like there's been some progress in the past few weeks. 
> Check out Robert's post. 
> 
> As for connecting to it via ethernet (which is pretty easy)... you can either 
> connect it directly to the ethernet port on your Mac, or you can connect it 
> to your router. To log in all you have to do is open a terminal and ssh in...
> 
> ssh root@beaglebone.local
> 
> You don't have to fool around with IP addresses etc. as most of the tutorials 
> indicate. Much easier that way. Once you're in though, create a new user so 
> that you're not using root all the time.
> 
> If you want to go the Debian route, I highly recommend this video from Derek 
> Molloy to get things started. It will show you how to get the Eclipse IDE up 
> and running which will allow you to do cross compilation, remote deployment 
> of your binaries, and remote debugging. It's pretty slick!
> 
> https://www.youtube.com/watch?v=T9yFyWsyyGk
> 
> Cheers, Joe
> 
> On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5, theobo...@gmail.com wrote:
> Dear Joe,
> 
> I see you are running os 10.11, me too.
> I'm not getting the BBB to be recognized by my mac.
> And when i'm trying to install the Serial driver, i get an error
> Can you help me?
> 
> Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
> I've found some great resources out there that help us Mac folk out with 
> building an arm toolchain on the OS X platform. Here they are if any others 
> stumble across this thread looking for the same:
> 
> http://www.benmont.com/tech/crosscompiler.html 
> 
> http://will-tm.com/cross-compiling-mac-os-x-mavericks/ 
> 
> http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html 
>   
> (this one is the most detailed)
> 
> 
> I've gotten through a few of the stumbling blocks but I'm currently stuck. I 
> get this far:
> 
> [INFO ]  Performing some trivial sanity checks
> 
> [INFO ]  Build started 20151023.200552
> 
> [INFO ]  Building environment variables
> 
> [00:03] /
> 
> 
> 
> So, after that, if I look at the activity monitor, bash is around 100% 
> processor utilization on one of the cores. I figure "great, it's doing 
> something". I left it to do its thing and after an hour, I killed the 
> process. I changed a few settings... ran it again... same thing. Okay... 
> maybe it just takes a really long time. I left it overnight. This morning it 
> was still near 100% processor utilization and nothing had changed in the 
> build.log file. Here's the last few lines from the build log:
> 
> 
> 
> [DEBUG]  =
> 
> [DEBUG]  Checking that we can run gcc -v
> 
> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-v' 
> 
> [DEBUG]Configured with: 
> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> 
> [DEBUG]Apple LLVM version 7.0.0 (clang-700.1.76)
> 
> [DEBUG]Target: x86_64-apple-darwin15.0.0
> 
> [DEBUG]Thread model: posix
> 
> [DEBUG]  Checking that we can run gcc -v: done in 0.00s (at 00:03)
> 
> [DEBUG]  =
> 
> [DEBUG]  Checking that gcc can compile a trivial program
> 
> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-O2' '-g' 
> '-pipe' '/Volumes/CaSe/.build/arm-JoesBeaglebone-linux-gnueabi/build/test.c' 
> '-o' '/Volumes/CaSe/.build/arm-unknown-linux-gnueabi/build/.gccout' 
> 
> [DEBUG]  Checking that gcc can compile a trivial program: done in 0.00s (at 
> 00:03)
> 
> [EXTRA]  Installing user-supplied crossto

Re: [beagleboard] Re: Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

>
> *I ended up installing Debian Jessie on an old Macbook (the original one
> actually, version 1,1) and everything just works great with it. After
> playing around a bit on the Mac I decided to buy a new Dell XPS 13 for
> development (warning there... you'll need to run Debian unstable with the
> 4.3 experimental kernel in order to support the new Skylake architecture
> but figuring all that out was MUCH easier than trying to build a cross
> compiler toolchain for Xcode). As for getting get the USB working... I
> never did but it looks like there's been some progress in the past few
> weeks. Check out Robert's post. *
>

This is probably the best move anyone could make. That is using an i386 /
i386-64 Linux ( and why not debian ? ) system for development. There are
simply too many factors to consider when using anything else, and while
probably not impossible. It is simply too much of a hassle.

So, I run Windows, and have the capability to use Linaro's Windows binaries
for a cross toolchain - But I don't. I've actually set this up with
code:blocks, and it works fine. But there are so many dahmed hoops to jump
through for even the simplest things like using a third party library. It's
just not worth it.

Passed that though . . .


   1. Mount an NFS share on the Beglebone from this dev system.
   2. Set up a Samba share from that NFS share root.
   3. Map that Samba share on your host system.
   4. Use editor of choice, on host to write code that seems local, but is
   actually remote.
   5. Compile natively on the Beaglebone using ssh / gcc, etc.


Definitively there are simply ways to get a single file, or a few files
over to the target(Beaglebone ). But for multiple files / projects this is
the method that I personally find the best / easiest.

On Tue, Nov 17, 2015 at 1:26 PM, Joe Ciarcia  wrote:

> I gave up on using OS X El Cap and Xcode for development on the
> Beaglebone. I posted to the crosstool-ng list to see if anyone could help
> with the errors I was seeing and I didn't get any responses (even though
> it's a pretty active list, I just suspect very few people are trying to do
> cross platform development for the arm on a Mac). I ended up installing
> Debian Jessie on an old Macbook (the original one actually, version 1,1)
> and everything just works great with it. After playing around a bit on the
> Mac I decided to buy a new Dell XPS 13 for development (warning there...
> you'll need to run Debian unstable with the 4.3 experimental kernel in
> order to support the new Skylake architecture but figuring all that out was
> MUCH easier than trying to build a cross compiler toolchain for Xcode). As
> for getting get the USB working... I never did but it looks like there's
> been some progress in the past few weeks. Check out Robert's post.
>
> As for connecting to it via ethernet (which is pretty easy)... you can
> either connect it directly to the ethernet port on your Mac, or you can
> connect it to your router. To log in all you have to do is open a terminal
> and ssh in...
>
> ssh root@beaglebone.local
>
> You don't have to fool around with IP addresses etc. as most of the
> tutorials indicate. Much easier that way. Once you're in though, create a
> new user so that you're not using root all the time.
>
> If you want to go the Debian route, I highly recommend this video from
> Derek Molloy to get things started. It will show you how to get the Eclipse
> IDE up and running which will allow you to do cross compilation, remote
> deployment of your binaries, and remote debugging. It's pretty slick!
>
> https://www.youtube.com/watch?v=T9yFyWsyyGk
>
> Cheers, Joe
>
> On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5, theobo...@gmail.com
> wrote:
>>
>> Dear Joe,
>>
>> I see you are running os 10.11, me too.
>> I'm not getting the BBB to be recognized by my mac.
>> And when i'm trying to install the Serial driver, i get an error
>> Can you help me?
>>
>> Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
>>>
>>> I've found some great resources out there that help us Mac folk out with
>>> building an arm toolchain on the OS X platform. Here they are if any others
>>> stumble across this thread looking for the same:
>>>
>>> http://www.benmont.com/tech/crosscompiler.html
>>> http://will-tm.com/cross-compiling-mac-os-x-mavericks/
>>> http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html
>>>  (this one is the most detailed)
>>>
>>>
>>> I've gotten through a few of the stumbling blocks but I'm currently
>>> stuck. I get this far:
>>>
>>> [INFO ]  Performing some trivial sanity checks
>>>
>>> [INFO ]  Build started 20151023.200552
>>>
>>> [INFO ]  Building environment variables
>>>
>>> [00:03] /
>>>
>>>
>>> So, after that, if I look at the activity monitor, bash is around 100%
>>> processor utilization on one of the cores. I figure "great, it's doing
>>> something". I left it to do its thing and after an hour, I killed the
>>> process. I changed a few settings... ran it again.

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[John Syne]

Hi William,

I don’t want to prompt an argument here, but I am curious. Where is it that you 
believe Windows adds value here? I accept that you have a windows machine, but 
why not run Debian or Ubuntu on Virtualbox or VMWare and avoid all the 
complications of Windows? I use OSX for all my Nodejs/Angularjs/HTML 
development and then I use Ubuntu for my embedded development. The only reason 
I use Windows is to run Solidworks and Altium, and my only hope is that one day 
I can run these on OSX or Linux. 

Regards,
John




> On Nov 17, 2015, at 3:41 PM, William Hermans  wrote:
> 
> I ended up installing Debian Jessie on an old Macbook (the original one 
> actually, version 1,1) and everything just works great with it. After playing 
> around a bit on the Mac I decided to buy a new Dell XPS 13 for development 
> (warning there... you'll need to run Debian unstable with the 4.3 
> experimental kernel in order to support the new Skylake architecture but 
> figuring all that out was MUCH easier than trying to build a cross compiler 
> toolchain for Xcode). As for getting get the USB working... I never did but 
> it looks like there's been some progress in the past few weeks. Check out 
> Robert's post. 
> 
> This is probably the best move anyone could make. That is using an i386 / 
> i386-64 Linux ( and why not debian ? ) system for development. There are 
> simply too many factors to consider when using anything else, and while 
> probably not impossible. It is simply too much of a hassle. 
> 
> So, I run Windows, and have the capability to use Linaro's Windows binaries 
> for a cross toolchain - But I don't. I've actually set this up with 
> code:blocks, and it works fine. But there are so many dahmed hoops to jump 
> through for even the simplest things like using a third party library. It's 
> just not worth it. 
> 
> Passed that though . . .
> 
> Mount an NFS share on the Beglebone from this dev system.
> Set up a Samba share from that NFS share root.
> Map that Samba share on your host system.
> Use editor of choice, on host to write code that seems local, but is actually 
> remote.
> Compile natively on the Beaglebone using ssh / gcc, etc.
> 
> Definitively there are simply ways to get a single file, or a few files over 
> to the target(Beaglebone ). But for multiple files / projects this is the 
> method that I personally find the best / easiest.
> 
> On Tue, Nov 17, 2015 at 1:26 PM, Joe Ciarcia  > wrote:
> I gave up on using OS X El Cap and Xcode for development on the Beaglebone. I 
> posted to the crosstool-ng list to see if anyone could help with the errors I 
> was seeing and I didn't get any responses (even though it's a pretty active 
> list, I just suspect very few people are trying to do cross platform 
> development for the arm on a Mac). I ended up installing Debian Jessie on an 
> old Macbook (the original one actually, version 1,1) and everything just 
> works great with it. After playing around a bit on the Mac I decided to buy a 
> new Dell XPS 13 for development (warning there... you'll need to run Debian 
> unstable with the 4.3 experimental kernel in order to support the new Skylake 
> architecture but figuring all that out was MUCH easier than trying to build a 
> cross compiler toolchain for Xcode). As for getting get the USB working... I 
> never did but it looks like there's been some progress in the past few weeks. 
> Check out Robert's post. 
> 
> As for connecting to it via ethernet (which is pretty easy)... you can either 
> connect it directly to the ethernet port on your Mac, or you can connect it 
> to your router. To log in all you have to do is open a terminal and ssh in...
> 
> ssh root@beaglebone.local
> 
> You don't have to fool around with IP addresses etc. as most of the tutorials 
> indicate. Much easier that way. Once you're in though, create a new user so 
> that you're not using root all the time.
> 
> If you want to go the Debian route, I highly recommend this video from Derek 
> Molloy to get things started. It will show you how to get the Eclipse IDE up 
> and running which will allow you to do cross compilation, remote deployment 
> of your binaries, and remote debugging. It's pretty slick!
> 
> https://www.youtube.com/watch?v=T9yFyWsyyGk 
> 
> 
> Cheers, Joe
> 
> On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5, theobo...@gmail.com 
>  wrote:
> Dear Joe,
> 
> I see you are running os 10.11, me too.
> I'm not getting the BBB to be recognized by my mac.
> And when i'm trying to install the Serial driver, i get an error
> Can you help me?
> 
> Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
> I've found some great resources out there that help us Mac folk out with 
> building an arm toolchain on the OS X platform. Here they are if any others 
> stumble across this thread looking for the same:
> 
> http://www.benmont.com/tech/crosscompiler.html 

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[evilwulfie]

re read what he said. i think you misunderstood him.

On 11/17/2015 5:32 PM, John Syne wrote:
> Hi William,
>
> I don’t want to prompt an argument here, but I am curious. Where is it
> that you believe Windows adds value here? I accept that you have a
> windows machine, but why not run Debian or Ubuntu on Virtualbox or
> VMWare and avoid all the complications of Windows? I use OSX for all
> my Nodejs/Angularjs/HTML development and then I use Ubuntu for my
> embedded development. The only reason I use Windows is to run
> Solidworks and Altium, and my only hope is that one day I can run
> these on OSX or Linux. 
>
> Regards,
> John
>
>
>
>
>> On Nov 17, 2015, at 3:41 PM, William Hermans > > wrote:
>>
>> /I ended up installing Debian Jessie on an old Macbook (the
>> original one actually, version 1,1) and everything just works
>> great with it. After playing around a bit on the Mac I decided to
>> buy a new Dell XPS 13 for development (warning there... you'll
>> need to run Debian unstable with the 4.3 experimental kernel in
>> order to support the new Skylake architecture but figuring all
>> that out was MUCH easier than trying to build a cross compiler
>> toolchain for Xcode). As for getting get the USB working... I
>> never did but it looks like there's been some progress in the
>> past few weeks. Check out Robert's post. /
>>
>>
>> This is probably the best move anyone could make. That is using an
>> i386 / i386-64 Linux ( and why not debian ? ) system for development.
>> There are simply too many factors to consider when using anything
>> else, and while probably not impossible. It is simply too much of a
>> hassle.
>>
>> So, I run Windows, and have the capability to use Linaro's Windows
>> binaries for a cross toolchain - But I don't. I've actually set this
>> up with code:blocks, and it works fine. But there are so many dahmed
>> hoops to jump through for even the simplest things like using a third
>> party library. It's just not worth it.
>>
>> Passed that though . . .
>>
>>  1. Mount an NFS share on the Beglebone from this dev system.
>>  2. Set up a Samba share from that NFS share root.
>>  3. Map that Samba share on your host system.
>>  4. Use editor of choice, on host to write code that seems local, but
>> is actually remote.
>>  5. Compile natively on the Beaglebone using ssh / gcc, etc.
>>
>>
>> Definitively there are simply ways to get a single file, or a few
>> files over to the target(Beaglebone ). But for multiple files /
>> projects this is the method that I personally find the best / easiest.
>>
>> On Tue, Nov 17, 2015 at 1:26 PM, Joe Ciarcia > > wrote:
>>
>> I gave up on using OS X El Cap and Xcode for development on the
>> Beaglebone. I posted to the crosstool-ng list to see if anyone
>> could help with the errors I was seeing and I didn't get any
>> responses (even though it's a pretty active list, I just suspect
>> very few people are trying to do cross platform development for
>> the arm on a Mac). I ended up installing Debian Jessie on an old
>> Macbook (the original one actually, version 1,1) and everything
>> just works great with it. After playing around a bit on the Mac I
>> decided to buy a new Dell XPS 13 for development (warning
>> there... you'll need to run Debian unstable with the 4.3
>> experimental kernel in order to support the new Skylake
>> architecture but figuring all that out was MUCH easier than
>> trying to build a cross compiler toolchain for Xcode). As for
>> getting get the USB working... I never did but it looks like
>> there's been some progress in the past few weeks. Check out
>> Robert's post. 
>>
>> As for connecting to it via ethernet (which is pretty easy)...
>> you can either connect it directly to the ethernet port on your
>> Mac, or you can connect it to your router. To log in all you have
>> to do is open a terminal and ssh in...
>>
>> ssh root@beaglebone.local 
>>
>> You don't have to fool around with IP addresses etc. as most of
>> the tutorials indicate. Much easier that way. Once you're in
>> though, create a new user so that you're not using root all the time.
>>
>> If you want to go the Debian route, I highly recommend this video
>> from Derek Molloy to get things started. It will show you how to
>> get the Eclipse IDE up and running which will allow you to do
>> cross compilation, remote deployment of your binaries, and remote
>> debugging. It's pretty slick!
>>
>> https://www.youtube.com/watch?v=T9yFyWsyyGk
>>
>> Cheers, Joe
>>
>> On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5,
>> theobo...@gmail.com  wrote:
>>
>> Dear Joe,
>>
>> I see you are running os 10.11, me too.
>> I'm not getting the BBB to be recognized by my mac.
>>   

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

>
> *Hi William,*
>
> *I don’t want to prompt an argument here, but I am curious. Where is it
> that you believe Windows adds value here? I accept that you have a windows
> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
> all the complications of Windows? I use OSX for all my
> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
> development. The only reason I use Windows is to run Solidworks and Altium,
> and my only hope is that one day I can run these on OSX or Linux. *
>
> *Regards,*
> *John*
>

Like wulf said, you misunderstood what I was saying.  I have two systems
that are completely dedicated to Beaglebone development. Both run Debian
wheezy, and one is i386, where the other is x64. Both are headless, and do
not run any GUI garbage at all. Why 2 ? Imagine for a minute compiling the
kernel from a 8-12G tmpfs . . . that requires an X64 system, where the i386
system is mostly a storage repository . . .

So why do I write code from Windows ?


   1. I get to use the editor I prefer.
   2. I do not have to crap up the other systems with GUI garbage.
   3. After having been using MS OSes since the early 90's ( Linux this
   long too ) I've become accustomed to the Windows GUI.


In, short. It's a matter of preference.

Honestly though, I very seriously wonder why OSX users think OSX adds value
to this sort of thing myself. . .

On Tue, Nov 17, 2015 at 5:56 PM, evilwulfie  wrote:

> re read what he said. i think you misunderstood him.
>
>
> On 11/17/2015 5:32 PM, John Syne wrote:
>
> Hi William,
>
> I don’t want to prompt an argument here, but I am curious. Where is it
> that you believe Windows adds value here? I accept that you have a windows
> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
> all the complications of Windows? I use OSX for all my
> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
> development. The only reason I use Windows is to run Solidworks and Altium,
> and my only hope is that one day I can run these on OSX or Linux.
>
> Regards,
> John
>
>
>
>
> On Nov 17, 2015, at 3:41 PM, William Hermans  wrote:
>
> *I ended up installing Debian Jessie on an old Macbook (the original one
>> actually, version 1,1) and everything just works great with it. After
>> playing around a bit on the Mac I decided to buy a new Dell XPS 13 for
>> development (warning there... you'll need to run Debian unstable with the
>> 4.3 experimental kernel in order to support the new Skylake architecture
>> but figuring all that out was MUCH easier than trying to build a cross
>> compiler toolchain for Xcode). As for getting get the USB working... I
>> never did but it looks like there's been some progress in the past few
>> weeks. Check out Robert's post. *
>>
>
> This is probably the best move anyone could make. That is using an i386 /
> i386-64 Linux ( and why not debian ? ) system for development. There are
> simply too many factors to consider when using anything else, and while
> probably not impossible. It is simply too much of a hassle.
>
> So, I run Windows, and have the capability to use Linaro's Windows
> binaries for a cross toolchain - But I don't. I've actually set this up
> with code:blocks, and it works fine. But there are so many dahmed hoops
> to jump through for even the simplest things like using a third party
> library. It's just not worth it.
>
> Passed that though . . .
>
>
>1. Mount an NFS share on the Beglebone from this dev system.
>2. Set up a Samba share from that NFS share root.
>3. Map that Samba share on your host system.
>4. Use editor of choice, on host to write code that seems local, but
>is actually remote.
>5. Compile natively on the Beaglebone using ssh / gcc, etc.
>
>
> Definitively there are simply ways to get a single file, or a few files
> over to the target(Beaglebone ). But for multiple files / projects this is
> the method that I personally find the best / easiest.
>
> On Tue, Nov 17, 2015 at 1:26 PM, Joe Ciarcia < 
> jazzka...@gmail.com> wrote:
>
>> I gave up on using OS X El Cap and Xcode for development on the
>> Beaglebone. I posted to the crosstool-ng list to see if anyone could help
>> with the errors I was seeing and I didn't get any responses (even though
>> it's a pretty active list, I just suspect very few people are trying to do
>> cross platform development for the arm on a Mac). I ended up installing
>> Debian Jessie on an old Macbook (the original one actually, version 1,1)
>> and everything just works great with it. After playing around a bit on the
>> Mac I decided to buy a new Dell XPS 13 for development (warning there...
>> you'll need to run Debian unstable with the 4.3 experimental kernel in
>> order to support the new Skylake architecture but figuring all that out was
>> MUCH easier than trying to build a cross compiler toolchain for Xcode). As
>> for getting get the USB working... I never did but it looks like there's
>> been so

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

Not to mention the main point I was trying to put across is that Linux is
not necessarily my primary Desktop OS either . . .

On Tue, Nov 17, 2015 at 7:20 PM, William Hermans  wrote:

> *Hi William,*
>>
>> *I don’t want to prompt an argument here, but I am curious. Where is it
>> that you believe Windows adds value here? I accept that you have a windows
>> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
>> all the complications of Windows? I use OSX for all my
>> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
>> development. The only reason I use Windows is to run Solidworks and Altium,
>> and my only hope is that one day I can run these on OSX or Linux. *
>>
>> *Regards,*
>> *John*
>>
>
> Like wulf said, you misunderstood what I was saying.  I have two systems
> that are completely dedicated to Beaglebone development. Both run Debian
> wheezy, and one is i386, where the other is x64. Both are headless, and do
> not run any GUI garbage at all. Why 2 ? Imagine for a minute compiling the
> kernel from a 8-12G tmpfs . . . that requires an X64 system, where the i386
> system is mostly a storage repository . . .
>
> So why do I write code from Windows ?
>
>
>1. I get to use the editor I prefer.
>2. I do not have to crap up the other systems with GUI garbage.
>3. After having been using MS OSes since the early 90's ( Linux this
>long too ) I've become accustomed to the Windows GUI.
>
>
> In, short. It's a matter of preference.
>
> Honestly though, I very seriously wonder why OSX users think OSX adds
> value to this sort of thing myself. . .
>
> On Tue, Nov 17, 2015 at 5:56 PM, evilwulfie  wrote:
>
>> re read what he said. i think you misunderstood him.
>>
>>
>> On 11/17/2015 5:32 PM, John Syne wrote:
>>
>> Hi William,
>>
>> I don’t want to prompt an argument here, but I am curious. Where is it
>> that you believe Windows adds value here? I accept that you have a windows
>> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
>> all the complications of Windows? I use OSX for all my
>> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
>> development. The only reason I use Windows is to run Solidworks and Altium,
>> and my only hope is that one day I can run these on OSX or Linux.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Nov 17, 2015, at 3:41 PM, William Hermans  wrote:
>>
>> *I ended up installing Debian Jessie on an old Macbook (the original one
>>> actually, version 1,1) and everything just works great with it. After
>>> playing around a bit on the Mac I decided to buy a new Dell XPS 13 for
>>> development (warning there... you'll need to run Debian unstable with the
>>> 4.3 experimental kernel in order to support the new Skylake architecture
>>> but figuring all that out was MUCH easier than trying to build a cross
>>> compiler toolchain for Xcode). As for getting get the USB working... I
>>> never did but it looks like there's been some progress in the past few
>>> weeks. Check out Robert's post. *
>>>
>>
>> This is probably the best move anyone could make. That is using an i386 /
>> i386-64 Linux ( and why not debian ? ) system for development. There are
>> simply too many factors to consider when using anything else, and while
>> probably not impossible. It is simply too much of a hassle.
>>
>> So, I run Windows, and have the capability to use Linaro's Windows
>> binaries for a cross toolchain - But I don't. I've actually set this up
>> with code:blocks, and it works fine. But there are so many dahmed hoops
>> to jump through for even the simplest things like using a third party
>> library. It's just not worth it.
>>
>> Passed that though . . .
>>
>>
>>1. Mount an NFS share on the Beglebone from this dev system.
>>2. Set up a Samba share from that NFS share root.
>>3. Map that Samba share on your host system.
>>4. Use editor of choice, on host to write code that seems local, but
>>is actually remote.
>>5. Compile natively on the Beaglebone using ssh / gcc, etc.
>>
>>
>> Definitively there are simply ways to get a single file, or a few files
>> over to the target(Beaglebone ). But for multiple files / projects this is
>> the method that I personally find the best / easiest.
>>
>> On Tue, Nov 17, 2015 at 1:26 PM, Joe Ciarcia < 
>> jazzka...@gmail.com> wrote:
>>
>>> I gave up on using OS X El Cap and Xcode for development on the
>>> Beaglebone. I posted to the crosstool-ng list to see if anyone could help
>>> with the errors I was seeing and I didn't get any responses (even though
>>> it's a pretty active list, I just suspect very few people are trying to do
>>> cross platform development for the arm on a Mac). I ended up installing
>>> Debian Jessie on an old Macbook (the original one actually, version 1,1)
>>> and everything just works great with it. After playing around a bit on the
>>> Mac I decided to buy a new Dell XPS 13 for development (warning there...
>>> you'll ne

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[John Syne]

Hi William,

With a smile on my face; why OSX? Watch any video training on web development 
and 95% use OSX (Lynda, Pluralsight, Udemy, Infiniteskills, etc). Watch any web 
development conference presentation and again about 95% are presented on OSX. 
When I say 95%, I mean in the vast majority of cases. I don’t recall the last 
time I saw someone using Windows. 

OSX is just Unix with a easy to use GUI, but most important, the hardware works 
great (long battery life, no fan noise, does not get hot, stable, beautify 
display, thunderbolt and very fast). OSX doesn’t use slow SATA hard drives, 
they use PCI express interfaces to SSD so you get way faster disk access. For 
backups, you just cannot beat Time-Machine. I have two external Thunderbolt 
disks running Time-Machine so the backups alternate each hour between both 
disks. Monitors disk SMART parameters to detect potential disk failure. 

Most important, I don’t see those annoying, shitty updates each time I shutdown 
or startup. Oh, I forgot, I almost never shutdown. Several years ago my family 
(wife, kids, dad, etc) made the transition to OSX and every since, I don’t get 
those daily calls about system crashes or files missing or some other crappy 
windows error dialog. 

Sorry for the rant. I just hate Windows and I love OSX. 

BTW, watch Jason Kridner’s presentations on BBB. He uses OSX. 

Regards,
John




> On Nov 17, 2015, at 7:36 PM, William Hermans  wrote:
> 
> Not to mention the main point I was trying to put across is that Linux is not 
> necessarily my primary Desktop OS either . . . 
> 
> On Tue, Nov 17, 2015 at 7:20 PM, William Hermans  > wrote:
> Hi William,
> 
> I don’t want to prompt an argument here, but I am curious. Where is it that 
> you believe Windows adds value here? I accept that you have a windows 
> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid 
> all the complications of Windows? I use OSX for all my Nodejs/Angularjs/HTML 
> development and then I use Ubuntu for my embedded development. The only 
> reason I use Windows is to run Solidworks and Altium, and my only hope is 
> that one day I can run these on OSX or Linux. 
> 
> Regards,
> John
> 
> Like wulf said, you misunderstood what I was saying.  I have two systems that 
> are completely dedicated to Beaglebone development. Both run Debian wheezy, 
> and one is i386, where the other is x64. Both are headless, and do not run 
> any GUI garbage at all. Why 2 ? Imagine for a minute compiling the kernel 
> from a 8-12G tmpfs . . . that requires an X64 system, where the i386 system 
> is mostly a storage repository . . .
> 
> So why do I write code from Windows ?
> 
> I get to use the editor I prefer.
> I do not have to crap up the other systems with GUI garbage.
> After having been using MS OSes since the early 90's ( Linux this long too ) 
> I've become accustomed to the Windows GUI.
> 
> In, short. It's a matter of preference.
> 
> Honestly though, I very seriously wonder why OSX users think OSX adds value 
> to this sort of thing myself. . . 
> 
> On Tue, Nov 17, 2015 at 5:56 PM, evilwulfie  > wrote:
> re read what he said. i think you misunderstood him.
> 
> 
> On 11/17/2015 5:32 PM, John Syne wrote:
>> Hi William,
>> 
>> I don’t want to prompt an argument here, but I am curious. Where is it that 
>> you believe Windows adds value here? I accept that you have a windows 
>> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid 
>> all the complications of Windows? I use OSX for all my Nodejs/Angularjs/HTML 
>> development and then I use Ubuntu for my embedded development. The only 
>> reason I use Windows is to run Solidworks and Altium, and my only hope is 
>> that one day I can run these on OSX or Linux. 
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Nov 17, 2015, at 3:41 PM, William Hermans >> > wrote:
>>> 
>>> I ended up installing Debian Jessie on an old Macbook (the original one 
>>> actually, version 1,1) and everything just works great with it. After 
>>> playing around a bit on the Mac I decided to buy a new Dell XPS 13 for 
>>> development (warning there... you'll need to run Debian unstable with the 
>>> 4.3 experimental kernel in order to support the new Skylake architecture 
>>> but figuring all that out was MUCH easier than trying to build a cross 
>>> compiler toolchain for Xcode). As for getting get the USB working... I 
>>> never did but it looks like there's been some progress in the past few 
>>> weeks.   Check out Robert's post. 
>>> 
>>> This is probably the best move anyone could make. That is using an i386 / 
>>> i386-64 Linux ( and why not debian ? ) system for development. There are 
>>> simply too many factors to consider when using anything else, and while 
>>> probably not impossible. It is simply too much of a hassle. 
>>> 
>>> So, I run Windows, and have the capability to use Li

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

>
>
> *Sorry for the rant. I just hate Windows and I love OSX. *
>

To sum things up. Any OS is only as good as the user using it. None are
perfect, and they all have major flaws. I refuse to use OSX because it
comes attached to hardware that is ridiculously priced. That's a personal
decision aside from all the flaws OSX has. Never mind the high end laptop I
own for half the cost of a MBP, that will outperform a MBP in every thing.
It only gets better, because if for some reason I decide I do not like
Windows an longer. I do not have to pretend I'm running BSD, I can install
and run the real thing. Or Linux, or whatever OS I like. Bootcamp ? pffft,
such a silly notion. How about boot *disk* ?

As far as what other people use for an OS. I could care less. I'm not an OS
crony . . . But I will say I can not remember the last time I've seen
anyone in person who uses OSX.  A friends wife has an MBP, that was given
to her for her birthday a couple years ago . . . and shes a Windows person.

Anyway, you can blame Windows for your problem all you want. Bottom line
is, either the hardware running said Windows was garbage, or you just did
not know how to use it . . .I know, I know, Windows looks simple. But in
order to use it correctly one needs to understand how it works, and how to
do things.

On Tue, Nov 17, 2015 at 10:38 PM, John Syne  wrote:

> Hi William,
>
> With a smile on my face; why OSX? Watch any video training on web
> development and 95% use OSX (Lynda, Pluralsight, Udemy, Infiniteskills,
> etc). Watch any web development conference presentation and again about 95%
> are presented on OSX. When I say 95%, I mean in the vast majority of cases.
> I don’t recall the last time I saw someone using Windows.
>
> OSX is just Unix with a easy to use GUI, but most important, the hardware
> works great (long battery life, no fan noise, does not get hot, stable,
> beautify display, thunderbolt and very fast). OSX doesn’t use slow SATA
> hard drives, they use PCI express interfaces to SSD so you get way faster
> disk access. For backups, you just cannot beat Time-Machine. I have two
> external Thunderbolt disks running Time-Machine so the backups alternate
> each hour between both disks. Monitors disk SMART parameters to detect
> potential disk failure.
>
> Most important, I don’t see those annoying, shitty updates each time I
> shutdown or startup. Oh, I forgot, I almost never shutdown. Several years
> ago my family (wife, kids, dad, etc) made the transition to OSX and every
> since, I don’t get those daily calls about system crashes or files missing
> or some other crappy windows error dialog.
>
> Sorry for the rant. I just hate Windows and I love OSX.
>
> BTW, watch Jason Kridner’s presentations on BBB. He uses OSX.
>
> Regards,
> John
>
>
>
>
> On Nov 17, 2015, at 7:36 PM, William Hermans  wrote:
>
> Not to mention the main point I was trying to put across is that Linux is
> not necessarily my primary Desktop OS either . . .
>
> On Tue, Nov 17, 2015 at 7:20 PM, William Hermans 
> wrote:
>
>> *Hi William,*
>>>
>>> *I don’t want to prompt an argument here, but I am curious. Where is it
>>> that you believe Windows adds value here? I accept that you have a windows
>>> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
>>> all the complications of Windows? I use OSX for all my
>>> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
>>> development. The only reason I use Windows is to run Solidworks and Altium,
>>> and my only hope is that one day I can run these on OSX or Linux. *
>>>
>>> *Regards,*
>>> *John*
>>>
>>
>> Like wulf said, you misunderstood what I was saying.  I have two systems
>> that are completely dedicated to Beaglebone development. Both run Debian
>> wheezy, and one is i386, where the other is x64. Both are headless, and do
>> not run any GUI garbage at all. Why 2 ? Imagine for a minute compiling the
>> kernel from a 8-12G tmpfs . . . that requires an X64 system, where the i386
>> system is mostly a storage repository . . .
>>
>> So why do I write code from Windows ?
>>
>>
>>1. I get to use the editor I prefer.
>>2. I do not have to crap up the other systems with GUI garbage.
>>3. After having been using MS OSes since the early 90's ( Linux this
>>long too ) I've become accustomed to the Windows GUI.
>>
>>
>> In, short. It's a matter of preference.
>>
>> Honestly though, I very seriously wonder why OSX users think OSX adds
>> value to this sort of thing myself. . .
>>
>> On Tue, Nov 17, 2015 at 5:56 PM, evilwulfie  wrote:
>>
>>> re read what he said. i think you misunderstood him.
>>>
>>>
>>> On 11/17/2015 5:32 PM, John Syne wrote:
>>>
>>> Hi William,
>>>
>>> I don’t want to prompt an argument here, but I am curious. Where is it
>>> that you believe Windows adds value here? I accept that you have a windows
>>> machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
>>> all the complications of Windows? I use OSX for a

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

The point is however. It does not matter which OS, anyone uses for a
desktop. A development system that should be separate, and a tool, that in
this case is best used with Linux.

But apparently that does not stop people from trying . . . and we're seeing
how that works out - aren't we ?

On Wed, Nov 18, 2015 at 12:10 AM, William Hermans  wrote:

>
>> *Sorry for the rant. I just hate Windows and I love OSX. *
>>
>
> To sum things up. Any OS is only as good as the user using it. None are
> perfect, and they all have major flaws. I refuse to use OSX because it
> comes attached to hardware that is ridiculously priced. That's a personal
> decision aside from all the flaws OSX has. Never mind the high end laptop I
> own for half the cost of a MBP, that will outperform a MBP in every thing.
> It only gets better, because if for some reason I decide I do not like
> Windows an longer. I do not have to pretend I'm running BSD, I can install
> and run the real thing. Or Linux, or whatever OS I like. Bootcamp ? pffft,
> such a silly notion. How about boot *disk* ?
>
> As far as what other people use for an OS. I could care less. I'm not an
> OS crony . . . But I will say I can not remember the last time I've seen
> anyone in person who uses OSX.  A friends wife has an MBP, that was given
> to her for her birthday a couple years ago . . . and shes a Windows person.
>
> Anyway, you can blame Windows for your problem all you want. Bottom line
> is, either the hardware running said Windows was garbage, or you just did
> not know how to use it . . .I know, I know, Windows looks simple. But in
> order to use it correctly one needs to understand how it works, and how to
> do things.
>
> On Tue, Nov 17, 2015 at 10:38 PM, John Syne  wrote:
>
>> Hi William,
>>
>> With a smile on my face; why OSX? Watch any video training on web
>> development and 95% use OSX (Lynda, Pluralsight, Udemy, Infiniteskills,
>> etc). Watch any web development conference presentation and again about 95%
>> are presented on OSX. When I say 95%, I mean in the vast majority of cases.
>> I don’t recall the last time I saw someone using Windows.
>>
>> OSX is just Unix with a easy to use GUI, but most important, the hardware
>> works great (long battery life, no fan noise, does not get hot, stable,
>> beautify display, thunderbolt and very fast). OSX doesn’t use slow SATA
>> hard drives, they use PCI express interfaces to SSD so you get way faster
>> disk access. For backups, you just cannot beat Time-Machine. I have two
>> external Thunderbolt disks running Time-Machine so the backups alternate
>> each hour between both disks. Monitors disk SMART parameters to detect
>> potential disk failure.
>>
>> Most important, I don’t see those annoying, shitty updates each time I
>> shutdown or startup. Oh, I forgot, I almost never shutdown. Several years
>> ago my family (wife, kids, dad, etc) made the transition to OSX and every
>> since, I don’t get those daily calls about system crashes or files missing
>> or some other crappy windows error dialog.
>>
>> Sorry for the rant. I just hate Windows and I love OSX.
>>
>> BTW, watch Jason Kridner’s presentations on BBB. He uses OSX.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Nov 17, 2015, at 7:36 PM, William Hermans  wrote:
>>
>> Not to mention the main point I was trying to put across is that Linux is
>> not necessarily my primary Desktop OS either . . .
>>
>> On Tue, Nov 17, 2015 at 7:20 PM, William Hermans 
>> wrote:
>>
>>> *Hi William,*

 *I don’t want to prompt an argument here, but I am curious. Where is it
 that you believe Windows adds value here? I accept that you have a windows
 machine, but why not run Debian or Ubuntu on Virtualbox or VMWare and avoid
 all the complications of Windows? I use OSX for all my
 Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
 development. The only reason I use Windows is to run Solidworks and Altium,
 and my only hope is that one day I can run these on OSX or Linux. *

 *Regards,*
 *John*

>>>
>>> Like wulf said, you misunderstood what I was saying.  I have two systems
>>> that are completely dedicated to Beaglebone development. Both run Debian
>>> wheezy, and one is i386, where the other is x64. Both are headless, and do
>>> not run any GUI garbage at all. Why 2 ? Imagine for a minute compiling the
>>> kernel from a 8-12G tmpfs . . . that requires an X64 system, where the i386
>>> system is mostly a storage repository . . .
>>>
>>> So why do I write code from Windows ?
>>>
>>>
>>>1. I get to use the editor I prefer.
>>>2. I do not have to crap up the other systems with GUI garbage.
>>>3. After having been using MS OSes since the early 90's ( Linux this
>>>long too ) I've become accustomed to the Windows GUI.
>>>
>>>
>>> In, short. It's a matter of preference.
>>>
>>> Honestly though, I very seriously wonder why OSX users think OSX adds
>>> value to this sort of thing myself. . .
>>>
>>> On Tue

Re: [beagleboard] Setting up cross compiler under OS X 10.11 / El Capitan

[William Hermans]

>
> *A development system that should be separate, and a tool, that in this
> case is best used with Linux.*
>

A development system is a system that should be separate, and is a tool
that should run Linux in this case.

On Wed, Nov 18, 2015 at 12:41 AM, William Hermans  wrote:

> The point is however. It does not matter which OS, anyone uses for a
> desktop. A development system that should be separate, and a tool, that in
> this case is best used with Linux.
>
> But apparently that does not stop people from trying . . . and we're
> seeing how that works out - aren't we ?
>
> On Wed, Nov 18, 2015 at 12:10 AM, William Hermans 
> wrote:
>
>>
>>> *Sorry for the rant. I just hate Windows and I love OSX. *
>>>
>>
>> To sum things up. Any OS is only as good as the user using it. None are
>> perfect, and they all have major flaws. I refuse to use OSX because it
>> comes attached to hardware that is ridiculously priced. That's a personal
>> decision aside from all the flaws OSX has. Never mind the high end laptop I
>> own for half the cost of a MBP, that will outperform a MBP in every thing.
>> It only gets better, because if for some reason I decide I do not like
>> Windows an longer. I do not have to pretend I'm running BSD, I can install
>> and run the real thing. Or Linux, or whatever OS I like. Bootcamp ? pffft,
>> such a silly notion. How about boot *disk* ?
>>
>> As far as what other people use for an OS. I could care less. I'm not an
>> OS crony . . . But I will say I can not remember the last time I've seen
>> anyone in person who uses OSX.  A friends wife has an MBP, that was given
>> to her for her birthday a couple years ago . . . and shes a Windows person.
>>
>> Anyway, you can blame Windows for your problem all you want. Bottom line
>> is, either the hardware running said Windows was garbage, or you just did
>> not know how to use it . . .I know, I know, Windows looks simple. But in
>> order to use it correctly one needs to understand how it works, and how to
>> do things.
>>
>> On Tue, Nov 17, 2015 at 10:38 PM, John Syne  wrote:
>>
>>> Hi William,
>>>
>>> With a smile on my face; why OSX? Watch any video training on web
>>> development and 95% use OSX (Lynda, Pluralsight, Udemy, Infiniteskills,
>>> etc). Watch any web development conference presentation and again about 95%
>>> are presented on OSX. When I say 95%, I mean in the vast majority of cases.
>>> I don’t recall the last time I saw someone using Windows.
>>>
>>> OSX is just Unix with a easy to use GUI, but most important, the
>>> hardware works great (long battery life, no fan noise, does not get hot,
>>> stable, beautify display, thunderbolt and very fast). OSX doesn’t use slow
>>> SATA hard drives, they use PCI express interfaces to SSD so you get way
>>> faster disk access. For backups, you just cannot beat Time-Machine. I have
>>> two external Thunderbolt disks running Time-Machine so the backups
>>> alternate each hour between both disks. Monitors disk SMART parameters to
>>> detect potential disk failure.
>>>
>>> Most important, I don’t see those annoying, shitty updates each time I
>>> shutdown or startup. Oh, I forgot, I almost never shutdown. Several years
>>> ago my family (wife, kids, dad, etc) made the transition to OSX and every
>>> since, I don’t get those daily calls about system crashes or files missing
>>> or some other crappy windows error dialog.
>>>
>>> Sorry for the rant. I just hate Windows and I love OSX.
>>>
>>> BTW, watch Jason Kridner’s presentations on BBB. He uses OSX.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>> On Nov 17, 2015, at 7:36 PM, William Hermans  wrote:
>>>
>>> Not to mention the main point I was trying to put across is that Linux
>>> is not necessarily my primary Desktop OS either . . .
>>>
>>> On Tue, Nov 17, 2015 at 7:20 PM, William Hermans 
>>> wrote:
>>>
 *Hi William,*
>
> *I don’t want to prompt an argument here, but I am curious. Where is
> it that you believe Windows adds value here? I accept that you have a
> windows machine, but why not run Debian or Ubuntu on Virtualbox or VMWare
> and avoid all the complications of Windows? I use OSX for all my
> Nodejs/Angularjs/HTML development and then I use Ubuntu for my embedded
> development. The only reason I use Windows is to run Solidworks and 
> Altium,
> and my only hope is that one day I can run these on OSX or Linux. *
>
> *Regards,*
> *John*
>

 Like wulf said, you misunderstood what I was saying.  I have two
 systems that are completely dedicated to Beaglebone development. Both run
 Debian wheezy, and one is i386, where the other is x64. Both are headless,
 and do not run any GUI garbage at all. Why 2 ? Imagine for a minute
 compiling the kernel from a 8-12G tmpfs . . . that requires an X64 system,
 where the i386 system is mostly a storage repository . . .

 So why do I write code from Windows ?


1. I get to use the editor I prefer.