Re: [beagleboard] Blue booting as Robot controller vs. booting as Linux computer

2017-08-03 Thread Jason Kridner


> On Aug 3, 2017, at 4:57 PM, Mark A. Yoder  wrote:
> 
> Sounds like a good idea.  How do I turn on the ADC drivers?

https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-custom.dts#L56

> 
> --Mark
> 
>> On Thursday, August 3, 2017 at 2:45:44 PM UTC-4, Jason Kridner wrote:
>> 
>> 
>>> On Aug 3, 2017, at 2:32 PM, Mark A. Yoder  wrote:
>>> 
>>> It looks like when the Blue comes out of the box, running a current image 
>>> it's all set up to run the Robotics stuff. You can access the ADCs, servos, 
>>> etc. through the robot interface.
>>> 
>>> When I teach my Embedded Linux class I would also like my students to 
>>> access the ADCs, PWM, etc in the Linux way.  
>>> 
>>> How do I configure the Blue to boot up in "Embedded Linux" mode rather than 
>>> "Robot Linux" mode?
>> 
>> If we get the integration right, IMO, we'll boot up so that we can use the 
>> Linux userspace interfaces and the libroboticscape interfaces. The 
>> libroboticscape setup should do whatever is needed to disable Linux kernel 
>> drivers at runtime in order to enable its userspace accesses. 
>> 
>> Turn on the ADC kernel drivers and look how libroboticscape fails. Then, 
>> report that as a bug. 
>> 
>> 
>>> 
>>> --Mark
>>> 
>>> 
 On Wednesday, August 2, 2017 at 11:15:40 AM UTC-4, Mark A. Yoder wrote:
 It sounds like I can either have a Blue that boots as a robot, or boots as 
 an embedded processor, but not both at the same time.
 I need to see what it would take to remove the ADC from the robots control.
 
 --Mark
 
> On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote:
> I have lived on BBB + Robotics Cape in James' world for some time. While 
> I haven't done this with a Blue, I suspect what I did can work there too. 
> I did do his installation (for a Rev C BBB and a Rev D Robotics Cape). 
> With Robert's help I put the Capemgr back in the DTs and added the 
> capemgr partno boot line for BB-ADC.  This seems to be a workable 
> combination of the two worlds. My premise is that I don't try to do both 
> at once.  That is, I don't run any of the rc_* apps or services while 
> trying to read the ADCs from /sys/bus/iio. So far it seems to work for me.
> Hugh
> 
>> On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:
>> Yup, this is the Blue.
>> In there short term is there an easy way to turn off the robotics stuff 
>> and get easy access to the analog in?
>> 
>> In the long term, what will it take to convert James' robot stuff to 
>> libiio?  I might take a shot at it if it isn't too hard.
>> 
>> --Mark
>> 
>>> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:
>>> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
>>> wrote: 
>>> > How do I read AIN on the latest images?  I don't know where to find 
>>> > it in 
>>> > /sys/ 
>>> 
>>> Hi Mark, 
>>> 
>>> This is with the Blue right? 
>>> 
>>> James' got the ADC tied up in mmap for the Robotic's cape library.. 
>>> 
>>> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c
>>>  
>>> 
>>> We need to convert his library to use libiio, then we can just enable 
>>> the ADC's as an iio device and share usage with the library.. 
>>> 
>>> https://analogdevicesinc.github.io/libiio/ 
>>> 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/df730860-d5e5-4aad-8968-20a5e4188b50%40googlegroups.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.
To view this discussion on the 

[beagleboard] Re: Cannot start kernel after update_kernel.sh --bone-kernel --stable

2017-08-03 Thread dyen
  Yay !   Use the mount command to see the /dev/mmcblk1p1 is the root 
filesystem.
lsblk -no UUID /dev/mmcblk1p1
gives the UUID which can be entered into /boot/uEnv.txt
and also comment out enable_boot_overlays=1
#enable_uboot_overlays=1

Now our driver can be compiled against the 3.8.13 headers, hurray.

arm login: ubuntu
Password:
Last login: Fri Jul 14 14:48:35 UTC 2017 on ttyS0
Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 3.8.13-bone86 armv7l)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage
ubuntu@arm:~$ uname -r
3.8.13-bone86

On Thursday, August 3, 2017 at 1:20:39 PM UTC-7, dy...@sentons.com wrote:
>
> *  My second and brand new Beaglebone Black was flashed to eMMC and worked 
> fine with *
> BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-07-14-2gb.img
> *following the excellent instructions of*
>
>
> http://derekmolloy.ie/write-a-new-image-to-the-beaglebone-black/#prettyPhoto
>
> *Next installed:* sudo apt install linux-headers-3.8.13-bone86
>
> *because we have a driver that needs those 3.8.13 headers.*
>
> *We have a script that calls* update_kernel.sh --bone-kernel --stable
>
> *Afterwards the reboot will not start the kernel.  My first board used 
> 3.8.13-bone84 alright but is running from microSD not eMMC.*
>
> *What is causing kernel start failure and how to fix it?  Should I just 
> replace the `uname -r` in the driver Makefile with explicit 3.8.13-bone86 
> ???*
>
> *Console output for second Beaglebone Black has:*
>
>
> Running uname_boot ...
>
> loading /boot/vmlinuz-3.8.13-bone86 ...
>
> 5594568 bytes read in 373 ms (14.3 MiB/s)
>
> uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
>
> loading /boot/dtbs/3.8.13-bone86/am335x-boneblack.dtb ...
>
> 26118 bytes read in 31 ms (822.3 KiB/s)
>
> uboot_overlays: [fdt_buffer=0x6] ...
>
> uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo ...
>
> 378 bytes read in 340 ms (1000 Bytes/s)
>
> fdt_overlay_apply(): FDT_ERR_NOTFOUND
>
> uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
>
> 1105 bytes read in 238 ms (3.9 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
>
> 4169 bytes read in 134 ms (30.3 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
>
> 695 bytes read in 350 ms (1000 Bytes/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo ...
>
> 2402 bytes read in 130 ms (17.6 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
>
> 54858 bytes read in 209 ms (255.9 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> loading /boot/initrd.img-3.8.13-bone86 ...
>
> 4705709 bytes read in 320 ms (14 MiB/s)
>
> debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0 quiet cape_universal=enable] ...
>
> debug: [bootz 0x8200 0x8808:47cdad 8800] ...
>
> ERROR: Did not find a cmdline Flattened Device Tree
>
> Could not find a valid device tree
>
>
> and finally is stuck at boot prompt,
>
>
> Config file not found
>
> starting USB...
>
> USB0:   Port not available.
>
> link up on port 0, speed 100, full duplex
>
> BOOTP broadcast 1
>
> DHCP client bound to address 10.150.100.52 (37 ms)
>
> Using cpsw device
>
> TFTP from server 0.0.0.0; our IP address is 10.150.100.52; sending through 
> gateway 10.150.100.1
>
> Filename 'boot.scr.uimg'.
>
> Load address: 0x8000
>
> Loading: T T T T T T T T T T T T T T T T T T T T
>
> Retry count exceeded; starting again
>
> link up on port 0, speed 100, full duplex
>
> BOOTP broadcast 1
>
> DHCP client bound to address 10.150.100.52 (40 ms)
>
> Using cpsw device
>
> TFTP from server 0.0.0.0; our IP address is 10.150.100.52; sending through 
> gateway 10.150.100.1
>
> Filename 'boot.scr.uimg'.
>
> Load address: 0x8200
>
> Loading: T T T T T T T T T T T T T T T T T T T T
>
> Retry count exceeded; starting again
>
> =>
>
> *Would really enjoy running from eMMC rather than microSD.  While waiting 
> for reply, I will try changing the driver Makefile to explicitly plug in 
> 3.8.13-bone86, which means I have to reflash since otherwise I am stuck at 
> boot prompt.*
>

-- 
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.
To view this discussion on 

Re: [beagleboard] Blue booting as Robot controller vs. booting as Linux computer

2017-08-03 Thread Jason Kridner


> On Aug 3, 2017, at 2:32 PM, Mark A. Yoder  wrote:
> 
> It looks like when the Blue comes out of the box, running a current image 
> it's all set up to run the Robotics stuff. You can access the ADCs, servos, 
> etc. through the robot interface.
> 
> When I teach my Embedded Linux class I would also like my students to access 
> the ADCs, PWM, etc in the Linux way.  
> 
> How do I configure the Blue to boot up in "Embedded Linux" mode rather than 
> "Robot Linux" mode?

If we get the integration right, IMO, we'll boot up so that we can use the 
Linux userspace interfaces and the libroboticscape interfaces. The 
libroboticscape setup should do whatever is needed to disable Linux kernel 
drivers at runtime in order to enable its userspace accesses. 

Turn on the ADC kernel drivers and look how libroboticscape fails. Then, report 
that as a bug. 


> 
> --Mark
> 
> 
>> On Wednesday, August 2, 2017 at 11:15:40 AM UTC-4, Mark A. Yoder wrote:
>> It sounds like I can either have a Blue that boots as a robot, or boots as 
>> an embedded processor, but not both at the same time.
>> I need to see what it would take to remove the ADC from the robots control.
>> 
>> --Mark
>> 
>>> On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote:
>>> I have lived on BBB + Robotics Cape in James' world for some time. While I 
>>> haven't done this with a Blue, I suspect what I did can work there too. I 
>>> did do his installation (for a Rev C BBB and a Rev D Robotics Cape). With 
>>> Robert's help I put the Capemgr back in the DTs and added the capemgr 
>>> partno boot line for BB-ADC.  This seems to be a workable combination of 
>>> the two worlds. My premise is that I don't try to do both at once.  That 
>>> is, I don't run any of the rc_* apps or services while trying to read the 
>>> ADCs from /sys/bus/iio. So far it seems to work for me.
>>> Hugh
>>> 
 On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:
 Yup, this is the Blue.
 In there short term is there an easy way to turn off the robotics stuff 
 and get easy access to the analog in?
 
 In the long term, what will it take to convert James' robot stuff to 
 libiio?  I might take a shot at it if it isn't too hard.
 
 --Mark
 
> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:
> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
> wrote: 
> > How do I read AIN on the latest images?  I don't know where to find it 
> > in 
> > /sys/ 
> 
> Hi Mark, 
> 
> This is with the Blue right? 
> 
> James' got the ADC tied up in mmap for the Robotic's cape library.. 
> 
> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c
>  
> 
> We need to convert his library to use libiio, then we can just enable 
> the ADC's as an iio device and share usage with the library.. 
> 
> https://analogdevicesinc.github.io/libiio/ 
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/F2C0A1E5-41EB-4E40-9431-A933D69ECAD7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Blue booting as Robot controller vs. booting as Linux computer

2017-08-03 Thread Mark A. Yoder
It looks like when the Blue comes out of the box, running a current image 
it's all set up to run the Robotics stuff. You can access the ADCs, servos, 
etc. through the robot interface.

When I teach my Embedded Linux class I would also like my students to 
access the ADCs, PWM, etc in the Linux way.  

*How do I configure the Blue to boot up in "Embedded Linux" mode rather 
than "Robot Linux" mode*?

--Mark


On Wednesday, August 2, 2017 at 11:15:40 AM UTC-4, Mark A. Yoder wrote:
>
> It sounds like I can either have a Blue that boots as a robot, or boots as 
> an embedded processor, but not both at the same time.
> I need to see what it would take to remove the ADC from the robots control.
>
> --Mark
>
> On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote:
>>
>> I have lived on BBB + Robotics Cape in James' world for some time. While 
>> I haven't done this with a Blue, I suspect what I did can work there too. I 
>> did do his installation (for a Rev C BBB and a Rev D Robotics Cape). With 
>> Robert's help I put the Capemgr back in the DTs and added the capemgr 
>> partno boot line for BB-ADC.  This seems to be a workable combination of 
>> the two worlds. My premise is that I don't try to do both at once.  That 
>> is, I don't run any of the rc_* apps or services while trying to read the 
>> ADCs from /sys/bus/iio. So far it seems to work for me.
>> Hugh
>>
>> On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:
>>
>>> Yup, this is the Blue.
>>> In there short term is there an easy way to turn off the robotics stuff 
>>> and get easy access to the analog in?
>>>
>>> In the long term, what will it take to convert James' robot stuff to 
>>> libiio?  I might take a shot at it if it isn't too hard.
>>>
>>> --Mark
>>>
>>> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:

 On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
 wrote: 
 > How do I read AIN on the latest images?  I don't know where to find 
 it in 
 > /sys/ 

 Hi Mark, 

 This is with the Blue right? 

 James' got the ADC tied up in mmap for the Robotic's cape library.. 


 https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c
  

 We need to convert his library to use libiio, then we can just enable 
 the ADC's as an iio device and share usage with the library.. 

 https://analogdevicesinc.github.io/libiio/ 

 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: [beagleboard] TPS65217C in BBB board

2017-08-03 Thread Gerald Coley
They come up in a default mode. No need for the AM3358 to do anything. Check 
the datasheet of the TPS65217 for more information.

Gerald


From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of huole.z...@gmail.com
Sent: Thursday, August 3, 2017 2:47 AM
To: BeagleBoard 
Subject: [beagleboard] TPS65217C in BBB board

Hi experts,

I've a Beaglebone black board, TPS65217C power management IC is used on it. My 
question is about the I2C interface of it.

By default, all power outputs of TPS65217 are off, so there is no 1.1V, 1.5V, 
1.8V, etc. which means AM335x needs to configure the I2C interface firstly to 
enable these power rails, while AM335x is off at this moment, it looks like a 
endless loop.

Any comments?

Thanks
Chris
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/589dc3e8-c334-40a6-9965-2640f547e08a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7291191d115d4a1d928f8710fd2d4a3f%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] TPS65217C in BBB board

2017-08-03 Thread huole . zhao
Hi experts,

I've a Beaglebone black board, TPS65217C power management IC is used on it. 
My question is about the I2C interface of it.

By default, all power outputs of TPS65217 are off, so there is no 1.1V, 
1.5V, 1.8V, etc. which means AM335x needs to configure the I2C interface 
firstly to enable these power rails, while AM335x is off at this moment, it 
looks like a endless loop.

Any comments?

Thanks
Chris

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/589dc3e8-c334-40a6-9965-2640f547e08a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: JTAG beagle bone black with buspirate and openocd

2017-08-03 Thread Jeff Andich
If there's a reason why you need to stick with openocd, are there other 
forums, http://openocd.org/discussion/forum/, where you can post up on the 
messages you are seeing?

I'm currently attempting JTAG debugging of the Linux SPL on the 
am572xEVM/BeagleBoard-X15 platform using CCS 7.2 (running under an Ubuntu 
VM) and XDS100V2.

Even though I'm a newbie, if you were to use CCS7 + the Blackhawk debugger 
(XDS100V2), maybe people in my shoes on this forum would have already 
encountered some errors that you see, and potentially be able to provide 
tips..

CCS 7 is free and XDS100V2 is like $100.00. 

Plus in addition to this site, there's a CCS forum on TI e2e, 
https://e2e.ti.com/support/development_tools/code_composer_studio/f/81?tisearch=e2e-sitesearch=code%20composer%20studio%20forum,

But last I checked, for Linux they support TI SDK images and not 
BeagleBoard.org images..
But if you're just trying to get started with CCS and XDS100V2, they may be 
able to walk you through
some of your issues.




On Tuesday, August 1, 2017 at 12:15:06 AM UTC-5, Jitendriya Parida wrote:

> Hello
>
> I am very new to JTAG and i am trying to do the setup for jtag in 
> beaglebone black(BBB) rev c board using buspirate(BP) and openocd.
> I have installed the P2 header in BBB manually. I have connected the BBB 
> and BP as follows
>
> JTAG
>
> BP
>
> BBB
>
> TMS
>
> CS
>
> P2(1) P2 header pin 1
>
> TDI
>
> MOSI
>
> P2(3)
>
> VTREF
>
> VPU
>
> P2(5)
>
> TDO
>
> MISO
>
> P2(7)
>
> TCK
>
> CLK
>
> P2(11)
>
> TRST
>
> AUX
>
> P2(2)
>
> GRND
>
> GND
>
> P2(10)
>
>
>
> I am using my user configuration file(BP_userconfig.cfg) for openocd which 
> has following content.
>
> source [find interface/buspirate.cfg]
>
> buspirate_vreg 0
> buspirate_mode open-drain
> buspirate_pullup 1
> reset_config srst_only
> buspirate_port /dev/ttyUSB0
>
> source [find board/ti_beaglebone_black.cfg]
>
> Now while running the command *sudo openocd -f  BP_userconfig.cfg* I am 
> getting following error.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *lenova@lenova-ThinkPad-T410:~/jiten/JTAG$ sudo openocd -f 
> BP_userconfig.cfg Open On-Chip Debugger 0.10.0+dev-00167-g29cfe9c 
> (2017-07-20-14:08) Licensed under GNU GPL v2 For bug reports, read 
> http://openocd.org/doc/doxygen/bugs.html 
>  Warn : Adapter driver 
> 'buspirate' did not declare which transports it allows; assuming legacy 
> JTAG-only Info : only one transport option; autoselect 'jtag' srst_only 
> separate srst_gates_jtag srst_open_drain connect_deassert_srst 
> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain 
> connect_deassert_srst adapter speed: 1000 kHz trst_and_srst separate 
> srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst Info : 
> Buspirate Interface ready! Info : This adapter doesn't support configurable 
> speed Info : JTAG tap: am335x.jrc tap/device found: 0x2b94402f (mfg: 0x017 
> (Texas Instruments), part: 0xb944, ver: 0x2) Info : JTAG tap: am335x.dap 
> enabled Error: JTAG-DP STICKY ERROR Error: Could not initialize the APB-AP 
> *Does 
> anyone have any idea about this error? and do i need to do anything else in 
> BBB apart from installing P2 header?
> Please let me know if i am doing anything wrong.
>
> Thanks in advance.
>
> Regards
> jitendriya
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/252cb0cc-d6d5-45ea-b3b0-13458babf9ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: BeagleBone Blue; Pinout diagram / System Reference Manual ?

2017-08-03 Thread Jason Kridner


> On Aug 2, 2017, at 10:58 AM, Mark A. Yoder  wrote:
> 
> Wow, that's a great diagram.  It makes it very clear what pins are where.
> 
> --Mark
> 
>> On Tuesday, August 1, 2017 at 8:15:30 PM UTC-4, nms...@gmail.com wrote:

Fantastic. Can we get this on the wiki?


>> 
>> 
>>> On Sunday, July 9, 2017 at 4:23:09 AM UTC+1, Jeff Albrecht wrote:
>>> I'm looking for a detailed pinout of the BBBlue. Hopefully similar to this, 
>>> or the many similar ones, for the BBB.
>>> 
>>> 
>>> 
>>> The BBBlue FAQ has a Pinouts section with this picture. For instance I 
>>> found the SPI connector but I don't know the pin numbers and pin names on 
>>> the connector to hook up the hardware.
>>> 
>>> 
>>> 
>>> I found Pin Multiplexing on the Strasown Design site. It's getting closer 
>>> but not a definitive reference for me. Perhaps this could be added to the 
>>> Pinouts of the BBBlue FAQ.
>>> 
>>> I have a 6-wire JST-SH connector. Not sure where pin 1 is on the connector 
>>> or which pin is SCLK, MOSI, MIS0 SS* etc...
>>> 
>>> Does a detailed pinout for the BBBlue exist?
>>> 
>>> The BeagleBone Blue page refers to the System Reference Manual on the 
>>> github page but I'm not finding it. Does the System Reference Manual for 
>>> the 'blue exist?
>>> 
>>> Browse the BeagleBone Blue Github page to find all available hardware 
>>> specifications such as:
>>> Bill of materials
>>> PCB source files
>>> Manufacturing files
>>> Schematic (PDF and source)
>>> System Reference Manual
>>>  
>>> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/dafcb626-f17e-455b-af9a-779a5329c672%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/A7E3B890-4094-4ADA-9C7B-077C302E5AFE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] New DLP pico projector from TI

2017-08-03 Thread Bill Barnett
See:
http://linuxgizmos.com/tis-99-dlp-pico-projector-board-connects-to-beaglebone-black/

for $99 a DLP cape for the Beaglebone Black.


-- 

Bill Barnett

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAP4vyaecyjRQNwTqzRVwZwm%3DXdSma4tAiGUMZW%3DYbj34jWLXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: JTAG beagle bone black with buspirate and openocd

2017-08-03 Thread Jitendriya Parida
Hello

I would really like any kind of suggestion.
I am stuck at this error for last quiet a days.

any idea please??

On Tuesday, August 1, 2017 at 10:45:06 AM UTC+5:30, Jitendriya Parida wrote:
>
> Hello
>
> I am very new to JTAG and i am trying to do the setup for jtag in 
> beaglebone black(BBB) rev c board using buspirate(BP) and openocd.
> I have installed the P2 header in BBB manually. I have connected the BBB 
> and BP as follows
>
> JTAG
>
> BP
>
> BBB
>
> TMS
>
> CS
>
> P2(1) P2 header pin 1
>
> TDI
>
> MOSI
>
> P2(3)
>
> VTREF
>
> VPU
>
> P2(5)
>
> TDO
>
> MISO
>
> P2(7)
>
> TCK
>
> CLK
>
> P2(11)
>
> TRST
>
> AUX
>
> P2(2)
>
> GRND
>
> GND
>
> P2(10)
>
>
>
> I am using my user configuration file(BP_userconfig.cfg) for openocd which 
> has following content.
>
> source [find interface/buspirate.cfg]
>
> buspirate_vreg 0
> buspirate_mode open-drain
> buspirate_pullup 1
> reset_config srst_only
> buspirate_port /dev/ttyUSB0
>
> source [find board/ti_beaglebone_black.cfg]
>
> Now while running the command *sudo openocd -f  BP_userconfig.cfg* I am 
> getting following error.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *lenova@lenova-ThinkPad-T410:~/jiten/JTAG$ sudo openocd -f 
> BP_userconfig.cfg Open On-Chip Debugger 0.10.0+dev-00167-g29cfe9c 
> (2017-07-20-14:08) Licensed under GNU GPL v2 For bug reports, read 
> http://openocd.org/doc/doxygen/bugs.html 
>  Warn : Adapter driver 
> 'buspirate' did not declare which transports it allows; assuming legacy 
> JTAG-only Info : only one transport option; autoselect 'jtag' srst_only 
> separate srst_gates_jtag srst_open_drain connect_deassert_srst 
> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain 
> connect_deassert_srst adapter speed: 1000 kHz trst_and_srst separate 
> srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst Info : 
> Buspirate Interface ready! Info : This adapter doesn't support configurable 
> speed Info : JTAG tap: am335x.jrc tap/device found: 0x2b94402f (mfg: 0x017 
> (Texas Instruments), part: 0xb944, ver: 0x2) Info : JTAG tap: am335x.dap 
> enabled Error: JTAG-DP STICKY ERROR Error: Could not initialize the APB-AP 
> *Does 
> anyone have any idea about this error? and do i need to do anything else in 
> BBB apart from installing P2 header?
> Please let me know if i am doing anything wrong.
>
> Thanks in advance.
>
> Regards
> jitendriya
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e8b15735-9efe-40c9-bc6f-c2ecf5776eb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.