date:20151029

[beagleboard] Re: Device Overlay to Disable USR0 LED

2015-10-29 Thread 73553js

Hello Joshua, 

Not sure if you'll see this but here goes.

You can modify the base dtb file at 
/boot/dtbs/3.8.XX-boneXX/am335x-boneblack.dtb by converting to dts, 
modifying, and converting back.  I followed the guide here, specifically 
"What is the device tree?" and step 
1:http://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2013/05/22/bbb--working-with-the-pru-icssprussv2

cd /boot/dtbs/3.8.13-bone70/ # navigate to dtb directory, may have to 
change version numbers
cp am335x-boneblack.dtb am335x-boneblack.dtb_orig # create a backup of the 
dtb incase anything goes wrong
dtc -I dtb -O dts am335x-boneblack.dtb > am335x-boneblack.dts_noled # 
convert dtb file to dts (human readable)
nano am335x-boneblack.dts_noled # open the file for editing with your 
favorite editor

Search for "led0".  Should be line no. ~946

 946 led0 {
 947 label = "beaglebone:green:usr0";
 948 gpios = <0x5 0x15 0x0>;
 949 linux,default-trigger = "heartbeat";
 950 default-state = "off";
 951 };
 952
 953 led1 {
 954 label = "beaglebone:green:usr1";
 955 gpios = <0x5 0x16 0x0>;
 956 linux,default-trigger = "mmc0";
 957 default-state = "off";
 958 };
 959
 960 led2 {
 961 label = "beaglebone:green:usr2";
 962 gpios = <0x5 0x17 0x0>;
 963 linux,default-trigger = "cpu0";
 964 default-state = "off";
 965 };
 966
 967 led3 {
 968 label = "beaglebone:green:usr3";
 969 gpios = <0x5 0x18 0x0>;
 970 default-state = "off";
 971 linux,default-trigger = "mmc1";
 972 };

All you have to do is change this line in led0

linux,default-trigger = "heartbeat";

to

linux,default-trigger = "none";

You can also repeat for leds 1,2, and 3 if desired.

Now just convert the dts back to dtb:

dtc -I dts -O dtb am335x-boneblack.dts_noled > am335x-boneblack.dtb_noled
cp am335x-boneblack.dtb_noled am335x-boneblack.dtb

and reboot!  Your leds should now be disabled.

If anything goes wrong you can always start over with your original backup 
copy.


On Wednesday, June 10, 2015 at 9:18:01 AM UTC-4, joshuap...@gmail.com wrote:
>
> HI Forum,
>
> I am attempting to create a device over lay for BBB "Linux beaglebone 
> 3.8.13-bone70" that will disable the linux heartbeat LED.  
>
> I am interested to do this primary as a learning process for device tree, 
> but I plan to use the BBB in a room where I don't want a LED to flash.
>
> I followed the guide at http://elinux.org/BeagleBone_and_the_3.8_Kernel. 
>
> dtc -O dtb -o BBB-LEDS.dtbo -b 0 -@ BBB-LEDS-00A0.dts
>
> sudo cp BBB-LEDS.dtbo /lib/firmware/
>
> sudo sh -c "echo BBB-LEDS > /sys/devices/bone_capemgr.9/slots"
>
> However the LED continues to flash.
>
> Could someone point me how to get the overlay to work?
>
> Thanks
>
> Joshua
>
> /dts-v1/;
> /plugin/;
> /
> {
>  compatible = "ti,beaglebone", "ti,beaglebone-black";
>  part-number = "BBB-LEDS";
>  version = "00A0";
>
>  fragment@0
>  {
>target = <&am33xx_pinmux>;
> __overlay__ 
>{
>  userled_pins: pinmux_userled_pins {
> pinctrl-single,pins = <
> 0x54 0x7 /* gpmc_a5.gpio1_21, OUTPUT | MODE7 */
> >;
>  };
> };
>  };
>
>  fragment@1
>   {
>  target = <&ocp>;
>  __overlay__
>  {
>  gpio-leds {
>  compatible = "gpio-leds";
>  pinctrl-names = "default";
>  pinctrl-0 = <&userled_pins>;
>  led0 {
>  label = "beaglebone:green:usr0";
>  gpios = <&gpio2 21 0>;
>  linux,default-trigger = "none";
>  default-state = "off";
>  };
>  };
>  };
>};
> };
>

-- 
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] ubuntu-14.04.3

2015-10-29 Thread Robert Nelson

On Thu, Oct 29, 2015 at 9:24 PM, Siv  wrote:
> Hi i have installed ubuntu-14.04.3 on my virtual Machine...After completion
> of the installation it is asking for Username and password.
>
> I have tried Ubuntu with blank password
> ubuntu: blank
> ubuntu:temppwd
>
> nothing works...Please help...

Have you tried asking the person you got the image from?

Regards,

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

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

[beagleboard] ubuntu-14.04.3

2015-10-29 Thread Siv

Hi i have installed ubuntu-14.04.3 on my virtual Machine...After completion 
of the installation it is asking for Username and password.

I have tried Ubuntu with blank password
ubuntu: blank
ubuntu:temppwd

nothing works...Please help...

-- 
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: BBB, GPMC bus for FPGA FIFO and 3.8 linux kernel

2015-10-29 Thread serkam

Hi Alberto

Could you succeed to access GPMC as you posted in your 22/10/13 post?

I am involved in similar project, that must access a FPGA that have a video 
FIFO connected to a video digitalizer and we need to transfer a video frame 
into BBB, using its GPMC.

Could you give some directions on how to access the GPMC in a BBB board?

Thanks

Sergio Kamakura
Warp Tecnologia

-- 
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: CAN BUS MCP2515 and dts labels

2015-10-29 Thread Ferdinand Haselbacher

Hi Eric,

which Probles do you encounter?

Do you have mikrobus-capes or another cape/shield?

i can send you my working dts for Angstrom if you want to.

A good starting point for getting this stuff working (if you're not using a 
mikrobus/cape) is to check TowerTechs TT3201 dts files, that's where i 
started. Maybe you can post your dts files and i'll see what i can make.

For me it is definitly working.
so far,
Ferdinand

Am Donnerstag, 29. Oktober 2015 15:10:30 UTC+1 schrieb Eric Schmidt:
>
> Did you ever figure this out? I am attempting the same thing and not 
> having 
> any luck. 
>
> Thanks, 
> Eric 
>
>
>

-- 
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] Linphone and PulseAudio only static and clicks instead of voice

2015-10-29 Thread Peter Gregory

I have a Beaglebone Black Rev C with a USB audio card using ALSA & PulseAudio
My USB audio card only seems to support 44khz for recording and playback.
I'm running linphonec 3.5.2 with Debian Linux beaglebone 3.8.13-bone72 #1 SMP 
Tue Jun 16 21:36:04 UTC 2015 armv7l GNU/Linux
My goal is to have peer-to-peer SIP communications between my Mac running 
Linphone and my BBB running Linphone.
They are able to communicate and connect to each other.
The audio on both sides comes across and clicks and static noises.
Any help would be appreciated.

The negotiation for audio looks like this:

ortp-message-cb_snd123456xx (id=1)
Connected.
linphonec> ortp-message-Call 0x6b8a8: moving from state 
LinphoneCallIncomingReceived to LinphoneCallConnected
Call 1 with  connected.
ortp-message-Audio bandwidth for this call is 44
ortp-message-speex_lib_ctl does not support SPEEX_LIB_CPU_FEATURE_NEON
ortp-message-cb_nict_kill_transaction (id=1)
ortp-message-eXosip: timer sec:0 usec:648457!
ortp-message-Payload's bitrate is 44000
ortp-message-Setting audio encoder network bitrate to 44000
ortp-message-ms_filter_link: MSAlsaRead:0x70e98,0-->MSSpeexEC:0x81250,1
ortp-message-ms_filter_link: MSSpeexEC:0x81250,1-->MSVolume:0x6fa98,0
ortp-message-ms_filter_link: MSVolume:0x6fa98,0-->MSSpeexEnc:0x6bcd0,0
ortp-message-ms_filter_link: MSSpeexEnc:0x6bcd0,0-->MSRtpSend:0x70f20,0
ortp-message-ms_filter_link: MSRtpRecv:0x789b8,0-->MSSpeexDec:0x6fa20,0
ortp-message-ms_filter_link: MSSpeexDec:0x6fa20,0-->MSDtmfGen:0x810b8,0
ortp-message-ms_filter_link: MSDtmfGen:0x810b8,0-->MSVolume:0x6be68,0
ortp-message-ms_filter_link: MSVolume:0x6be68,0-->MSEqualizer:0x6bed0,0
ortp-message-ms_filter_link: MSEqualizer:0x6bed0,0-->MSSpeexEC:0x81250,0
ortp-message-ms_filter_link: MSSpeexEC:0x81250,0-->MSAlsaWrite:0x76540,0
ortp-message-Initializing speex echo canceler with framesize=64, 
filterlength=4000, delay_samples=0
ortp-message-Setting maxbitrate=28000 to speex encoder.
ortp-message-Using bitrate 27800 for speex encoder, ip bitrate is 43600
ortp-message-Priority used: 99
ortp-message-Audio MSTicker setpriority() failed: Permission denied, nevermind.
ortp-message-Filter MSRtpRecv is already being scheduled; nothing to do.
ortp-message-Call 0x6b8a8: moving from state LinphoneCallConnected to 
LinphoneCallStreamsRunning
Media streams established with  for call 1.
ortp-message-call answered.
linphonec> ortp-message-alsa_open_r: opening default at 16000Hz, bits=16, 
stereo=0
xcb_connection_has_error() returned true
ortp-message-Received message: 
ACK sip:debian@10.128.84.154 SIP/2.0
Via: SIP/2.0/UDP 10.128.84.155:5060;rport;branch=z9hG4bK.FHinVVo8u
From: ;tag=gm8PDvkzI
To: ;tag=1705673520
CSeq: 20 ACK
Call-ID: 7x78li-cQI
Max-Forwards: 70


ortp-message-Message received from: 10.128.84.155:5060
ortp-message-Message received from: 10.128.84.155:5060
ortp-message-MESSAGE REC. CALLID:7x78li-cQI
ortp-message-Message received from: 10.128.84.155:5060
ortp-message-This is a request
ortp-message-linphone process event get a message 15

ortp-message-CALL_ACK
ortp-message-eXosip: timer sec:0 usec:547862!
ortp-warning-alsa_set_params: periodsize:512 Using 512
ortp-warning-alsa_set_params: period:8 Using 8
ortp-message-alsa_open_r: Audio params set
ortp-message-ms_ticker_set_time_func: ticker updated.
ortp-warning-Getting reference signal but no echo to synchronize on.
ortp-warning-Not enough ref samples, using zeroes
ortp-message-alsa_open_w: opening default at 16000Hz, bits=16, stereo=0
xcb_connection_has_error() returned true
ortp-warning-alsa_set_params: periodsize:512 Using 512
ortp-warning-alsa_set_params: period:8 Using 8
ortp-message-bandwidth usage: audio=[d=0.0,u=0.0] video=[d=0.0,u=0.0] kbit/sec
ortp-message-Thread processing load: audio=129.954559   video=0.00
ortp-message-alsa_open_w: Audio params set


My configuration for Linphone is the default it creates when started:

debian@beaglebone:~$ cat .linphonerc 
[sip]
media_encryption=none
guess_hostname=1
contact=sip:debian@unknown-host
inc_timeout=15
use_info=0
use_rfc2833=0
use_ipv6=0
register_only_when_network_is_up=1

[net]
download_bw=0
upload_bw=0
firewall_policy=0
mtu=0

[call_log_0]
dir=1
status=0
from=
to=
start_date=Thu Oct 29 12:23:34 2015
duration=14
quality=1.889588

[rtp]
audio_rtp_port=7078
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=60
nortp_timeout=30

[sound]
remote_ring=/usr/share/sounds/linphone/ringback.wav

[video]
size=cif
display=0
capture=0
show_local=0
self_view=1

[audio_codec_0]
mime=speex
rate=32000
enabled=1

[audio_codec_1]
mime=speex
rate=16000
enabled=1

[audio_codec_2]
mime=speex
rate=8000
enabled=1

[audio_codec_3]
mime=GSM
rate=8000
enabled=1

[audio_codec_4]
mime=PCMU
rate=8000
enabled=1

[audio_codec_5]
mime=PCMA
rate=8000
enabled=1

[audio_codec_6]
mime=L16
rate=44100
enabled=0

[audio_codec_7]
mime=L16
rate=44100
enabled=0

[audio_codec_8]
mime=G722
rate=8000
enabled=0

[video_codec_0]
mime=MP4V-ES
rate=9
enabled=1
recv_fmtp=profile-level-id=3

[video_

Re: [beagleboard] BBB Shipments

2015-10-29 Thread Gerald Coley

I would say that having another maker of the design does affect overall
sales of the BeagleBone Black.

Gerlad


On Thu, Oct 29, 2015 at 10:06 AM, Kees k  wrote:

> Hello all,
>
> Today I looked on http://elinux.org/Beagleboard:BeagleBoneBlack and saw
> that the montly shipments are much lower in 2015.
> Is this because there are two manufacturers now? (element14/embest and
> circuitco) Or because of decreasing demand?
>
>
> Kind regards
>
> Kees
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

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

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

[beagleboard] BBB Shipments

2015-10-29 Thread Kees k

Hello all,

Today I looked on http://elinux.org/Beagleboard:BeagleBoneBlack and saw 
that the montly shipments are much lower in 2015. 
Is this because there are two manufacturers now? (element14/embest and 
circuitco) Or because of decreasing demand?


Kind regards

Kees


-- 
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: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

2015-10-29 Thread Przemek Klosowski

The circuit looks reasonable in general, but it's hard to tell because you
don't show all the connections and labels. Like, what are the G and V
things on the relay boards? I assume you're talking about
http://www.superdroidrobots.com/product_info/TE-249-070_Schematic.pdf, so
probably JP17-1 and -2, but how would we know for sure? can you redraw your
schematic with more specific connection diagram, listing the specific
connections you make to the relay board and the DAC?

Also, it's possible to mess up by plugging the things in the wrong
sequence, e.g. if you work under power and connect the data lines before
connecting power.

On Wed, Oct 28, 2015 at 10:57 PM, Yongfan Men  wrote:

> Forgot to attach the illustration figure.
>
>
> On Wednesday, October 28, 2015 at 10:41:36 PM UTC-4, Yongfan Men wrote:
>>
>>
>> I burnt my BBB, which let me very sad. I ordered a new one online because
>> it's an urgent project, but until I have fully figured out what happened
>> with my circuit, I dare not connect the BBB to it again.
>>
>> This circuit, as shown in  the attached image, worked all well during the
>> last whole week. I turned it off this Monday, and turned it on this
>> morning, and Bang! The BBB's burnt. It won't boot up. When I plug the 5V
>> power cable or mini USB cable to it, only the PWR LED will light up a
>> little bit, and it never boots up again. I didn't believe it's my circuit's
>> fault, so I plugged my backup BBB on, and again, it's killed. I burned $100
>> in 10 minutes.
>>
>> I'm attaching the circuit design here because I need to know if this
>> design is really problematic. Let me explain a little bit: I'm trying to
>> control an I/P converter (SMC ITV0011), which is driven by a 0-5V voltage
>> signal and powered by 12V dc. *The problem is It only has three wires,
>> and the ground wire is shared.* That's why I think I have to connect all
>> of the ground wires together.
>>
>> I'm using a DAC chip (MCP4725) to generate a proper voltage control
>> signal to the I/P converter. This DAC chip is communicated by I2C, and
>> powered directly by the onboard 3.3V from the BBB. I have carefully checked
>> with multimeter that with digital command through I2C, the voltage could be
>> linearly generated, which is very cool.
>>
>> I'm using a GPIO to control a relay (powered by 5V) to control the on/off
>> of the I/P converter, which means only when I want the I/P converter to be
>> turned on, I will send the GPIO to 1. Otherwise, when GPIO is 0, the I/P
>> converter would not be powered, which is a way of enlarging the lifetime of
>> the $200 I/P converter.
>>
>> That's the whole idea. And I also used a Qt GUI to control the output of
>> both the I2C and GPIO. Last week, I enjoyed a lot using the stylus to drag
>> the slidebar on the touch screen to adjust the pressure output by the I/P
>> Converter. I just don't understand why it suddenly became so dangerous.
>>
>> But last week I did noticed one strange phenomenon. When the relay was
>> not working, there is a strange minus 17 volt on the relay output port.
>> This is probably 12V + 5V, But I don't understand neither why this is a sum
>> nor why it is negative, and since everything works, I didn't pay attention.
>>
>> Today, after I burned the two BBB, I measured the voltage of the relay
>> output port when it's off again. The voltage is 1.7V (5V-3.3V?). So strange!
>>
>> From my newbie understanding, any output signal should has two wires, one
>> signal wire, and one ground wire. Because you need a closed circuit to
>> transfer electrons. That's how coaxial cable works for oscilloscope, and
>> function generator, and multimeter, and so forth. Therefore I'm connecting
>> the GND from BBB to DAC, and the GND from DAC to I/P converter; also the
>> GND from 12V dc power source to the I/P converter. *This equals that the
>> Ground from the 12V dc power source is directly connected to the BBB*.
>> But theoretically, I don't see any problems, since it's just ground!
>>
>> In the image, I think once I remove the red wire, the BBB will be
>> isolated from the whole 5V and 12V dc circuits. But I don't know if this is
>> the right solution, and also if the voltage output from the DAC will be
>> transfered to the I/P converter. If any of you could explain a little bit
>> about this issue, I would appreciate a lot.
>>
>> Also, If I want to add some more protection to the BBB (on both I2C and
>> GPIO), what should I do? Thanks!
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Is it possible to shutdown Main CPU and keep PRU running?

2015-10-29 Thread st . staudacher


Hello there!

Is it possible to boot the Black, load a PRU binary, start it, shutdown the 
Main CPU again and keep a PRU Running?

Would this reduce energy consumption? Can sb. approximate by which factor?

Is it possible to start the Main System agein and read the Results or Logs 
from PRU work out of the memory again?

How would that look like practicle? Load PRU Program, shutdown linux distro 
without -h and -P arguments to keep power supply, boot distro after some 
time, relink to pru completion interruptevent, read the memory for results?

I'm sorry I'm not very experienced with this. I read and workesd through 
the Book "Exploring Beaglebone Tools and Techniques for building with 
embedded Linux" by Derek Molloy and found it extremly helpfull!

But I couldn't find out about the above questions.

Thanks in advance!

Stefan

-- 
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: Unable to Connect to BBB via USB from OSX Yosemite

2015-10-29 Thread yo . ian . g

Following these steps exactly worked for me with El Capitan, must be 10.11.1
https://github.com/jwise/HoRNDIS/issues/42#issuecomment-150522963

On Friday, February 27, 2015 at 9:07:22 PM UTC-5, Brad Nicholas wrote:
>
> confirm that BBB USB comms working perfectly on Yosemite, Win7 and Debian 
> 7.8 Wheezy here (triple boot mb air 4,2).  Installed directly off the BBB's 
> web page.
>

-- 
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: Unable to Connect to BBB via USB from OSX Yosemite

2015-10-29 Thread yo . ian . g

Not working here with OSX El Capitan, anyone have any insight into the 
issue previously?

On Monday, December 22, 2014 at 2:22:07 AM UTC-5, bigsti...@gmail.com wrote:
>
> When running Mavericks connecting via USB to my BBB Rev A6A was amazingly 
> simple.
>
> After updating to Yosemite I've not been able to successfully 
> install/re-install the USB/Network or Serial drivers or to connect to the 
> board at http://192.168.7.2/
>
> I've downloaded, reinstalled latest HornDIS rev 7 drivers and FTDI 2.2.18 
> serial drivers and restarted my laptop numerous times but still cannot 
> connect to my BBB as before with Mavericks.
>
> Any suggestions would be most welcome.
>

-- 
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] OSX el Capitan breaks HoRNDIS?

2015-10-29 Thread yo . ian . g

Following these steps exactly worked for me:
https://github.com/jwise/HoRNDIS/issues/42#issuecomment-150522963

On Saturday, October 24, 2015 at 5:55:06 PM UTC-4, Heath Raftery wrote:
>
> On Sunday, October 25, 2015 at 6:34:18 AM UTC+11, Heath Raftery wrote:
>>
>> On Wednesday, October 21, 2015 at 2:17:44 AM UTC+11, RobertCNelson wrote:
>>>
>>>
>>> http://nyus.joshuawise.com/HoRNDIS-rel8pre1.pkg 
>>>
>>>
>> Anyone get this version to work? There's certainly progress since the 
>> kext now happily loads. But nothing happens when I plug the Beaglebone in. 
>> In particular, nothing appears in System Preferences -> Network, and 
>> there's no response from 192.168.7.2. Is there another step to turn 
>> "tethering" on in the Beaglebone?
>>
>> Answering my own question: there's nothing more to do, except upgrade to 
> 10.11.1. Then it all just works! 
>

-- 
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: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

2015-10-29 Thread evilwulfie


You MUST have all grounds tied together or you will have very
unpredictable results including smoked BBB boards.
The only thing i can really think of after looking at your circuit is
that when you turn off your project the power supplies
you are using do not all power down the same.  Can you be sure that when
the BBB is powered off the relay does not blip on ? as the BBB is
powering off if that relay happens to turn on and there is still 12v
being provided by that power supply you do have a chance to zap the BBB.
Isolation of the BBB using an opto isolator is your best bet to make
this work.


On 10/28/2015 7:57 PM, Yongfan Men wrote:
> Forgot to attach the illustration figure.
>
> On Wednesday, October 28, 2015 at 10:41:36 PM UTC-4, Yongfan Men wrote:
>
>
> I burnt my BBB, which let me very sad. I ordered a new one online
> because it's an urgent project, but until I have fully figured out
> what happened with my circuit, I dare not connect the BBB to it
> again.
>
> This circuit, as shown in  the attached image, worked all well
> during the last whole week. I turned it off this Monday, and
> turned it on this morning, and Bang! The BBB's burnt. It won't
> boot up. When I plug the 5V power cable or mini USB cable to it,
> only the PWR LED will light up a little bit, and it never boots up
> again. I didn't believe it's my circuit's fault, so I plugged my
> backup BBB on, and again, it's killed. I burned $100 in 10 minutes.
>
> I'm attaching the circuit design here because I need to know if
> this design is really problematic. Let me explain a little bit:
> I'm trying to control an I/P converter (SMC ITV0011), which is
> driven by a 0-5V voltage signal and powered by 12V dc. _The
> problem is It only has three wires, and the ground wire is
> shared._ That's why I think I have to connect all of the ground
> wires together.
>
> I'm using a DAC chip (MCP4725) to generate a proper voltage
> control signal to the I/P converter. This DAC chip is communicated
> by I2C, and powered directly by the onboard 3.3V from the BBB. I
> have carefully checked with multimeter that with digital command
> through I2C, the voltage could be linearly generated, which is
> very cool.
>
> I'm using a GPIO to control a relay (powered by 5V) to control the
> on/off of the I/P converter, which means only when I want the I/P
> converter to be turned on, I will send the GPIO to 1. Otherwise,
> when GPIO is 0, the I/P converter would not be powered, which is a
> way of enlarging the lifetime of the $200 I/P converter.
>
> That's the whole idea. And I also used a Qt GUI to control the
> output of both the I2C and GPIO. Last week, I enjoyed a lot using
> the stylus to drag the slidebar on the touch screen to adjust the
> pressure output by the I/P Converter. I just don't understand why
> it suddenly became so dangerous.
>
> But last week I did noticed one strange phenomenon. When the relay
> was not working, there is a strange minus 17 volt on the relay
> output port. This is probably 12V + 5V, But I don't understand
> neither why this is a sum nor why it is negative, and since
> everything works, I didn't pay attention.
>
> Today, after I burned the two BBB, I measured the voltage of the
> relay output port when it's off again. The voltage is 1.7V
> (5V-3.3V?). So strange!
>
> From my newbie understanding, any output signal should has two
> wires, one signal wire, and one ground wire. Because you need a
> closed circuit to transfer electrons. That's how coaxial cable
> works for oscilloscope, and function generator, and multimeter,
> and so forth. Therefore I'm connecting the GND from BBB to DAC,
> and the GND from DAC to I/P converter; also the GND from 12V dc
> power source to the I/P converter. _This equals that the Ground
> from the 12V dc power source is directly connected to the BBB_.
> But theoretically, I don't see any problems, since it's just ground!
>
> In the image, I think once I remove the red wire, the BBB will be
> isolated from the whole 5V and 12V dc circuits. But I don't know
> if this is the right solution, and also if the voltage output from
> the DAC will be transfered to the I/P converter. If any of you
> could explain a little bit about this issue, I would appreciate a lot.
>
> Also, If I want to add some more protection to the BBB (on both
> I2C and GPIO), what should I do? Thanks!
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout

AW: [beagleboard] Re: CAN BUS MCP2515 and dts labels

2015-10-29 Thread Ferdinand Haselbacher

Yes Did succeed send you more information tonight CET


Ferdinand Haselbacher
  Originalnachricht  
Von: Eric Schmidt
Gesendet: Donnerstag, 29. Oktober 2015 15:10
An: beagleboard@googlegroups.com
Antwort an: beagleboard@googlegroups.com
Betreff: [beagleboard] Re: CAN BUS MCP2515 and dts labels

Did you ever figure this out? I am attempting the same thing and not having 
any luck.

Thanks,
Eric


-- 
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/MxLBF4hOX4w/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: CAN BUS MCP2515 and dts labels

2015-10-29 Thread Eric Schmidt

Did you ever figure this out? I am attempting the same thing and not having 
any luck.

Thanks,
Eric


-- 
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: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

2015-10-29 Thread Yongfan Men

This DAC has a flexable input voltage option. So if I'm inputing a 3.3V
voltage to it, by controlling via I2C, I can get a 0~3.3V linear voltage
output. That 5V power source is just for powering the relay and the BBB &
touch screen. So I don't think I'm driving a 5V circuit with BBB. On the
other hand, I think the BBB can also output 5V, so I can as well give the
DAC a 5V directly from BBB, right?

2015-10-28 23:30 GMT-04:00 Bill Pretty :

> After just a quick look at the circuit, I suspect that the BBB is trying
> to source/sink too much current?
>
>
>
> Also, the BBB has 3.3V logic and you are driving 5V logic. I would suggest
> that you use an opto-isolator
>
> for both isolation and logic level conversion.
>
>
>
> Bill
>
> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
> *On Behalf Of *Yongfan Men
> *Sent:* Wednesday, October 28, 2015 10:58 PM
> *To:* BeagleBoard
> *Subject:* [beagleboard] Re: My circuit that burnt my BBB needs modify: I
> wonder if the ground is necessary
>
>
>
> Forgot to attach the illustration figure.
>
> On Wednesday, October 28, 2015 at 10:41:36 PM UTC-4, Yongfan Men wrote:
>
>
> I burnt my BBB, which let me very sad. I ordered a new one online because
> it's an urgent project, but until I have fully figured out what happened
> with my circuit, I dare not connect the BBB to it again.
>
>
>
> This circuit, as shown in  the attached image, worked all well during the
> last whole week. I turned it off this Monday, and turned it on this
> morning, and Bang! The BBB's burnt. It won't boot up. When I plug the 5V
> power cable or mini USB cable to it, only the PWR LED will light up a
> little bit, and it never boots up again. I didn't believe it's my circuit's
> fault, so I plugged my backup BBB on, and again, it's killed. I burned $100
> in 10 minutes.
>
>
>
> I'm attaching the circuit design here because I need to know if this
> design is really problematic. Let me explain a little bit: I'm trying to
> control an I/P converter (SMC ITV0011), which is driven by a 0-5V voltage
> signal and powered by 12V dc. *The problem is It only has three wires,
> and the ground wire is shared.* That's why I think I have to connect all
> of the ground wires together.
>
>
>
> I'm using a DAC chip (MCP4725) to generate a proper voltage control signal
> to the I/P converter. This DAC chip is communicated by I2C, and powered
> directly by the onboard 3.3V from the BBB. I have carefully checked with
> multimeter that with digital command through I2C, the voltage could be
> linearly generated, which is very cool.
>
>
>
> I'm using a GPIO to control a relay (powered by 5V) to control the on/off
> of the I/P converter, which means only when I want the I/P converter to be
> turned on, I will send the GPIO to 1. Otherwise, when GPIO is 0, the I/P
> converter would not be powered, which is a way of enlarging the lifetime of
> the $200 I/P converter.
>
>
>
> That's the whole idea. And I also used a Qt GUI to control the output of
> both the I2C and GPIO. Last week, I enjoyed a lot using the stylus to drag
> the slidebar on the touch screen to adjust the pressure output by the I/P
> Converter. I just don't understand why it suddenly became so dangerous.
>
>
>
> But last week I did noticed one strange phenomenon. When the relay was not
> working, there is a strange minus 17 volt on the relay output port. This is
> probably 12V + 5V, But I don't understand neither why this is a sum nor why
> it is negative, and since everything works, I didn't pay attention.
>
>
>
> Today, after I burned the two BBB, I measured the voltage of the relay
> output port when it's off again. The voltage is 1.7V (5V-3.3V?). So strange!
>
>
>
> From my newbie understanding, any output signal should has two wires, one
> signal wire, and one ground wire. Because you need a closed circuit to
> transfer electrons. That's how coaxial cable works for oscilloscope, and
> function generator, and multimeter, and so forth. Therefore I'm connecting
> the GND from BBB to DAC, and the GND from DAC to I/P converter; also the
> GND from 12V dc power source to the I/P converter. *This equals that the
> Ground from the 12V dc power source is directly connected to the BBB*.
> But theoretically, I don't see any problems, since it's just ground!
>
>
>
> In the image, I think once I remove the red wire, the BBB will be isolated
> from the whole 5V and 12V dc circuits. But I don't know if this is the
> right solution, and also if the voltage output from the DAC will be
> transfered to the I/P converter. If any of you could explain a little bit
> about this issue, I would appreciate a lot.
>
>
>
> Also, If I want to add some more protection to the BBB (on both I2C and
> GPIO), what should I do? Thanks!
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it

Re: [beagleboard] Reverse Polarity 5V Connection

2015-10-29 Thread 'andrew stillie' via BeagleBoard

Thank you.  I have sent the form.

I have checked all the voltage rails and they appear correct.  I plan to
check the crystal at lunchtime.

Maybe I have damaged the emmc.
Return Material Authorization. It is a process whereby broken hardware is
repaired.

http://www.elinux.org/Beagleboard:BeagleBoneBlack#RMA_Support


Gerald

On Wed, Oct 28, 2015 at 4:54 PM, 'andrew stillie' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Thanks Gerald,  excuse my ignorance but what is a RMA and how do I request
> one?
>
> On Wed, 28 Oct 2015 21:23 Gerald Coley  wrote:
>
>> Possibly could have killed it. Swapping processor I would think might be
>> difficult not to mention of something else was blown, you could blow it
>> again..
>>
>> eMMC could be saved if the fix to repair it is successful and the eMMC is
>> still working.
>>
>> I suggest you request and RMA and let us see what we can do.
>>
>> Gerald
>>
>>
>>
>> On Wed, Oct 28, 2015 at 4:14 PM, AndyS 
>> wrote:
>>
>>> Hi All,
>>>
>>> I just powered my BBB with the 5V power jack wired reversed.Would
>>> this have killed the Sitara or are there some likely components I should
>>> try swapping out?
>>>
>>> The 3V3 rail appears fine.
>>>
>>> No activity on the USER -LEDS.
>>>
>>> Also is there any way of recovering data I have stored on the eMMC?
>>>
>>> Thanks in advance.
>>>
>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/fQdUqwMcs_Q/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.
>



-- 
Gerald

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

-- 
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/fQdUqwMcs_Q/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: Device Overlay to Disable USR0 LED

Re: [beagleboard] ubuntu-14.04.3

[beagleboard] ubuntu-14.04.3

[beagleboard] Re: BBB, GPMC bus for FPGA FIFO and 3.8 linux kernel

[beagleboard] Re: CAN BUS MCP2515 and dts labels

[beagleboard] Linphone and PulseAudio only static and clicks instead of voice

Re: [beagleboard] BBB Shipments

[beagleboard] BBB Shipments

Re: [beagleboard] Re: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

[beagleboard] Is it possible to shutdown Main CPU and keep PRU running?

[beagleboard] Re: Unable to Connect to BBB via USB from OSX Yosemite

[beagleboard] Re: Unable to Connect to BBB via USB from OSX Yosemite

Re: [beagleboard] OSX el Capitan breaks HoRNDIS?

Re: [beagleboard] Re: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

AW: [beagleboard] Re: CAN BUS MCP2515 and dts labels

[beagleboard] Re: CAN BUS MCP2515 and dts labels

Re: [beagleboard] Re: My circuit that burnt my BBB needs modify: I wonder if the ground is necessary

Re: [beagleboard] Reverse Polarity 5V Connection

18 matches

Site Navigation

Mail list logo

Footer information