[beagleboard] Unable to compile kernel for beaglebone black

[pratik panchal]

Hi all,

I have downloaded the source code of U-BOOT and Kernel and trying to 
compile them as given in the site lhttp://elinux.org/Building_BBB_Kernel
after doing all the stuff i can't compile code of Kernel and every time it 
gives me error.
Is there any reliable source code of kernel for beaglebone black ?

-- 
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: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Adam Singer]

Wow great job Andrew! Just ran with this image with ease. Is there anything 
built in that can be used to flash to eMMC? Any plans to integrate with the 
SGX drivers for better graphics drivers?

-- 
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] debian testing: 2014-10-08 (Jessie Snapshot)

[Robert Nelson]

On Thu, Oct 9, 2014 at 6:45 PM, Charles Steinkuehler
 wrote:
> On 10/9/2014 6:42 PM, Charles Steinkuehler wrote:
>> On 10/9/2014 5:57 PM, Robert Nelson wrote:
>>>
>>> Thanks! THis is now fixed:
>>>
>>> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black
>>
>> When following the directions exactly, it fails because the
>> sgx_create_package.sh script can't source the ".CC" file.  It looks like
>> this is created by the scripts/gcc.sh when downloading the compiler, but
>> that doesn't happen unless you build the kernel first.
>
> I tried to cheat by just running scripts/gcc.sh to download the
> compiler, but when I ran ./sgx_create_package.sh again, I got:
>
>> charles@dozer:/home/maker/ti-linux-kernel-dev$ ./sgx_create_package.sh
>> Verifying: Graphics_SDK_setuplinux_hardfp_5_01_01_01.bin
>> md5sum match: 94acdbd20152c905939c2448d5e80a72
>> Graphics_SDK_setuplinux_5_01_01_01 is installed
>> Cloning into /home/maker/ti-linux-kernel-dev/ignore/ti-sdk-pvr...
>> remote: Counting objects: 1205, done.
>> remote: Total 1205 (delta 0), reused 0 (delta 0)
>> Receiving objects: 100% (1205/1205), 1.90 MiB | 1.29 MiB/s, done.
>> Resolving deltas: 100% (555/555), done.
>> Branch tmp-build set up to track remote branch 5.01.01.01-ti from origin.
>> Switched to a new branch 'tmp-build'
>> Starting: copying files from the SDK
>> Copying: es8.x to build dir
>>
>> ERROR: Run: ./build_kernel.sh first
>
> So it seems like you should just add ./build_kernel.sh to the directions
> on the elinux page.  :)

This works. ;)

https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/dd1f919b37d76493e1cc33955b1b97c351dab8be


Regards,

-- 
Robert Nelson
http://www.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] debian testing: 2014-10-08 (Jessie Snapshot)

[Charles Steinkuehler]

On 10/9/2014 6:42 PM, Charles Steinkuehler wrote:
> On 10/9/2014 5:57 PM, Robert Nelson wrote:
>>
>> Thanks! THis is now fixed:
>>
>> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black
> 
> When following the directions exactly, it fails because the
> sgx_create_package.sh script can't source the ".CC" file.  It looks like
> this is created by the scripts/gcc.sh when downloading the compiler, but
> that doesn't happen unless you build the kernel first.

I tried to cheat by just running scripts/gcc.sh to download the
compiler, but when I ran ./sgx_create_package.sh again, I got:

> charles@dozer:/home/maker/ti-linux-kernel-dev$ ./sgx_create_package.sh
> Verifying: Graphics_SDK_setuplinux_hardfp_5_01_01_01.bin
> md5sum match: 94acdbd20152c905939c2448d5e80a72
> Graphics_SDK_setuplinux_5_01_01_01 is installed
> Cloning into /home/maker/ti-linux-kernel-dev/ignore/ti-sdk-pvr...
> remote: Counting objects: 1205, done.
> remote: Total 1205 (delta 0), reused 0 (delta 0)
> Receiving objects: 100% (1205/1205), 1.90 MiB | 1.29 MiB/s, done.
> Resolving deltas: 100% (555/555), done.
> Branch tmp-build set up to track remote branch 5.01.01.01-ti from origin.
> Switched to a new branch 'tmp-build'
> Starting: copying files from the SDK
> Copying: es8.x to build dir
> 
> ERROR: Run: ./build_kernel.sh first

So it seems like you should just add ./build_kernel.sh to the directions
on the elinux page.  :)

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] debian testing: 2014-10-08 (Jessie Snapshot)

[Charles Steinkuehler]

On 10/9/2014 5:57 PM, Robert Nelson wrote:
> 
> Thanks! THis is now fixed:
> 
> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black

When following the directions exactly, it fails because the
sgx_create_package.sh script can't source the ".CC" file.  It looks like
this is created by the scripts/gcc.sh when downloading the compiler, but
that doesn't happen unless you build the kernel first.

>> IIRC there are some library blobs that cannot be redistributed?  Or do
>> they just not comply with the DFSG?
> 
> So it's the "imgtec" demo's that cause the license issue. Till TI
> physically separates the two into a lib & example download package i
> can't do nothing about packing..

Can't the required user-mode library code be distributed without the
examples once it's all compiled and linked?  Or am I missing something?

It _has_ to be possible for someone to ship a device with the SGX
drivers enabled.  Is it just not possible to make a working image
legally downloadable?  It seems like that would cause issues with
commercial folks trying to do on-line firmware updates!?!

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] debian testing: 2014-10-08 (Jessie Snapshot)

[Robert Nelson]

On Thu, Oct 9, 2014 at 5:43 PM, Charles Steinkuehler
 wrote:
> On 10/9/2014 10:45 AM, Robert Nelson wrote:
>>
>> Now for Jessie...
>
> Hooray!!!
>
>> With a big Warning, Jessie isn't frozeen yet...
>>
>> https://release.debian.org/jessie/freeze_policy.html
>>
>> So anything packaged could still be taken away.
>>
>> Desktop: lxqt 0.7.96 + qt 5.3.2
>> Kernel: 3.14.19-ti-r28 + sgx modules
>
> Is anything else required to get the sgx working?
>
> These instructions seem quite a bit outdated:
> http://elinux.org/BeagleBoardDebian#SGX_Drivers

Thanks! THis is now fixed:

http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black


> IIRC there are some library blobs that cannot be redistributed?  Or do
> they just not comply with the DFSG?

So it's the "imgtec" demo's that cause the license issue. Till TI
physically separates the two into a lib & example download package i
can't do nothing about packing..

Regards,

-- 
Robert Nelson
http://www.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] debian testing: 2014-10-08 (Jessie Snapshot)

[Charles Steinkuehler]

On 10/9/2014 10:45 AM, Robert Nelson wrote:
> 
> Now for Jessie...

Hooray!!!

> With a big Warning, Jessie isn't frozeen yet...
> 
> https://release.debian.org/jessie/freeze_policy.html
> 
> So anything packaged could still be taken away.
> 
> Desktop: lxqt 0.7.96 + qt 5.3.2
> Kernel: 3.14.19-ti-r28 + sgx modules

Is anything else required to get the sgx working?

These instructions seem quite a bit outdated:
http://elinux.org/BeagleBoardDebian#SGX_Drivers

IIRC there are some library blobs that cannot be redistributed?  Or do
they just not comply with the DFSG?

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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: Booting adeneo wince 7 on beaglebone black

[CEinTX]

Hi,

Generally - this works the same as in the original BB days.
Format using HP USB format tool - found it works best on an XP machine.
Not sure what this does different from the Windows format - but it is and is
far more reliable.

Once formatted, copy the MLO 1st so it goes to the base location that your 
MLO needs to be able to find it.
Then load your eboot and nk.bin and any other files you may need.

As far as booting Corey's suggestion will work. If I'm going to be always 
booting from uSD
I will short the switch out with a jumper or solder ball/blob.

Hope that helps,
Matt


On Thursday, July 10, 2014 4:23:44 AM UTC-5, corey...@gmail.com wrote:
>
> Hello, 
> This happens on mine, I suggest holding the S2 button(User) and then 
> pressing the S1 button (reset). it should start the process if it doesn't 
> try the other power supply option.
> Tch
>
> *uss,Corey*
> On Tuesday, October 8, 2013 9:08:22 AM UTC+2, Ali Asadzadeh wrote:
>>
>> Dear all
>> I have loaded a 4GB SD card with the MLO and EBOOTSD.nb0 and NK.bin that 
>> comes with the AM335X_BeagleBoneBlack_WEC7_BIN_V0131 package from 
>> Adeno,Also I have formatted the card with Fat32 and 4096 byte sectors 
>> (using windows foarmt), and I have used the TI SD card utility for flashing 
>> the SD card, Also I have pushed the user button before power up,
>> But nothing happens!!! 
>> when I power the board up the leds won't flash, and there is no activity 
>> on the Serial header, So I think it's a boot problem, How can I be sure 
>> that the MLO is in the first sector of the SD card? I have loaded android, 
>> angstrom and ubuntu successfully on to beaglebone balck, I want to test 
>> what windows ce have to offer, So if somebody have booted successfully 
>> please help me too.
>>
>

-- 
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] Multi camera project BeagleBlack

[Jon E]

Hi,

Fwiw - I've tried a few times to capture PAL or NTSC composite video over 
USB (with an easycap style adapter, various kernel versions up to the 
latest 3.14-ti branch) and have never been successful. It always chokes on 
the data transfer, and I believe it just can't handle the data rate for the 
isochronous transfer.

I've vaguely wondered about putting a decoder IC on a cape, and using the 
PRU to process the digital (BT656?) output, but haven't got further than 
just thinking about it..

Regards,
Jon


On Thursday, 9 October 2014 22:21:45 UTC+1, Peter Fearing wrote:
>
> Yes, and that's pretty much what we're thinking right now. The biggest 
> challenges at this point are the possibility of having to interpret ADC 
> input as a video stream (for Linux) and the need to create composite (NTSC) 
> output from the Beaglebone.
>
>

-- 
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] Multi camera project BeagleBlack

[Peter Fearing]

Yes, and that's pretty much what we're thinking right now. The biggest
challenges at this point are the possibility of having to interpret ADC
input as a video stream (for Linux) and the need to create composite (NTSC)
output from the Beaglebone.

On Wednesday, October 8, 2014, Przemek Klosowski <
przemek.klosow...@gmail.com> wrote:

>
>
> On Wed, Oct 8, 2014 at 6:29 PM, Peter Fearing  > wrote:
>
>>
>> A possibility we considered briefly was using the USB port for one camera
>> and the microUSB for the other.  Does that seem feasible?
>>
>
> Have you considered placing a USB hub between BBB and your webcams? the
> typical USB webcam bandwidth requirements are not that great  unless you
> need high resolution in space and/or time.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/z8BFcZTBOmQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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] Re: EMAC RMII Setup

[CEinTX]

Hi All,

In addition to the above, found that I needed to set a bit or two (1 port 
or 2) in the MACCONTROL reg.
The routine I found changed to this (CE7 file cpsw3g.c)

BOOL Cpsw3g_get_phy_link_state(UINT32 port)
{
UINT16 phy_id;
int speed = 0, duplex = 0;
UINT16 reg;
UINT32 mac_control = 0;

BOOL link = FALSE;

PCpswCb pCpsw3gCb=&g_cpsw3gCb;

phy_id = pCpsw3gCb->phy_id;

if (MdioRd(phy_id, PHY_BMSR, 0, ®))
return link; /* could not read, assume no link */

if (reg & PHY_BMSR_LS) { /* link up */
speed = Phy_speed(phy_id);
duplex = Phy_duplex(phy_id);

link = TRUE;
mac_control = (1 << 5); /* MIIEN */
if (speed == 10)
mac_control |= (1 << 18);/* In Band mode */

// *  added these lines *
if (speed == 100)
mac_control |= (1 << 15);/* RMII Gasket 100Mb Mode */
// * add bit 16 for 2nd port if needed

if (speed == 1000)
mac_control |= ((1 << 7) | (1 << 17)); /* GIGABITEN | GIGABIT_FORCE */
if (duplex == FULL)
mac_control |= (1 << 0);/* FULLDUPLEXEN */
}

if (mac_control == pCpsw3gCb->mac_control)
return link;

if (mac_control) 
{
OALMSGS(OAL_ERROR, ( 
L"link up on port %d, speed %d, %s duplex\r\n", port, speed, 
((duplex == FULL) ?  L"full" : L"half") ));
OALMSGS(OAL_ERROR, ( L"Mac Ctrl: %x\r\n", mac_control));
} 
else 
{
OALMSGS(OAL_ERROR, ( L"link down on port %d\r\n", port));
}

Cpsw3g_Write_Register((UINT32 *)CPMAC_MAC_CTRL(port), mac_control);
pCpsw3gCb->mac_control = mac_control;

return link;
}

Hope this helps someone.
Still testing to see if that's all that's needed.
At least it's getting the DHCP and doing the BOOTME now.

Again, if anyone knows of anything else that I may have missed. I'd 
appreciate the feedback.

Thanks,
Matt


On Thursday, October 9, 2014 9:43:36 AM UTC-5, CEinTX wrote:
>
> Hi
>
> I've notice a couple of threads that talk about people using the RMII 
> interface
> and there being some issues. However, I haven't seen any resolutions 
> posted.
>
> I have gotten the interface to do the negotiation for link and speed.
> This all seems to happen over the MDIO interface.  
>
> When it gets to DHCP - it times out.
> I don't see any traffic over the RX or TX lanes of the RMII interface
> and I don't see any packet requests via Wireshark.
> However, there is a lot of traffic over the MDIO interface while waiting 
> for time out.
>
> I can only infer on this that I am missing something in the software side
> of the setup.
>
> I am working in CE7, but would welcome any feedback from the Linux or
> other OS folks as it will likely be applicable just not identical.
>
> I've gone through this as far as a hardware guy knows how. I could use
> some pointers from the software people out there.
>
> Things that I know needed to be done:
> Set GMII_SEL_REG to 0xF5 
> this sets the reference clocks to inputs from the phys
> also sets the ports to RMII mode vs MII or RGMII.
>
> Set pad configs to:
> PAD_ENTRY(MII1_RXERR,  MODE(1) | RXACTIVE)   
>  /* RMII1_RXERR  (J15)i - RMII1_RXERR  */ \
> PAD_ENTRY(MII1_TXEN, MODE(1))/* 
> RMII1_TXEN   (J16)o - RMII1_TX_EN  */ \
> PAD_ENTRY(MII1_CRS,  MODE(1) | RXACTIVE) 
>/* RMII1_CRS_DV (H17)i - RMII1_CRS_DV */ \
> PAD_ENTRY(MII1_TXD1, MODE(1))/* 
> RMII1_TXD1   (K16)o - RMII1_TXD1   */ \
> PAD_ENTRY(MII1_TXD0, MODE(1))/* 
> RMII1_TXD0   (K17)o - RMII1_TXD0   */ \
> PAD_ENTRY(RMII1_REFCLK,  MODE(0) | RXACTIVE)/* RMII1_RXCLK  (H18)i - 
> RMII1_REFCLK */ \
> PAD_ENTRY(MII1_RXD1, MODE(1) | RXACTIVE) 
>/* RMII1_RXD1   (L15)i - RMII1_RXD1   */ \
> PAD_ENTRY(MII1_RXD0, MODE(1) | RXACTIVE) 
>/* RMII1_RXD0   (M16)i - RMII1_RXD0   */ \
> PAD_ENTRY(GPMC_WPN,  MODE(3) | RXACTIVE)/* RMII2_RXERR  (U17)i - 
> RMII2_RXERR  */ \
> PAD_ENTRY(GPMC_A0,MODE(3))/* RMII2_TXEN   (R13)o - RMII2_TXEN 
>   */ \
> PAD_ENTRY(GPMC_WAIT0, MODE(3) | RXACTIVE)/* RMII2_CRS_DV (T17)i - 
> RMII2_CRS_DV */ \
> PAD_ENTRY(GPMC_A4, MODE(3))/* RMII2_TXD1   (R14)o - 
> RMII2_TXD1   */ \
> PAD_ENTRY(GPMC_A5, MODE(3))/* RMII2_TXD0   (V15)o - 
> RMII2_TXD0   */ \
> PAD_ENTRY(MII1_COL, MODE(1) | RXACTIVE)/* RMII2_RXCLK  (H16)i - 
> RMII2_REFCLK */ \
> PAD_ENTRY(GPMC_A10, MODE(3) | RXACTIVE)/* RMII2_RXD1   (T16)i - 
> RMII2_RXD1   */ \
> PAD_ENTRY(GPMC_A11, MODE(3) | RXACTIVE)/* RMII2_RXD0   (V17)i - 
> RMII2_RXD0   */ \
> PAD_ENTRY(MDIO_DATA,MODE(0) | RXACTIVE | PULLUP_EN)/* 
> MDIO_DATA */   \
> PAD_ENTRY(MDIO_CLK,  MODE(0) | PULLUP_EN)/* 
> MDIO_CLK */\
>
> If anyone see something I did wrong or knows of additional things I need 
> to do, I'd appreciate the insight.
>
> Thanks,
> Matt
>

-- 
For more options, visit http://beagleboard.

[beagleboard] How to Enable Beaglebone Black Power On Self-Test (POST)?

[Lei Wang]

Hi,

I need to perform memory test at BBB boot. I'd like to perform memory POST 
test as documented in "doc/README.memory-test". However I have difficulty 
to enable the tests.

u-boot version: u-boot-2013.10

I added below (3) lines to the file "am335x_evm.h" to enable memory POST.

#define CONFIG_POST
#define CONFIG_SYS_POST_MEMORY
#define CONFIG_SYS_POST_MEM_REGIONS 

I've got errors when I build:
 "... include/post.h:60:2: error: #error "_POST_WORD_ADDR currently not 
implemented for this platform!" ".

It seems that "post,h" file suggests that am335x platform is not supported 
by POST.  

I wonder if someone could give me some guidance on this topic.


Thanks a lot!

Lei Wang
 
PS I also tried with the latest u-boot release (v2014.10-rc3). I got the 
same error.



-- 
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 to cross compile the kernel without script

[Robert Nelson]

On Thu, Oct 9, 2014 at 1:52 PM,   wrote:
>
> Hi,
>
> I compile and install the new kernel(3.16.2) image for my PC. And, I have
> installed the ARM Cross Compiler for  BeagleBone Black (Rev C). Now how can
> i cross compile the kernel for BeagleBone Black

make ARCH=arm CROSS_COMPILE= zImage modules dtbs

Regards,

-- 
Robert Nelson
http://www.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] how to cross compile the kernel without script

[vairamhcet]

Hi,

I compile and install the new kernel(3.16.2) image for my PC. And, I have 
installed the ARM Cross Compiler for  BeagleBone Black (Rev C). Now how can 
i cross compile the kernel for BeagleBone Black

Thanks in Advance,
Vairamani V

-- 
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] A couple of questions about the BBB EEPROM

[Ulisse Ruiz]

i testing this 
thanks very very very much.

Il giorno 09/ott/2014, alle ore 19:26, Robert Nelson  
ha scritto:

> On Thu, Oct 9, 2014 at 11:47 AM, Ulisse Ruiz  wrote:
>> I mounted this in led illumination project but i make a error with program
>> eeprom and this result blank.
>> the problem is the boot not load null  because read eeprom and not view
>> the original value.
>> 
>> Can you help me with file boot...
>> i buy less 40 board but this is urgently and important for my work.
>> 
> 
> If they are 100% clones, aka ddr3 + 1Ghz cpu:
> 
> GND TP4 and flash via this image:
> 
> https://rcn-ee.net/deb/testing/2014-10-08/lxde-4gb/BBB-blank-eMMC-flasher-debian-7.6-lxde-4gb-armhf-2014-10-08-4gb.img.xz
> 
> Regards,
> 
> 
> -- 
> Robert Nelson
> http://www.rcn-ee.com/
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Access GPIO/SPI etc. on Expansion Header

[Andrew Henderson]

To be fair, using spidev to set up SPI and then bitbanging it from 
userspace is, at best, a very unorthodox approach.  It just happened to be 
suited to the particular problem that I trying to solve.  I can completely 
understand how such an approach would be viewed with some distaste by 
experienced kernel developers as it is far from the a standard approach to 
the problem.  And they really aren't wrong.  It isn't the correct way to 
develop a generalized solution.  I was just curious as to whether anyone 
else had attempted it and what their results were like.  

The particular project that required my SPI tinkering finished quite a 
while ago and it worked like a charm, so I'll just chalk it up as a 
learning experience and leave it at that.  The BBB, kernel code, etc. are 
all there for you to play around with.  Try crazy stuff out and have fun 
with it.  Some will work out OK and some won't, but you won't know until 
you give it a shot.

On Thursday, October 9, 2014 2:54:05 PM UTC-4, William Hermans wrote:
>
> *Well, I have gotten it working before using mmap() calls because I had a 
>> very specific need for it for a proprietary project that I can't share the 
>> code for, but I was informed (in no uncertain terms) that using mmap() for 
>> SPI comms in user space is a bad idea and that I am not a smart person:*
>>
>
> Isnt it funny how when you *may* ask these people who responded to you 
> post they would not offer any assistance. But as soon as you put up working 
> code for something that works for you, Suddenly everyone is offering their 
> "help"
>
> Personally, I can see several flaws with using mmap in any situation. But 
> if it works for you, and works well. I say to hell with what anyone else 
> says. So long as it's abstracted, and no one else has to maintain it.
>
> I keep seeing the same text from the same person "how very unlinix like of 
> you" or some such garbage. Sorry, I can not disagree more. First of all, 
> mmap was created for a reason. This reason has nothing to do with critiques 
> on user implementation while using it. Secondly, Linux is about freedom, 
> not one individuals "dictatorship" or misconception of what Linux should be.
>
> Also, I've seen some implementations many of the commentators of the post 
> you linked to and . . . yeah let us just say that some of the stuff I have 
> seen is far from perfect. So many of them do not have a leg to stand on 
> when it comes to criticizing someone else's implementation.
>
> Andrew, anyway you're probably smart enough to not need my encouragement, 
> but I'd encourage you to keep using mmap, while thinking of alternate 
> methods of achieving the same end goal. While again thinking which method 
> might be better and why. Software development is great for constantly 
> keeping our minds busy while learning new techniques, and technologies. 
> There is always something new to learn, and no one amongst us started off 
> by knowing *everything*.
>

-- 
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: Access GPIO/SPI etc. on Expansion Header

[William Hermans]

>
> *Well, I have gotten it working before using mmap() calls because I had a
> very specific need for it for a proprietary project that I can't share the
> code for, but I was informed (in no uncertain terms) that using mmap() for
> SPI comms in user space is a bad idea and that I am not a smart person:*
>

Isnt it funny how when you *may* ask these people who responded to you post
they would not offer any assistance. But as soon as you put up working code
for something that works for you, Suddenly everyone is offering their "help"

Personally, I can see several flaws with using mmap in any situation. But
if it works for you, and works well. I say to hell with what anyone else
says. So long as it's abstracted, and no one else has to maintain it.

I keep seeing the same text from the same person "how very unlinix like of
you" or some such garbage. Sorry, I can not disagree more. First of all,
mmap was created for a reason. This reason has nothing to do with critiques
on user implementation while using it. Secondly, Linux is about freedom,
not one individuals "dictatorship" or misconception of what Linux should be.

Also, I've seen some implementations many of the commentators of the post
you linked to and . . . yeah let us just say that some of the stuff I have
seen is far from perfect. So many of them do not have a leg to stand on
when it comes to criticizing someone else's implementation.

Andrew, anyway you're probably smart enough to not need my encouragement,
but I'd encourage you to keep using mmap, while thinking of alternate
methods of achieving the same end goal. While again thinking which method
might be better and why. Software development is great for constantly
keeping our minds busy while learning new techniques, and technologies.
There is always something new to learn, and no one amongst us started off
by knowing *everything*.



On Wed, Oct 8, 2014 at 12:50 PM, Andrew Henderson 
wrote:

> Well, I have gotten it working before using mmap() calls because I had a
> very specific need for it for a proprietary project that I can't share the
> code for, but I was informed (in no uncertain terms) that using mmap() for
> SPI comms in user space is a bad idea and that I am not a smart person:
>
> https://plus.google.com/109402916922772242647/posts/YUpRgyD1HME
>
> Offhand, I'm guessing that you're loading a device tree overlay for SPI
> that specifies the driver "spidev" to be in control of the SPI channels.
> You're probably hitting the registers correctly in user space, but the
> spidev driver is having the power management in the kernel shut down SPI
> because the spidev driver hasn't sent a message within the last 2 seconds.
> In the kernel source, the drivers/spi/spi-omap2-mcspi.c file has the
> function omap2_mcspi_probe().  This function sets up some power management
> at the end:
>
> pm_runtime_use_autosuspend(&pdev->dev);
> pm_runtime_set_autosuspend_delay(&pdev->dev, SPI_AUTOSUSPEND_TIMEOUT);
> pm_runtime_enable(&pdev->dev);
>
> As for an example of doing the transfer, you'll want to mimic the code in
> the omap2_mcspi_txrx_pio() function in that same file.  Ignore the
> OMAP2_MCSPI_CHCONF_TURBO paths, as you won't be hitting any of those.
> You'll also need to completely avoid mentioning the spidev in the overlay
> (only mux the pins) and set all the registers up yourself.  Or, you can
> shut off the power management in the SPI driver (comment out the
> pm_runtime_enable() call), set up SPI via ioctls() to /dev/spidev from
> userspace, and then bitbang the registers via mmap().  Either way,
> mmap()-ing SPI is possible, but you REALLY need to make sure that there
> isn't another way to do what you need to do.
>
> In short, you should not be doing it this way.  But, if you really want to
> experiment and learn about the spidev driver in the process, go for it.
>
> Andrew
>
>
> On Wednesday, October 8, 2014 3:14:28 PM UTC-4, Patrick Sheridan wrote:
>>
>> Hi Andrew,
>>
>> I know this is an old forum, but I've been stuck trying approach 2, using
>> an mmap to /dev/mem to control the SPI device.  Do you know of any working
>> examples?
>>
>> Specifically, I'm trying to write to SPI0[MCSPI_TX0] with SPI0.D0
>> configured for output without using a FIFO, but I typically get nothing--no
>> error, but no SPI CLK action either.  The CH0STAT register is showing TX to
>> be full, but I don't know why the system does not initiate the transfer.
>>
>> Any example configuration code you have would be greatly appreciated.
>>
>> Thanks,
>> Patrick
>>
>> On Tuesday, October 15, 2013 9:58:54 PM UTC-4, Andrew Henderson wrote:
>>>
>>> For SPI, mux the pins in the device tree to enable the SPI0 and or SPI1
>>> interfaces, then reference the Linux kernel documentation:
>>>
>>> https://www.kernel.org/doc/Documentation/spi
>>> https://github.com/piranha32/IOoo/blob/master/src/SPI.cpp
>>>
>>> I suspect that the "spidev_test.c" file in the kernel or the SPI.cpp is
>>> what you are interested in, though the "spidev" f

[beagleboard] Beaglebone Black 4DCape-43T ncurses terminal emulation

[Peter Gregory]

I'm running Debian 7.6 Console - no desktop loaded, just console 
applications

Linux beaglebone 3.14.19-ti-r28 #1 SMP PREEMPT Wed Oct 8 00:34:37 UTC 2014 
armv7l GNU/Linux

Running character applications like alsaplayer do not display the same on 
the LCD console as when I'm running a ssh session.

In the ssh session, it will display a single line that updates as the file 
plays.

On the LCD cape, the character positioning codes fail and it displays line 
after line as it plays.

Is there a configuration I need to set in the environment to tell Linux the 
terminal emulation to use with the LCD cape for the text positioning to 
work?



-- 
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] unloading and reloading DTO doesn't work for GPIO reconfiguration

[Charles Steinkuehler]

On 10/9/2014 1:32 PM, Britton Kerin wrote:
> Following Derek Molloy's page on DTO GPIO configuration:
> 
>   
> http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/#comment-29416
> 
> Unloading and reloading an overlay doesn’t work. If I make an overlay
> for a single pin, with a setting of 0×27 (input with pull-down enable), it
> works right after boot. Same for pull-up (0×37). But if I try to unload the
> overlay (echo ‘-overlay_number’ >$SLOTS) and load one with the opposite
> pull setting it doesn’t seem to take: I still get high if it was initially
> configured with pull-up, or low if initially configured with pull-down.
> 
> Is there anything in the overlay example itself that might be causing this,
> or is it just a bug somewhere?

Unloading *ANY* overlay is essentially broken.  Results will vary from
not doing anything to crashing the kernel.

If you want to unload a previously loaded device-tree overlay, you need
to reboot.

This will hopefully be fixed in the future as device-tree change-sets
have been incorporated into the mainline kernel code.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] unloading and reloading DTO doesn't work for GPIO reconfiguration

[Britton Kerin]

Following Derek Molloy's page on DTO GPIO configuration:

  
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/#comment-29416

Unloading and reloading an overlay doesn’t work. If I make an overlay
for a single pin, with a setting of 0×27 (input with pull-down enable), it
works right after boot. Same for pull-up (0×37). But if I try to unload the
overlay (echo ‘-overlay_number’ >$SLOTS) and load one with the opposite
pull setting it doesn’t seem to take: I still get high if it was initially
configured with pull-up, or low if initially configured with pull-down.

Is there anything in the overlay example itself that might be causing this,
or is it just a bug somewhere?

-- 
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] Reading all zero's from SPI using BBB Linux 3.14

[Guy Grotke]

You do need to leave the SCLK with RX_ENABLE turned on, or the receive 
section of the SPI will have no SPI clock.  RX_ENABLE does not make the 
pin an input or output:  It just enables reading the value out on the IO 
pin.  The use of the pin specified in the 3 MODE bits really defines if 
it will be used as input, output, or both.


I have not tried running 3.14, but I suggest you use /dev/mem and mmap() 
so you can look at the SPI control registers under the earlier OS and 
under 3.14 to see the differences.  The register definitions are not 
very complicated.  Probably the difference is just the definition of 
which of the data pins is output and which is input.


Has anyone been able to successfully use SPI devices on the 3.14 
kernel?  Neither SPI0 nor SPI1 seem to be able to read anything but zeros.


Thanks,

Dallas
--
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: Recomended USB Hub

[neo star]

Is there any particular brand you recomend

On Thu, Oct 9, 2014 at 11:02 PM, Peter Gregory  wrote:
> If you are planning on plugging in multiple devices I'd suggest getting a
> powered hub.
> I've had good luck with a plugable USB 2.0 4 port hub.  $17 on amazon with
> free shipping.
> It comes with a 2.5 amp power supply that can run the Beaglebone Black and
> the hub (splice in power lines & plug)
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/kdvK71ePQuw/unsubscribe.
> To unsubscribe from this group and all its topics, 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] Re: Recomended USB Hub

[Peter Gregory]

If you are planning on plugging in multiple devices I'd suggest getting a 
powered hub.
I've had good luck with a plugable USB 2.0 4 port hub.  $17 on amazon with 
free shipping.
It comes with a 2.5 amp power supply that can run the Beaglebone Black and 
the hub (splice in power lines & plug)

-- 
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] A couple of questions about the BBB EEPROM

[Gerald Coley]

Interesting.

Use Roberts instructions and do like he says..

Gerald


On Thu, Oct 9, 2014 at 12:23 PM, Ulisse Ruiz  wrote:

> fifty fifty
> are bbb rev c
> and personal maker.
>
> i need file for boot.
> thanks
> Il giorno 09/ott/2014, alle ore 19:21, Gerald Coley <
> ger...@beagleboard.org> ha scritto:
>
> Can I assume these are Embest boards?
>
> Gerald
>
>
> On Thu, Oct 9, 2014 at 11:47 AM, Ulisse Ruiz 
> wrote:
>
>> I mounted this in led illumination project but i make a error with
>> program eeprom and this result blank.
>> the problem is the boot not load null  because read eeprom and not
>> view the original value.
>>
>> Can you help me with file boot...
>> i buy less 40 board but this is urgently and important for my work.
>>
>> Help me please.
>>
>>
>> Il giorno 09/ott/2014, alle ore 18:21, Gerald Coley <
>> ger...@beagleboard.org> ha scritto:
>>
>> And where did you get these boards without the EEPROM programmed?
>>
>> Gerald
>>
>>
>> On Wed, Oct 8, 2014 at 7:43 PM,  wrote:
>>
>>> i have 5 bbb with new eeprom... can you help me with script???
>>> thanks...
>>>
>>> Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:

 1) We use a terminal program that runs a script that does i2C write
 commands in UBoot.
 2) Use a terminal program that runs a script that does i2C reads
 and displays them to the screen using commands in UBoot. The copy them to a
 text file for use later in the scripts created for #1.

 Gerald


 On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven 
 wrote:

> Just out of curiosity, wondering:
>
> 1) How are the EEPROMs for the BBB programmed in production? How are
> per-device things like serial numbers allocated? Curious also how that's
> matched up to the sticker with the serial number?
>
> 2) If I wanted to mess around with the EEPROM, what's the best way to
> keep a backup (particularly with respect to things like the serial 
> number)?
>
>
>
> --
> 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/groups/opt_out.
>


>>> --
>>> 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 tobeagleboard+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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
>> To unsubscribe from this group and all its topics, 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Re: [beagleboard] A couple of questions about the BBB EEPROM

[Ulisse Ruiz]

fifty fifty
are bbb rev c 
and personal maker.

i need file for boot.
thanks
Il giorno 09/ott/2014, alle ore 19:21, Gerald Coley  ha 
scritto:

> Can I assume these are Embest boards?
> 
> Gerald
> 
> 
> On Thu, Oct 9, 2014 at 11:47 AM, Ulisse Ruiz  wrote:
> I mounted this in led illumination project but i make a error with program 
> eeprom and this result blank.
> the problem is the boot not load null  because read eeprom and not view 
> the original value.
> 
> Can you help me with file boot...
> i buy less 40 board but this is urgently and important for my work.
> 
> Help me please.
> 
> 
> Il giorno 09/ott/2014, alle ore 18:21, Gerald Coley  
> ha scritto:
> 
>> And where did you get these boards without the EEPROM programmed?
>> 
>> Gerald
>> 
>> 
>> On Wed, Oct 8, 2014 at 7:43 PM,  wrote:
>> i have 5 bbb with new eeprom... can you help me with script???
>> thanks...
>> 
>> Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:
>> 1) We use a terminal program that runs a script that does i2C write commands 
>> in UBoot.
>> 2) Use a terminal program that runs a script that does i2C reads and 
>> displays them to the screen using commands in UBoot. The copy them to a text 
>> file for use later in the scripts created for #1.
>> 
>> Gerald
>> 
>> 
>> On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven  wrote:
>> Just out of curiosity, wondering:
>> 
>> 1) How are the EEPROMs for the BBB programmed in production? How are 
>> per-device things like serial numbers allocated? Curious also how that's 
>> matched up to the sticker with the serial number?
>> 
>> 2) If I wanted to mess around with the EEPROM, what's the best way to keep a 
>> backup (particularly with respect to things like the serial number)?
>> 
>> 
>> 
>> -- 
>> 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/groups/opt_out.
>> 
>> 
>> -- 
>> 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 tobeagleboard+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 a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
>> To unsubscribe from this group and all its topics, 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 a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
> To unsubscribe from this group and all its topics, 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] Re: bug in LCD4 patch

[mettingc]

Hi, After a week of struggling with this problem, it seems like I am having 
the exact same problem as you. My out-of-the-box BBB came with:
Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l 
GNU/Linux

and is a Debian Image from 2014-04-23.
After decompiling the LCD4 driver I saw that the Pin is still blocked. Is 
there any updates as to whether the new Debian image:
Debian (BeagleBone, BeagleBone Black - 2GB SD) 2014-05-14 

has resolved this or any more direct solutions to the issue. I'm new at 
this stuff so I apologize in advance if this isn't the place for this 
question.
Chris
On Monday, August 26, 2013 11:31:39 AM UTC-4, Tim T wrote:
>
>  Hi,
>
> The LCD4 cape basic support patch uses P9_21 in 
> bone_lcd4_cape_keys_00A2_pins pin group. However, according to the 
> schematic file at Beagleboardtoys wiki, it doesn't use P9_21. This error 
> prevents any other virtual capes such as UART2 or SPI0 to be loaded because 
> of pin conflict on P9_21.
>
> Patch location: 
> *meta-beagleboard / common-bsp / recipes-kernel / linux / 
> linux-mainline-3.8 / not-capebus / 
> 0168-capes-add-basic-support-for-LCD4-capes.patch *
>
> Schematic file of LCD4:
> *https://github.com/CircuitCo/BeagleBone-LCD4-RevA1/blob/master/BeagleBone-LCD4-RevA1-schematic.pdf?raw=true
>  
> 
>  
> *
>
> Thanks, 
> Tim 
>

-- 
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] A couple of questions about the BBB EEPROM

[Robert Nelson]

On Thu, Oct 9, 2014 at 11:47 AM, Ulisse Ruiz  wrote:
> I mounted this in led illumination project but i make a error with program
> eeprom and this result blank.
> the problem is the boot not load null  because read eeprom and not view
> the original value.
>
> Can you help me with file boot...
> i buy less 40 board but this is urgently and important for my work.
>

If they are 100% clones, aka ddr3 + 1Ghz cpu:

GND TP4 and flash via this image:

https://rcn-ee.net/deb/testing/2014-10-08/lxde-4gb/BBB-blank-eMMC-flasher-debian-7.6-lxde-4gb-armhf-2014-10-08-4gb.img.xz

Regards,


-- 
Robert Nelson
http://www.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] A couple of questions about the BBB EEPROM

[Gerald Coley]

Can I assume these are Embest boards?

Gerald


On Thu, Oct 9, 2014 at 11:47 AM, Ulisse Ruiz  wrote:

> I mounted this in led illumination project but i make a error with program
> eeprom and this result blank.
> the problem is the boot not load null  because read eeprom and not
> view the original value.
>
> Can you help me with file boot...
> i buy less 40 board but this is urgently and important for my work.
>
> Help me please.
>
>
> Il giorno 09/ott/2014, alle ore 18:21, Gerald Coley <
> ger...@beagleboard.org> ha scritto:
>
> And where did you get these boards without the EEPROM programmed?
>
> Gerald
>
>
> On Wed, Oct 8, 2014 at 7:43 PM,  wrote:
>
>> i have 5 bbb with new eeprom... can you help me with script???
>> thanks...
>>
>> Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:
>>>
>>> 1) We use a terminal program that runs a script that does i2C write
>>> commands in UBoot.
>>> 2) Use a terminal program that runs a script that does i2C reads
>>> and displays them to the screen using commands in UBoot. The copy them to a
>>> text file for use later in the scripts created for #1.
>>>
>>> Gerald
>>>
>>>
>>> On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven 
>>> wrote:
>>>
 Just out of curiosity, wondering:

 1) How are the EEPROMs for the BBB programmed in production? How are
 per-device things like serial numbers allocated? Curious also how that's
 matched up to the sticker with the serial number?

 2) If I wanted to mess around with the EEPROM, what's the best way to
 keep a backup (particularly with respect to things like the serial number)?



 --
 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/groups/opt_out.

>>>
>>>
>> --
>> 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 tobeagleboard+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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Re: [beagleboard] A couple of questions about the BBB EEPROM

[Ulisse Ruiz]

I mounted this in led illumination project but i make a error with program 
eeprom and this result blank.
the problem is the boot not load null  because read eeprom and not view the 
original value.

Can you help me with file boot...
i buy less 40 board but this is urgently and important for my work.

Help me please.


Il giorno 09/ott/2014, alle ore 18:21, Gerald Coley  ha 
scritto:

> And where did you get these boards without the EEPROM programmed?
> 
> Gerald
> 
> 
> On Wed, Oct 8, 2014 at 7:43 PM,  wrote:
> i have 5 bbb with new eeprom... can you help me with script???
> thanks...
> 
> Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:
> 1) We use a terminal program that runs a script that does i2C write commands 
> in UBoot.
> 2) Use a terminal program that runs a script that does i2C reads and displays 
> them to the screen using commands in UBoot. The copy them to a text file for 
> use later in the scripts created for #1.
> 
> Gerald
> 
> 
> On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven  wrote:
> Just out of curiosity, wondering:
> 
> 1) How are the EEPROMs for the BBB programmed in production? How are 
> per-device things like serial numbers allocated? Curious also how that's 
> matched up to the sticker with the serial number?
> 
> 2) If I wanted to mess around with the EEPROM, what's the best way to keep a 
> backup (particularly with respect to things like the serial number)?
> 
> 
> 
> -- 
> 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/groups/opt_out.
> 
> 
> -- 
> 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 tobeagleboard+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 a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/beagleboard/G6KU1KQ3n5M/unsubscribe.
> To unsubscribe from this group and all its topics, 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: boot error eeprom

[Gerald Coley]

Where did you get these boards?

Gerald


On Thu, Oct 9, 2014 at 8:26 AM, Jason Kridner  wrote:

> Take a look at the official build script at
> https://github.com/RobertCNelson/omap-image-builder/blob/master/beagleboard.org_image.sh
>  (https://github.com/beagleboard/image-builder). Note the
> bbb-blank-eeprom dtb option. Robert should be able to say where the source
> is at, but the binaries are pointed to by
> https://rcn-ee.net/deb/tools/latest/bootloader-ng as specific for
> BeagleBone Black (eeprom).
>
>
> On Thursday, October 9, 2014, Ulisse Ruiz  wrote:
>
>> *Hi,*
>> *Im Ulisse Ruiz.*
>> *I have a urgent question.*
>> *I have 20 board black with eeprom blank.*
>> *in test a error cause ereased eeprom and the boot not installing because
>> eeprom is 0x*
>> *Can you help me.*
>> *is urgent thanks very much*
>>
>> *i search in multi post but without success*
>> *Can you send me a boot with this patch?*
>> *is very important...*
>> *Thanks very much*
>>
>>
>>
>> *Ulisse Ruiz.*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>  --
> 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] A couple of questions about the BBB EEPROM

[Gerald Coley]

And where did you get these boards without the EEPROM programmed?

Gerald


On Wed, Oct 8, 2014 at 7:43 PM,  wrote:

> i have 5 bbb with new eeprom... can you help me with script???
> thanks...
>
> Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:
>>
>> 1) We use a terminal program that runs a script that does i2C write
>> commands in UBoot.
>> 2) Use a terminal program that runs a script that does i2C reads
>> and displays them to the screen using commands in UBoot. The copy them to a
>> text file for use later in the scripts created for #1.
>>
>> Gerald
>>
>>
>> On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven 
>> wrote:
>>
>>> Just out of curiosity, wondering:
>>>
>>> 1) How are the EEPROMs for the BBB programmed in production? How are
>>> per-device things like serial numbers allocated? Curious also how that's
>>> matched up to the sticker with the serial number?
>>>
>>> 2) If I wanted to mess around with the EEPROM, what's the best way to
>>> keep a backup (particularly with respect to things like the serial number)?
>>>
>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>
>>  --
> 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] Change the pinmux from MMC1 to MMC2

[Kaka]

Hi community member,

Would you please provide your advice for my request?

[Request]

 Now, we would like to change the MMC connection from 1 to 2.

 At this time, where should we change the software on linux?

 In my understanding, we should change the following settings at least.

 - mux.c file

 - DTS file

Any other?

[Background]

We could not access the WI-FI module via MMC2 even though change the pinmux 
at DTS file.

  Note: When used the MMC1, the application can access that module.

Best regards.

Kaka

-- 
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] USB Host mass storage device possible?

[kerrpumpstv]

Once mass storage device is created can you continue to send files to the pc 
from BBB even usb is has already been plugged in?

-- 
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] Change the pinmux from MMC1 to MMC2

[Kaka]

Hi community member,

Would you please provide your advice for my request?

[Request]

Now, we would like to change the MMC connection from 1 to 2.  At this time, 
where should we change the software on linux?

 In my understanding, we should change the following settings at least.

  --- DTS file

Any other files?

[Background]

We could not access the WI-FI module via MMC2 even though change the pinmux 
at DTS file.

  Note: When we used the MMC1, the application can access that module.

Also, they used the Beagleboneblack and angstrom linux.(Version 3.8)

Best regards,

Kaka

-- 
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] boot error eeprom

[Ulisse Ruiz]

Hi,
Im Ulisse Ruiz.
I have a urgent question.
I have 20 board black with eeprom blank.
in test a error cause ereased eeprom and the boot not installing because eeprom 
is 0x
Can you help me.
is urgent thanks very much

i search in multi post but without success
Can you send me a boot with this patch?
is very important...
Thanks very much



Ulisse Ruiz.














-- 
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] Beaglebone Black: Bonescript not compiled nor running under Cloud9

[reinharddaemon]

Hello,

the demo-program "Blink an on-board LED" only works under the following 
surface:



 *but not, when I run it under Cloud9:*

* 
*

I can even make syntax errors. There is no complain for the non-working 
code and (still) the LED is not blinking:



Am I missing a setting that I would have to make?

Should I update debian?

Beaglebone black: Element14, rev. C

Windows: XP

 Best regards,

-- 
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] A couple of questions about the BBB EEPROM

[ulissedj]

i have 5 bbb with new eeprom... can you help me with script???
thanks...

Il giorno sabato 17 agosto 2013 15:34:40 UTC+2, Gerald ha scritto:
>
> 1) We use a terminal program that runs a script that does i2C write 
> commands in UBoot.
> 2) Use a terminal program that runs a script that does i2C reads 
> and displays them to the screen using commands in UBoot. The copy them to a 
> text file for use later in the scripts created for #1.
>
> Gerald
>
>
> On Sat, Aug 17, 2013 at 4:31 AM, Marcos Scriven  > wrote:
>
>> Just out of curiosity, wondering:
>>
>> 1) How are the EEPROMs for the BBB programmed in production? How are 
>> per-device things like serial numbers allocated? Curious also how that's 
>> matched up to the sticker with the serial number?
>>
>> 2) If I wanted to mess around with the EEPROM, what's the best way to 
>> keep a backup (particularly with respect to things like the serial number)?
>>
>>
>>  -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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] Should I go on with angstrom: A specific use case

[shyni]

Hi,
   Were you able to find a solution for this? 
   I am facing exactly the same problem now - installing scipy from pip 
fails because of missing BLAS libraries. I tried to compile the atlas 
libraries, only to find that gfortran is not available.
  I am using the armhf port of Debian on Beaglebone black.
Warm Regards,
Shyni


On Friday, November 15, 2013 12:13:39 AM UTC+11, Ozan Çağlayan wrote:
>
> Hi again, 
>
> Well I can't install scipy from pip as the build fails because of 
> missing BLAS and ATLAS libraries. 
>
> Well regarding Python, it is actually not at all :) If you use it for 
> scientific computing using numpy/scipy, it is actually quite 
> sufficient :) 
>

-- 
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] Details of connecting beagleboard-xm to linux-mint pc

[amit251291]

Hi all,

I have beagleboard-xm. I have ported Android - ICS on it. I want to get ip 
address of the board. As said on site, i connected the board using mini usb 
cable and clicked on http://192.168.7.2 but it did not open the page. Also 
if i type* ifconfig* on terminal of my pc it does not show *USB0* or 
something like that.. It only shows '*eth0* and '*lo*'. Where is the 
problem ??

As i have already said i have build Android ICS on the board, at that time 
i have used serial to usb cable to the board. Board is working well with 
Android ICS. I used minicom fot that.

But how to get the IP address is the problem for me.. 

-- 
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] Regarding HDMI cable

[Gerald Coley]

http://www.elinux.org/Beagleboard:BeagleBone_Black_Accessories

Gerald

On Thu, Oct 9, 2014 at 5:42 AM, DEEPAK KESWANI 
wrote:

> Hello everyone,
>
> I am currently working on Beaglebone Black processor.So for my project i
> need to see my output screen via Micro HDMI port.I have monitor with VGA
> port.So can you please suggest me cable converter for converting VGA to
> micro HDMI for beaglebone black?
>
> --
> 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: Beaglebone Black Rebooting Several Times Every Day

[Sebastian H]

I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with 
netconsole support)  and after a little over 24 hours uptime, my BBB 
rebooted without any entries in the netconsole log or any logs on the BBB 
that I could find. 

Did anyone have any luck in troubleshooting this issue any further? 

In the meantime, I guess I'll try your suggestion of disabling the watchdog 
for now.


On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans wrote:
>
> Short term, you can disable the hardware watchdog in kernel config. That 
> should temporarily fix your problem, and if it does not . . . bigger 
> mystery.
>
> Long term, it would be good to figure out what is triggering the watchdog. 
> strace on the watchdog PID will not work - I tested this myself.
>
> The only one thing I can think of off hand is perhaps modifying the 
> watchdog module to output a debug message before rebooting the system. As 
> to which process triggered a shutdown, and why. If possible . . .
>
> Will research more tomorrow it is very late ( actually early ) here.
>
> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson  > wrote:
>
>>
>>> Forget about claiming its a hardware issue. Because it is not. We've had 
>>> two beaglebone blacks for close to a year, and a half now. Both are rock 
>>> solid, running off barrel jack power, or USB( one of each ).
>>>
>>> Ok well just stating facts that bbw is not rebooting and BBB is with the 
>> same kernel
>>
>> Ok i would be happy to stop guessing and actually find the problem. Could 
>> you give me some real advise on HOW to use the serial module appropriately. 
>> i do have it connected to the serial console and i have event built a 
>> kernel with verbosed debugging on i am just not seeing anything. 
>>
>> So if you would like any information or dumps or whatever i am happy to 
>> provide that.
>>
>>
>>  -- 
>> 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] debian testing: 2014-10-08 (Jessie Snapshot)

[Robert Nelson]

Howdy!

I just pushed out another round of images for testing.

For wheezy, mostly fixes, most of which have just been pushed to the repo, so:

sudo apt-get update; sudo apt-get upgrade

bone101 works again ( http://beaglebone.local/Support/bone101/ )
Still one blocker with jekyll, so it's not the head version of the
bone101 repo yet

Now for Jessie...

With a big Warning, Jessie isn't frozeen yet...

https://release.debian.org/jessie/freeze_policy.html

So anything packaged could still be taken away.

Desktop: lxqt 0.7.96 + qt 5.3.2
Kernel: 3.14.19-ti-r28 + sgx modules
Init: systemd
Network: connman + cmst
Bugs: cloud9 doesn't like jessie's tmux, so the html terminal console
isn't working.
(yes flasher only, I was running late...)

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-08

3.8 -> 3.14 transition:
http://elinux.org/Beagleboard:Capes_3.8_to_3.14

Note, rsync is still running, so not all images have been pushed out
yet as of (10:44am central time)

Regards,

-- 
Robert Nelson
http://www.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] EMAC RMII Setup

[CEinTX]

Hi

I've notice a couple of threads that talk about people using the RMII 
interface
and there being some issues. However, I haven't seen any resolutions posted.

I have gotten the interface to do the negotiation for link and speed.
This all seems to happen over the MDIO interface.  

When it gets to DHCP - it times out.
I don't see any traffic over the RX or TX lanes of the RMII interface
and I don't see any packet requests via Wireshark.
However, there is a lot of traffic over the MDIO interface while waiting 
for time out.

I can only infer on this that I am missing something in the software side
of the setup.

I am working in CE7, but would welcome any feedback from the Linux or
other OS folks as it will likely be applicable just not identical.

I've gone through this as far as a hardware guy knows how. I could use
some pointers from the software people out there.

Things that I know needed to be done:
Set GMII_SEL_REG to 0xF5 
this sets the reference clocks to inputs from the phys
also sets the ports to RMII mode vs MII or RGMII.

Set pad configs to:
PAD_ENTRY(MII1_RXERR,  MODE(1) | RXACTIVE)   
 /* RMII1_RXERR  (J15)i - RMII1_RXERR  */ \
PAD_ENTRY(MII1_TXEN, MODE(1))/* 
RMII1_TXEN   (J16)o - RMII1_TX_EN  */ \
PAD_ENTRY(MII1_CRS,  MODE(1) | RXACTIVE)   
 /* RMII1_CRS_DV (H17)i - RMII1_CRS_DV */ \
PAD_ENTRY(MII1_TXD1, MODE(1))/* 
RMII1_TXD1   (K16)o - RMII1_TXD1   */ \
PAD_ENTRY(MII1_TXD0, MODE(1))/* 
RMII1_TXD0   (K17)o - RMII1_TXD0   */ \
PAD_ENTRY(RMII1_REFCLK,  MODE(0) | RXACTIVE)/* RMII1_RXCLK  (H18)i - 
RMII1_REFCLK */ \
PAD_ENTRY(MII1_RXD1, MODE(1) | RXACTIVE)   
 /* RMII1_RXD1   (L15)i - RMII1_RXD1   */ \
PAD_ENTRY(MII1_RXD0, MODE(1) | RXACTIVE)   
 /* RMII1_RXD0   (M16)i - RMII1_RXD0   */ \
PAD_ENTRY(GPMC_WPN,  MODE(3) | RXACTIVE)/* RMII2_RXERR  (U17)i - 
RMII2_RXERR  */ \
PAD_ENTRY(GPMC_A0,MODE(3))/* RMII2_TXEN   (R13)o - RMII2_TXEN   
*/ \
PAD_ENTRY(GPMC_WAIT0, MODE(3) | RXACTIVE)/* RMII2_CRS_DV (T17)i - 
RMII2_CRS_DV */ \
PAD_ENTRY(GPMC_A4, MODE(3))/* RMII2_TXD1   (R14)o - RMII2_TXD1 
  */ \
PAD_ENTRY(GPMC_A5, MODE(3))/* RMII2_TXD0   (V15)o - RMII2_TXD0 
  */ \
PAD_ENTRY(MII1_COL, MODE(1) | RXACTIVE)/* RMII2_RXCLK  (H16)i - 
RMII2_REFCLK */ \
PAD_ENTRY(GPMC_A10, MODE(3) | RXACTIVE)/* RMII2_RXD1   (T16)i - 
RMII2_RXD1   */ \
PAD_ENTRY(GPMC_A11, MODE(3) | RXACTIVE)/* RMII2_RXD0   (V17)i - 
RMII2_RXD0   */ \
PAD_ENTRY(MDIO_DATA,MODE(0) | RXACTIVE | PULLUP_EN)/* MDIO_DATA 
*/   \
PAD_ENTRY(MDIO_CLK,  MODE(0) | PULLUP_EN)/* 
MDIO_CLK */\

If anyone see something I did wrong or knows of additional things I need to 
do, I'd appreciate the insight.

Thanks,
Matt

-- 
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] Map R30/R31 EGPIO pins

[Charles Steinkuehler]

On 10/8/2014 10:56 PM, Ray Madigan wrote:
> I can't thank you enough for your help.  Every response is at least another 
> two day learning activity.  I just wish I didn't have to work to pay the 
> bills.
> 
> I went back to see what I did and it turns out I misspelled the name of the 
> dtbo file that I was using so there is no wonder it didn't work.
> Now I get an error that the file exists when I:
> 
> echo pru_enable > /sys/devices/bone_capemgr.8/slots
> 
> echo: write error: File exists
> prussdrv_open open failed
> 
> so I guess I have more to learn :(

The errors from capemgr are really cryptic.  You'll typically see "File
exists" when something you're trying to add to the device tree is
already in use.  There may be slightly more information in dmesg or the
kernel log.

Also note it is not really possible to unload a device-tree overlay, so
testing is a cycle of boot - test - shutdown.  :(

> What I am really trying to do is learn how to work with this device.  
> This activity is to learn to write to a set of 9 or 10 pins, 8 data and one 
> enable or 2 handshake.
> 
> My next step is to read fro a set of 9 or 10 pins, 8 for data and one for 
> write enable or 2 for a handshake.
> 
> So:
> 
> If I add your desired pinmux settings to a custom PRU overlay based off of 
> one of the BB-BONE-PRU overlays provided with the standard kernel.  What 
> would be the limitations?  

If you make a custom overlay and "hard-code" the pins you want to the
desired mode, the limitation is from then on you won't be able to change
them (without rebooting to unload your custom overlay).  If you use the
pinmux-helper as is done in the universal overlay, you can switch
between the available modes at run-time (via the generated sysfs entries).

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] BeagleBone Black device tree overlay applies, pinmux unchanged

[beagler001]

Trying to change over from BeagleBone White to Black. Like many others, I 
am having problems with DT overlays. No matter what I do, I cannot get the 
pinmux configuration to change. 

I am running with RCN's kernel rev 3.8.13-bone66 and Ubuntu 14.04.

Test overlay file I am applying can be found here: 
http://pastebin.com/iLfGun6r

DTC command used: dtc -O dtb -o BB-TESTCAPE2-00A0.dtbo -b 0 -@ 
tst_cape2.dts 

I scp'd the compiled overlay to the Beagle and copied into the 
/lib/firmware directory. I then ran the following on the Beagle: sudo sh -c 
"echo BB-TESTCAPE2 > /sys/devices/bone_capemgr.9/slots"

Dmesg output: 

[155948.247919] bone-capemgr bone_capemgr.9: part_number 'BB-TESTCAPE2', 
version 'N/A'
[155948.248099] bone-capemgr bone_capemgr.9: slot #8: generic override
[155948.248145] bone-capemgr bone_capemgr.9: bone: Using override eeprom data 
at slot 8
[155948.248192] bone-capemgr bone_capemgr.9: slot #8: 'Override Board 
Name,00A0,Override Manuf,BB-TESTCAPE2'
[155948.249863] bone-capemgr bone_capemgr.9: slot #8: Requesting part 
number/version based 'BB-TESTCAPE2-00A0.dtbo
[155948.249920] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 
'BB-TESTCAPE2-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[155948.24] bone-capemgr bone_capemgr.9: slot #8: dtbo 
'BB-TESTCAPE2-00A0.dtbo' loaded; converting to live tree
[155948.250453] bone-capemgr bone_capemgr.9: slot #8: #1 overlays
[155948.252634] bone-capemgr bone_capemgr.9: slot #8: Applied #1 overlays.


Slots configuration as follows:

cat $SLOTS
 0: 54:PF--- 
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-- Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-TESTCAPE2


Output of the pinmux configuration can be found here: 
http://pastebin.com/wjrRQURx

Notice the lack of change in pinmux settings for the pins I attempted to 
reconfigure.

If anyone can help, I would be most grateful.

-- 
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: boot error eeprom

[Jason Kridner]

Take a look at the official build script at
https://github.com/RobertCNelson/omap-image-builder/blob/master/beagleboard.org_image.sh
 (https://github.com/beagleboard/image-builder). Note the bbb-blank-eeprom
dtb option. Robert should be able to say where the source is at, but the
binaries are pointed to by https://rcn-ee.net/deb/tools/latest/bootloader-ng as
specific for BeagleBone Black (eeprom).

On Thursday, October 9, 2014, Ulisse Ruiz  wrote:

> *Hi,*
> *Im Ulisse Ruiz.*
> *I have a urgent question.*
> *I have 20 board black with eeprom blank.*
> *in test a error cause ereased eeprom and the boot not installing because
> eeprom is 0x*
> *Can you help me.*
> *is urgent thanks very much*
>
> *i search in multi post but without success*
> *Can you send me a boot with this patch?*
> *is very important...*
> *Thanks very much*
>
>
>
> *Ulisse Ruiz.*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

-- 
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] Reading all zero's from SPI using BBB Linux 3.14

[Dallas Clement]

Hi,

I recently upgraded from the 3.8 kernel to 3.14 and have been experiencing 
difficulty with reading from the SPI.  I seem to always read back zero's 
with a test program that was previously working on 3.8.  I have tried 
switching the pin mux sclk from an input to an output.  Doesn't seem to 
have helped.  The dtsi file is attached for the pinmux config.

Has anyone been able to successfully use SPI devices on the 3.14 kernel? 
 Neither SPI0 nor SPI1 seem to be able to read anything but zeros.

Thanks,

Dallas

-- 
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.


am335x-bone-common-pinmux.dtsi
Description: Binary data

[beagleboard] Regarding HDMI cable

[DEEPAK KESWANI]

Hello everyone,

I am currently working on Beaglebone Black processor.So for my project i 
need to see my output screen via Micro HDMI port.I have monitor with VGA 
port.So can you please suggest me cable converter for converting VGA to 
micro HDMI for beaglebone black?  

-- 
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] Map R30/R31 EGPIO pins

[Ray Madigan]

I found a problem that P9_31 conflicts with the HDMI Overlay so I will have 
to figure out if I try to eliminate it because it is not going to be used 
or if I can move the output to the pru1.


On Wednesday, October 8, 2014 11:59:37 PM UTC-7, Ray Madigan wrote:
>
> I also noticed in the exclusive-use list in the universal overlays you 
> have "pru0", "pru1", "pruss" with no other reference.  I don't have them in 
> mine?  What are they for?
>
> On Wednesday, October 8, 2014 11:47:04 PM UTC-7, Ray Madigan wrote:
>>
>> Taking your suggestion I went out to /lib/firmware and found several dts 
>> files that used pins like I want to use them.  The number of pins in the 
>> list I want are 1 to all Plus some.  The one that used all the pins I want 
>> to use include lots of stuff in the ocp fragment.  Is there a way to use a 
>> modified version of this one.  It is
>>
>> BB-BONE-PRU-04-00A0.dts
>>
>> On Wednesday, October 8, 2014 8:56:47 PM UTC-7, Ray Madigan wrote:
>>>
>>> I can't thank you enough for your help.  Every response is at least 
>>> another two day learning activity.  I just wish I didn't have to work to 
>>> pay the bills.
>>>
>>> I went back to see what I did and it turns out I misspelled the name of 
>>> the dtbo file that I was using so there is no wonder it didn't work.
>>> Now I get an error that the file exists when I:
>>>
>>> echo pru_enable > /sys/devices/bone_capemgr.8/slots
>>>
>>> echo: write error: File exists
>>> prussdrv_open open failed
>>>
>>> so I guess I have more to learn :(
>>>
>>> What I am really trying to do is learn how to work with this device.  
>>> This activity is to learn to write to a set of 9 or 10 pins, 8 data and 
>>> one enable or 2 handshake.
>>>
>>> My next step is to read fro a set of 9 or 10 pins, 8 for data and one 
>>> for write enable or 2 for a handshake.
>>>
>>> So:
>>>
>>> If I add your desired pinmux settings to a custom PRU overlay based off 
>>> of one of the BB-BONE-PRU overlays provided with the standard kernel.  What 
>>> would be the limitations?  
>>>
>>> I figure I could work out the problems at a later time.  after I see an 
>>> led light up:)
>>>
>>>
>>> On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler 
>>> wrote:

 On 10/8/2014 11:43 AM, Ray Madigan wrote: 
 > 
 > All I need to do is comment out the pins in exclusive-use section 
 that I 
 > don't want to use and comment out all of the entries for those pins 
 in the 
 > fragment.  Then comment out the sections for the modes I don't want 
 for the 
 > pins I do want? 

 If you use a "stripped down" version of the universal cape overlay, 
 you'll still have the pinmux helper in control of the pin multiplexing. 

 That means you'll need to either setup the proper pin choice using 
 sysfs 
 after loading the overlay or make the desired PRU pinmux mode the 
 default (or both). 

 Alternately, you could add your desired pinmux settings to a custom PRU 
 overlay based off of one of the BB-BONE-PRU overlays provided with the 
 standard kernel.  This would prevent any changes to the pinmux setting 
 after loading the overlay, which might be good or bad, depending on 
 exactly what you're attempting to do. 

 -- 
 Charles Steinkuehler 
 cha...@steinkuehler.net 

>>>

-- 
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] Map R30/R31 EGPIO pins

[Ray Madigan]

I also noticed in the exclusive-use list in the universal overlays you have 
"pru0", "pru1", "pruss" with no other reference.  I don't have them in 
mine?  What are they for?

On Wednesday, October 8, 2014 11:47:04 PM UTC-7, Ray Madigan wrote:
>
> Taking your suggestion I went out to /lib/firmware and found several dts 
> files that used pins like I want to use them.  The number of pins in the 
> list I want are 1 to all Plus some.  The one that used all the pins I want 
> to use include lots of stuff in the ocp fragment.  Is there a way to use a 
> modified version of this one.  It is
>
> BB-BONE-PRU-04-00A0.dts
>
> On Wednesday, October 8, 2014 8:56:47 PM UTC-7, Ray Madigan wrote:
>>
>> I can't thank you enough for your help.  Every response is at least 
>> another two day learning activity.  I just wish I didn't have to work to 
>> pay the bills.
>>
>> I went back to see what I did and it turns out I misspelled the name of 
>> the dtbo file that I was using so there is no wonder it didn't work.
>> Now I get an error that the file exists when I:
>>
>> echo pru_enable > /sys/devices/bone_capemgr.8/slots
>>
>> echo: write error: File exists
>> prussdrv_open open failed
>>
>> so I guess I have more to learn :(
>>
>> What I am really trying to do is learn how to work with this device.  
>> This activity is to learn to write to a set of 9 or 10 pins, 8 data and 
>> one enable or 2 handshake.
>>
>> My next step is to read fro a set of 9 or 10 pins, 8 for data and one for 
>> write enable or 2 for a handshake.
>>
>> So:
>>
>> If I add your desired pinmux settings to a custom PRU overlay based off 
>> of one of the BB-BONE-PRU overlays provided with the standard kernel.  What 
>> would be the limitations?  
>>
>> I figure I could work out the problems at a later time.  after I see an 
>> led light up:)
>>
>>
>> On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler 
>> wrote:
>>>
>>> On 10/8/2014 11:43 AM, Ray Madigan wrote: 
>>> > 
>>> > All I need to do is comment out the pins in exclusive-use section that 
>>> I 
>>> > don't want to use and comment out all of the entries for those pins in 
>>> the 
>>> > fragment.  Then comment out the sections for the modes I don't want 
>>> for the 
>>> > pins I do want? 
>>>
>>> If you use a "stripped down" version of the universal cape overlay, 
>>> you'll still have the pinmux helper in control of the pin multiplexing. 
>>>
>>> That means you'll need to either setup the proper pin choice using sysfs 
>>> after loading the overlay or make the desired PRU pinmux mode the 
>>> default (or both). 
>>>
>>> Alternately, you could add your desired pinmux settings to a custom PRU 
>>> overlay based off of one of the BB-BONE-PRU overlays provided with the 
>>> standard kernel.  This would prevent any changes to the pinmux setting 
>>> after loading the overlay, which might be good or bad, depending on 
>>> exactly what you're attempting to do. 
>>>
>>> -- 
>>> Charles Steinkuehler 
>>> cha...@steinkuehler.net 
>>>
>>

-- 
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.