[beagleboard] Re: Graphical Desktop with keyboard & display

[Tarmo]

Hi Bernard

On Monday, 15 June 2020 00:13:12 UTC+3, Bernard Fischer wrote:
>
> I have vnc working fine with a GUI on my BB AI.  But if it plug in a 
> display and keyboard/mouse i get a text terminal and can't start up a 
> graphical desktop.  startx is not found.
>
> What packages do I need to install for that? If it works over VNC why 
> doesn't it work directly?
>

One of the easiest ways to get started with graphical desktops in Debian is 
to install a "task-XXX-desktop" metapackage for your favourite desktop 
environment XXX, which pulls in the whole kaboodle via dependencies. It 
will probably include some packages which you don't want, so feel free to 
prune later.

E.g. for installing the light-weight LXDE environment you'd do this:

$ sudo apt install task-lxde-desktop

The reason you don't see a graphical environment when plugging in a monitor 
is you don't have a display manager installed (
https://wiki.debian.org/DisplayManager). The task you install will include 
a "friendly" display manager, e.g. in case of LXDE it'll be the lightdm. 
You might need to restart the board (or at least the display manager 
service) after you've plugged in a monitor post-boot.

--
Kind regards,
Tarmo

-- 
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/1abc43d9-631e-4360-ba5e-d39838bcab4bo%40googlegroups.com.

Re: [beagleboard] Re: Graphical Desktop with keyboard & display

[evilwulfie]

On 6/15/2020 6:29 AM, Tarmo wrote:

Hi Bernard

On Monday, 15 June 2020 00:13:12 UTC+3, Bernard Fischer wrote:

I have vnc working fine with a GUI on my BB AI.  But if it plug in
a display and keyboard/mouse i get a text terminal and can't start
up a graphical desktop.  startx is not found.

What packages do I need to install for that? If it works over VNC
why doesn't it work directly?


One of the easiest ways to get started with graphical desktops in 
Debian is to install a "task-XXX-desktop" metapackage for your 
favourite desktop environment XXX, which pulls in the whole kaboodle 
via dependencies. It will probably include some packages which you 
don't want, so feel free to prune later.


E.g. for installing the light-weight LXDE environment you'd do this:

$ sudo apt install task-lxde-desktop

The reason you don't see a graphical environment when plugging in a 
monitor is you don't have a display manager installed 
(https://wiki.debian.org/DisplayManager). The task you install will 
include a "friendly" display manager, e.g. in case of LXDE it'll be 
the lightdm. You might need to restart the board (or at least the 
display manager service) after you've plugged in a monitor post-boot.


--
Kind regards,
Tarmo


I am fairly sure he has a display manager installed as VNC will not function
without one.




--
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/1abc43d9-631e-4360-ba5e-d39838bcab4bo%40googlegroups.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/f960cd56-d780-e32f-8e63-f94943b6a451%40gmail.com.

[beagleboard] B.B.B. turn off automatically

[saeidi . 01 . majid]

Hi
My BeagleBone turn off automatically after 5 or 6 hours, whats the problem?
Do you have any idea?
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/297df8a6-aa14-4664-9e24-4de1cd8fe603o%40googlegroups.com.

[beagleboard] Re: B.B.B. turn off automatically

[graham]

Could be old software. Some earlier versions of Debian did that.
What version software are you using?

Could be a weak power supply.
Is your power supply good enough to power the peak currents for the 
BeagleBone at all times?

Are you using a PocketBeagle, and not a BeagleBone?
The PocketBeagles do that, if powered from the external power input.

===



On Monday, June 15, 2020 at 9:04:59 AM UTC-5, saeidi...@gmail.com wrote:
>
> Hi
> My BeagleBone turn off automatically after 5 or 6 hours, whats the problem?
> Do you have any idea?
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6b900d01-ccde-40b3-a785-8fbfac55ee08o%40googlegroups.com.

[beagleboard] Re: Graphical Desktop with keyboard & display

[Dennis Lee Bieber]

On Sun, 14 Jun 2020 14:13:12 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Bernard Fischer
 wrote:

>I have vnc working fine with a GUI on my BB AI.  But if it plug in a 
>display and keyboard/mouse i get a text terminal and can't start up a 
>graphical desktop.  startx is not found.
>

Off hand, that behavior sounds much like you have X-clients installed,
but not an X-server; the VNC software on the Beagle may be acting as the
server when it is running. cf:
https://www.debian.org/doc/manuals/debian-reference/ch07.en.html

>What packages do I need to install for that? If it works over VNC why 
>doesn't it work directly?

See above answer... Your X clients (applications) are sending drawing
commands to the VNC server on the Beagle, which relays them to the VNC
client on the other computer for display. Note: the desktop manager is a
/client/ application. {Note: the usage of server/client WRT VNC is opposite
of the usage for pure X Window. In X, the /display/ doing the rendering is
the server, clients send commands to the server over the network -- But
with VNC, the software on the Beagle is intercepting the commands and
reformulating them for VNC network protocol}

On a BBB with IoT image (and stripping out a lot of extraneous
packages):

debian@beaglebone:~$ apt search "x server"
Sorting... Done
Full Text Search... Done
tigervnc-xorg-extension/stable 1.9.0+dfsg-3+deb10u1 armhf
  Virtual network computing X server extension

weirdx/stable 1.0.32-7 all
  X server in Java

x11-xserver-utils/stable 7.7+8 armhf
  X server utilities

xdmx/stable 2:1.20.4-1 armhf
  distributed multihead X server

xfonts-biznet-100dpi/stable 3.0.0-26 all
  100 dpi BIZNET ISO-8859-2 fonts for X servers

xfonts-biznet-75dpi/stable 3.0.0-26 all
  75 dpi BIZNET ISO-8859-2 fonts for X servers

xfonts-biznet-base/stable 3.0.0-26 all
  Standard BIZNET ISO-8859-2 fonts for X servers

xinit/stable 1.4.0-1 armhf
  X server initialisation tool

xnest/stable 2:1.20.4-1 armhf
  Nested X server

xserver-common/stable 2:1.20.4-1 all
  common files used by various X servers

xserver-xephyr/stable 2:1.20.4-1 armhf
  nested X server

xserver-xorg/stable 1:7.7+19 armhf
  X.Org X server

xserver-xorg-core/stable 2:1.20.4-1 armhf
  Xorg X server - core server

xserver-xorg-input-all/stable 1:7.7+19 armhf
  X.Org X server -- input driver metapackage

xserver-xorg-video-fbdev/stable 1:0.5.0-1 armhf
  X.Org X server -- fbdev display driver

xvfb/stable 2:1.20.4-1 armhf
  Virtual Framebuffer 'fake' X server

xwayland/stable 2:1.20.4-1 armhf
  Xwayland X server





-- 
Dennis L Bieber

-- 
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/da2fefh48gecre7h1nm7dbtj9viao6csqm%404ax.com.

[beagleboard] PRU IEP timers non-responsive

[Fred Frey]

Hello

I'm trying to write a simple program to test the IEP timers. Ideally I'd 
like to be able to poll the timer and get an unsigned long value back, but 
for this test, I followed what I read in this post:

https://www.element14.com/community/community/designcenter/single-board-computers/next-genbeaglebone/blog/2019/08/12/beaglebone-pru-timer-functionality

With a few minor changes -- I provide a different GPIO pin, made it loop 
forever, and made the frequency for the square wave ~2kHz.

I also have a different way of configuring the IEP/INTC. I manually defined 
the addresses:

#define IEP_HOME((volatile unsigned long*)0x2E000)
#define TMR_GLOBAL_CFG (*(IEP_HOME+0x00))
#define TMR_GLOBAL_STATUS   (*(IEP_HOME+0x04))
#define TMR_COMPEN (*(IEP_HOME+0x08))
#define TMR_COUNT(*(IEP_HOME+0x0C))
#define TMR_CMP0   (*(IEP_HOME+0x48))
#define TMR_CMP_STATUS (*(IEP_HOME+0x44))
#define TMR_CMP_CFG   (*(IEP_HOME+0x40))

...

#define INTC_HOME   ((volatile unsigned long*)(0x2))

#define INTC_SECR0  (*(INTC_HOME+0x280))
#define INTC_SECR1  (*(INTC_HOME+0x284))


And I configured them like so:

TMR_GLOBAL_CFG &= 0xfffe; // disable timer

TMR_COUNT = 0x0; // reset timer

TMR_CMP_STATUS = 0xff; // clear compare status

TMR_CMP0 = 10; // 0.0025 SEC @ 200 MHz

TMR_COMPEN &= 0xff00;  // set compensation to 0

TMR_CMP_CFG &= 0x03; // enable cmp0 and reset on event

INTC_SECR0 = 0x;
INTC_SECR1 = 0x;

TMR_GLOBAL_CFG = 0x11; // enable counter


When I read from TMR_COUNT, it's always 0, and the interrupt never fires. 
What am I missing?

Thanks,
Fred

-- 
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/f0094b81-8d47-4631-91c5-b9f93e2888a5o%40googlegroups.com.

[beagleboard] Re: B.B.B. turn off automatically

[KenUnix]

Are you running on an external 5 volt power supply and not just the USB 
cable to your P.C.?

Type in the following two commands:

cat /etc/dogtag

uname -a


Ken

-- 
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/c026bd93-5bb1-425c-ae80-455c024c05b5o%40googlegroups.com.

[beagleboard] Voltage of Output Pins

[Nathan Smith]

Is anybody familiar with the voltage of the output pins?  I looked through 
the technical reference sheet, but I could not find this information. 

Thank you!

-- 
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/2d2e0736-ae07-46bd-b284-34f8b0e24a8do%40googlegroups.com.

[beagleboard] Re: Voltage of Output Pins

[Dennis Lee Bieber]

On Mon, 15 Jun 2020 09:10:27 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Nathan Smith
 wrote:

>Is anybody familiar with the voltage of the output pins?  I looked through 
>the technical reference sheet, but I could not find this information. 
>

https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual#beaglebone-black-features-and-specification
"""
Expansion Connectors

Power 5V, 3.3V , VDD_ADC(1.8V)
3.3V I/O on all signals
McASP0, SPI1, I2C, GPIO(69 max), LCD, GPMC, MMC1, MMC2, 7
AIN (1.8V MAX), 4 Timers, 4 Serial Ports, CAN0,
EHRPWM(0,2),XDMA Interrupt, Power button, Expansion Board ID (Up to 4 can
be stacked)
"""

The chipset used for the various beagles is 3.3V based (analog inputs
are limited to 1.8V). Presuming the old 30/70% thresholds for CMOS signals,
LOW is 0.0..1.0, HIGH is 2.3..3.3, 1.0..2.3 is indeterminate (the chips
should be outputting close to the 0.0 and 3.3 levels, but any input device
should accept the range).


-- 
Dennis L Bieber

-- 
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/b7dfeflt418jupqj0b51j4pfcch7li1ua3%404ax.com.

[beagleboard] Re: PocketScroller pin out

[Mark A. Yoder]

Dan:
  Thanks for the help.  It turns out the panel was plugged into connector 
J6, rather than J1.  Once I figure that out things made much more sense.

--Mark

The other things I learned is don't leave PRU 1 running while trying to 
debug PRU 0.

On Sunday, June 14, 2020 at 4:02:18 PM UTC-4, Daniel Kulp wrote:
>
>
> The newer pocketscrollers are use a slightly different pinout than the 
> originals.  The OE line was moved to a pin that could use the PWM hardware 
> in hopes of updating the PRU code to use that, but I never got around to 
> doing that. 
>
> If you are using one of the newer PocketScrollers with the OLED 
> header/buttons, then you can SSH into the FPP instance and look in 
> /home/fpp/media/tmp/panels and there is a JSON file that describes the pins 
> the various outputs use.  If using the older PocketScroller without the 
> eeprom, you would look in /opt/fpp/capes/pb/panels/PocketScroller.json.
>
> Dan
>
>
> On Friday, June 12, 2020 at 4:39:13 PM UTC-4, Mark A. Yoder wrote:
>>
>> I have a PocketScroller on my Pocket Beagle.  In the past I've had no 
>> trouble running fpp on it.
>>
>> Now I want to drive it directly from by own PRU code[1].  The code worked 
>> fine when I hand wired the P10 panel to my Pocket Beagle, but I don't know 
>> how things are attached internally so the
>> code doesn't work.  
>>
>> Is there a schematic I could reference?
>>
>> Thanks...
>>
>> --Mark
>>
>> [1] 
>> https://github.com/MarkAYoder/PRUCookbook/blob/master/docs/05blocks/code/rgb1.c
>>
>

-- 
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/3da41fc8-ad21-43be-8369-34428b525955o%40googlegroups.com.

[beagleboard] Problems Reconfiguring GPIO's

[P B]

Greetings,

I am working on developing a new piece of equipment using the BBB as the 
controller.

One aspect of the project is control of an inlet and outlet pump from a 
tank.  Time sensitivity is not critical.

I am looking to use
P8-11 (GPIO 45) as pulldown input - Program man/auto
P8-12 (GPIO 44) as pulldown input - Pump 1 - man on/off
P8-14 (GPIO 26) as pulldown input - Pump 2 - man on/off
P8-15 (GPIO 47) as pulldown input - Pump 2 start switch
P8-16 (GPIO 46) as pulldown input - Pump 1 Stop switch
P8-17 (GPIO 27) as pulldown input - Pump 2 Stop switch
P8-18 (GPIO 65) as pulldown input - Pump 1 Start switch

Fortunately, pulldown input is the default state of each of those pins.

Unfortunately, I also want
P9-12 (GPIO 60) as pulldown output to turn on pump 1 using a relay, where 
P9-12's default state is pullup input, and
P9-15 (GPIO 48) as pulldown output to turn on pump 2 using a relay, where 
P9-15's default state is pulldown input.

I have been trying to work through RCN's dtb-rebuilder with Derek Molloy's 
book to accomplish this.  

But I have not impacted this default state.

I am using Kenerl r.19.94-ti-r42.

I have captured my boot sequence using a serial cable through putty:

uboot_overlays: [uboot-base-dtb = am335x-boneblack-uboot-univ.dtb]...
the seqeunce confirms it switched to the above, then loads with 162266 
bytes read

am335x-boneblack-uboot-univ.dtb includes 
1) am33xx.dtsi, which appears to set on chip GPIO's,
2) am335x-bone-common.dtsi, which appears to only interact with P9-19 & 
P9-20 in terms of GPIO, and
3) am335x-bone-common-univ.dtsi


So looking at P9-12 in am335x-bone-common-univ.dtsi:

Line 713 of am335x-bone-common-univ.dtsi begins the definitions of Gpio on 
P9-12
/* P9_12 (ZCZ ball U18) gpio1_28 */
P9_12_default_pin: pinmux_P9_12_default_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */
P9_12_gpio_pin: pinmux_P9_12_gpio_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT | INPUT_EN | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */
P9_12_gpio_pu_pin: pinmux_P9_12_gpio_pu_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */
P9_12_gpio_pd_pin: pinmux_P9_12_gpio_pd_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLDOWN | INPUT_EN | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */
P9_12_gpio_input_pin: pinmux_P9_12_gpio_input_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_INPUT | MUX_MODE7) >; }; /* gpmc_be1n.gpio1_28 */

I have tried modifying the lines above with no success
1)
P9_12_gpio_pd_pin: pinmux_P9_12_gpio_pd_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLDOWN_EN | INPUT | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */

and

2)
P9_12_gpio_pd_pin: pinmux_P9_12_gpio_pd_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLDOWN_EN | MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */

and
3)
P9_12_gpio_pd_pin: pinmux_P9_12_gpio_pd_pin { pinctrl-single,pins = <
AM33XX_IOPAD(0x0878, PIN_OUTPUT_PULLDOWN| MUX_MODE7) >; }; /* 
gpmc_be1n.gpio1_28 */

Line 2049 starts the next section which appears to only define the pinctrl 
states
/* P9_12 (ZCZ ball U18) */
P9_12_pinmux {
compatible = "bone-pinmux-helper";
status = "okay";
pinctrl-names = "default", "gpio", "gpio_pu", "gpio_pd", "gpio_input";
pinctrl-0 = <&P9_12_default_pin>;
pinctrl-1 = <&P9_12_gpio_pin>;
pinctrl-2 = <&P9_12_gpio_pu_pin>;
pinctrl-3 = <&P9_12_gpio_pd_pin>;
pinctrl-4 = <&P9_12_gpio_input_pin>;
};

I have not played with these.

Finally, the last place it appears to configure P9-15 starts on Line 2777
P9_12 {
gpio-name = "P9_12";
gpio = <&gpio1 28 0>;
input;
dir-changeable;
};

I have tried a few modification here with no success such as

P9_12 {
gpio-name = "P9_12";
gpio = <&gpio1 28 3>;
output;
pulldown;
};


I nano'ed, modified and saved the am335x-bone-common-univ.dtsi file, used 
the dtb-rebuilder make all command, backed up the old binary file 
am335x-boneblack-uboot-univ.dtb_BACKUP and replaced it with the new 
am335x-boneblack-uboot-univ.dtb.

And yes I messed it up a couple times and had to completely rebuild the 
BBB's loaded image, updates, upgrades, etc...  Lots of fun.

I have not seen any change in the default state of P9-12 from pullup input 
as checked using config-pin query.

Can anyone redirect me to some examples, or provide a some tips, or simply 
tell me I'm off my rocker and nowhere close to where I need to be?  

I'm a little stuck here.

-- 
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/8646c994-c174-4b25-82cb-c3ab34ac2be7o%40googlegroups.com.

[beagleboard] Re: Voltage of Output Pins

[Nathan Smith]

Thank you so much

On Monday, June 15, 2020 at 1:57:58 PM UTC-4, Dennis Bieber wrote:
>
> On Mon, 15 Jun 2020 09:10:27 -0700 (PDT), in 
> gmane.comp.hardware.beagleboard.user Nathan Smith 
> > wrote: 
>
> >Is anybody familiar with the voltage of the output pins?  I looked 
> through 
> >the technical reference sheet, but I could not find this information. 
> > 
>
>
> https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual#beaglebone-black-features-and-specification
>  
> """ 
> Expansion Connectors 
>  
> Power 5V, 3.3V , VDD_ADC(1.8V) 
> 3.3V I/O on all signals 
> McASP0, SPI1, I2C, GPIO(69 max), LCD, GPMC, MMC1, MMC2, 7 
> AIN (1.8V MAX), 4 Timers, 4 Serial Ports, CAN0, 
> EHRPWM(0,2),XDMA Interrupt, Power button, Expansion Board ID (Up to 4 can 
> be stacked) 
> """ 
>
> The chipset used for the various beagles is 3.3V based (analog 
> inputs 
> are limited to 1.8V). Presuming the old 30/70% thresholds for CMOS 
> signals, 
> LOW is 0.0..1.0, HIGH is 2.3..3.3, 1.0..2.3 is indeterminate (the chips 
> should be outputting close to the 0.0 and 3.3 levels, but any input device 
> should accept the range). 
>
>
> -- 
> Dennis L Bieber 
>
>

-- 
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/7e13593b-759d-4d3d-b24e-06222c8a4955o%40googlegroups.com.

[beagleboard] Re: requesting information on pcb files for beaglebone black and beaglebone ai

[jimvr]

Jason,

Well, I was wrong, the dsn and brd files that are here, are not matching up.
https://github.com/beagleboard/beaglebone-ai/tree/master/HW 

I do see the A2 proposed changes, and I understand that the board files for 
that is not  yet available.

Can you confirm that the design set that is up in the github, match?  It 
could be just our conversion went wrong, and we need to figure that out.  
The schematic seems correct to the PDF that we have from the same github.

On Saturday, June 13, 2020 at 1:29:30 PM UTC-7 jimvr wrote:

> Jason,
>
> One of our friends has Allegro and we were able to convert, so good there. 
> However, I noted that the files on GitHub are for A1, is there a board set 
> package for A2, or errata from A1 to A2 that can be shared so that we can 
> be sure to understand what was left off?
>
> I am having some IO pin issues right now, and it just seems like my A1 
> board is missing a signal or two to the cape header.  Plus I can see that 
> the JTAG port is not right, two wires perhaps needed?
>
> And if you are happy with this, I can send you the Altium project when 
> done, and you can post that up?
>
> Share?
>
> On Saturday, June 13, 2020 at 9:01:41 AM UTC-7 jimvr wrote:
>
>> Jason,
>>
>> We also are interested in the Altium file export for the BBAI Rev A2, if 
>> you can do that export.  According to what I read, there are two methods 
>> from this Altium post:  
>> https://www.altium.com/documentation/altium-designer/allegro-import-ad
>>
>> *Allegro Binary PCB Design Files*
>>
>> The Import Wizard can directly import and translate Allegro PCB files 
>> (*.brd) to Altium Designer PCB files (*.PcbDoc) when the Wizard has local 
>> access to an Allegro PCB editor installation – that is, when a licensed 
>> copy of Allegro PCB is installed on the same machine as Altium Designer.
>>
>> The Wizard uses Allegro’s included file conversion capabilities to 
>> configure the design data for processing by the importer.
>>
>> *Allegro ASCII Extracted Design Files*
>>
>> Altium Designer’s Import Wizard can import and translate ASCII-based 
>> Allegro PCB files (*.alg) that have been created from a licensed Allegro 
>> PCB installation. The ASCII PCB design files are extracted from native 
>> Allegro PCB files (*.brd) by Allegro’s included file converter 
>> (extracta.exe), which is called by a special batch file supplied with 
>> Altium Designer.
>>
>> Since Allegro binary-to-ASCII conversion is a self-contained file 
>> process, the Allegro installation does not need to be accessed by Altium 
>> Designer. The Allegro installation can be on any machine, and is only used 
>> to generate suitable ASCII PCB design files.
>> We have many Altium seats here, if you wanted to "use" a license to try 
>> the first method, I can create a temporary login to our license for Altium, 
>> however you will need to download and install Altium on the same machine.
>> If you can create the .alg file set, that may help us that want to view 
>> the board in Altium.  Altium has no problem with the schematic, that was a 
>> native import within Altium.
>>
>> Please let us know!  You guys did a great job with that board design, and 
>> the support from your team, stellar all around.  Thanks.
>>
>> On Thursday, April 23, 2020 at 9:32:41 AM UTC-7 Jason Kridner wrote:
>>
>>> On Wed, Apr 22, 2020 at 10:35 AM Ramakrishna Bachimanchi <
>>> bach...@jlab.org> wrote:
>>>
 Hello,
 my name is Rama Bachimanchi and I am an electrical engineer working at 
 Jefferson Lab (non-profit research organization). I have come across the 
 amazing work you guys are doing and was looking into possibly modifying 
 one 
 of your designs to replace an obsolete ioc we are using (it's a kontron 
 pc/104 no longer in production). I was able to import the schematic into 
 Altium, but not the pcb design files. I am getting an error when tried to 
 view the files using the free allegro pcb viewer. Would it be possible to 
 update the files and also upload the ascii file, so that we can import 
 this 
 into altium. We are planning to replace the expansion connectors with 
 pc/104 connector. If we get to work and finish the design, we will most 
 likely share it with you(not sure, if this is useful for the community). 
 Please let me know

>>>
>>>
>>> I'm not sure what ASCII file is needed. If I knew, I'd be happy to 
>>> export it.
>>>
>>> For conversion to KiCAD, I created a cds2f text file: 
>>> https://github.com/beagleboard/beaglebone-ai/blob/master/HW/cds2f_BeagleBone-AI.txt
>>>
>>> When the KiCAD version is available, you might find it easier to import 
>>> that into Altium:
>>> https://www.altium.com/solution/kicad-pcb-design-software-free-download
>>>
>>>  
>>>

 Thanks,
 Rama Bachimanchi


>>>
>>> -- 
>>> https://beagleboard.org/about - a 501c3 non-profit educating around 
>>> open hardware computing
>>>
>>

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