[beagleboard] BBAI and HW MCSPI3 ch 0 (linux spidev 2.0) custom usage in Linux

2020-07-19 Thread Raul Rathmann 

Hi,

I've got a custom board where I need/want to use the MCSPI3 CS0, CS2 and 
CS3 hw lines for SPI.

When I configure and enable mcspi3 in a custom DTS for the Linux image, 
with  I get the following message viewable with dmesg:
[ 1.189920] omap2_mcspi 480b8000.spi: chipselect 0 already in use
[ 1.196085] spi_master spi2: spi_device register error 
/ocp/spi@480b8000/channel@0
[ 1.203721] spi_master spi2: Failed to create SPI device for 
/ocp/spi@480b8000/channel@0

So, channel 0 seems to be conflicting with some other driver or usage.

I finally figured out that the "am5729-beagleboneai.dts" file has a 
reference to mcspi3:
&mcspi3 {
status = "okay";
ti,pindir-d0-out-d1-in;

sn65hvs882: sn65hvs882@0 {
compatible = "pisosr-gpio";
gpio-controller;
#gpio-cells = <2>;

reg = <0>;
spi-max-frequency = <100>;
spi-cpol;
};
};

My question is can I disable/override this usage?

I don't know the system purpose of the "pisosr-gpio"/sn65hvs882 device and 
what the effect will be if Linux access is disabled. Since I'll have a 
custom device on linux spidev2.0, I don't want some other part of the 
system trying to access that SPI bus/channel and causing problems with my 
device.

Thanks for any insights.

Raul


-- 
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/5451426c-8c64-44df-87f5-c94eea5909e4n%40googlegroups.com.

[beagleboard] BBW not booting when serial to USB cable connected

2020-07-19 Thread Rishabh 
Hi,

I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
output to my terminal in Ubuntu. I am doing this to view U-Boot.

Whenever the serial to USB is connected, the board doesn't boot up.  

When the serial to USB cable is connected and I run 

picocom -b 115200 /dev/ttyUSB0 

the terminal waits for data on the port. As soon as I try to power up the 
board with the micro-USB cable, I get a fatal error and the serial port 
connection gets lost.

picocom v2.2

port is: /dev/ttyUSB0
flowcontrol: none
baudrate is: 115200
parity is  : none
databits are   : 8
stopbits are   : 1
escape is  : C-a
local echo is  : no
noinit is  : no
noreset is : no
nolock is  : no
send_cmd is: sz -vv
receive_cmd is : rz -vv -E
imap is: 
omap is: 
emap is: crcrlf,delbs,

Type [C-a] [C-h] to see available commands

Terminal ready

FATAL: term closed


The board boots up only when the serial to USB cable is disconnected from 
the PC.

I tried to connect the serial to USB after powering up the board and that 
powers off the board. I am not sure why but the two connections (serial to 
USB and micro-USB power cable) seem to be mutually exclusive. I would 
appreciate any suggestions on how to resolve this issue.

Thanks,
Rishabh

-- 
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/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%40googlegroups.com.

[beagleboard] Problem while booting on self-designed custom board using AM5728

2020-07-19 Thread nguyenhatrung411 
Hello, I have a problem with my self-design custom board using AM5728. My 
board design followed fully design of beaglebone X15.

i am using Processor  SDK for AM57x Sitara processor (
https://www.ti.com/tool/PROCESSOR-SDK-AM57X). After starting kernel, the 
problem happened and it stopped

My logfile from starting booting to the point where problem happened is 
shown below:


*U-Boot SPL 2019.01-g333c3e72d3 (Apr 20 2020 - 04:15:00 +)*
*DRA752-GP ES2.0*
*** Unable to read file dra7-ipu1-fw.xem4 ***
*Firmware loading failed*
*Trying to boot from MMC1*
*Loading Environment from FAT... OK*


*U-Boot 2019.01-g333c3e72d3 (Apr 20 2020 - 04:15:00 +)*

*CPU  : DRA752-GP ES2.0*
*Model: TI AM5728 BeagleBoard-X15*
*Board: UNKNOWN(BeagleBoard X15?) REV UNKNOWN*
*DRAM:  2 GiB*
*MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1*
*Loading Environment from FAT... OK*
*Warning: fastboot.board_rev: unknown board revision*
*omap_hsmmc_send_cmd : DMA timeout: No status update*
*invalid mmc device*
*am57x_idk_lcd_detect: Failed to get I2C device 0/56 (ret 1)*
*Net:   Could not get PHY for ethernet@48484000: addr 1*

*Warning: ethernet@48484000 using MAC address from ROM*
*eth0: ethernet@48484000*
*Hit any key to stop autoboot:  2 1 0 *
*switch to partitions #0, OK*
*mmc0 is current device*
*SD/MMC found on device 0*
*** Unable to read file boot.scr ***
*1490 bytes read in 3 ms (484.4 KiB/s)*
*Loaded env from uEnv.txt*
*Importing environment from mmc0 ...*
*Running uenvcmd ...*
*1 bytes read in 1 ms (1000 Bytes/s)*
*Already setup.*
*switch to partitions #0, OK*
*mmc0 is current device*
*SD/MMC found on device 0*
*4448768 bytes read in 758 ms (5.6 MiB/s)*
*90792 bytes read in 18 ms (4.8 MiB/s)*
*## Flattened Device Tree blob at 8800*
*   Booting using the fdt blob at 0x8800*
*   Loading Device Tree to 8ffe6000, end 82a7 ... OK*

*Starting kernel ...*

*[0.00] Booting Linux on physical CPU 0x0*
*[0.00] Linux version 4.19.94-gbe5389fd85 (oe-user@oe-host) (gcc 
version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 
(arm-rel-8.36))) #1 SMP PREEMPT Sun Apr 19 02:36:36 UTC 2020*
*[0.00] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), 
cr=30c5387d*
*[0.00] CPU: div instructions available: patching division code*
*[0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction 
cache*
*[0.00] OF: fdt: Machine model: TI AM5728 BeagleBoard-X15*
*[0.00] Memory policy: Data cache writealloc*
*[0.00] efi: Getting EFI parameters from FDT:*
*[0.00] efi: UEFI not found.*
*[0.00] Reserved memory: created CMA memory pool at 
0x9580, size 56 MiB*
*[0.00] OF: reserved mem: initialized node ipu2-memory@9580, 
compatible id shared-dma-pool*
*[0.00] Reserved memory: created CMA memory pool at 
0x9900, size 64 MiB*
*[0.00] OF: reserved mem: initialized node dsp1-memory@9900, 
compatible id shared-dma-pool*
*[0.00] Reserved memory: created DMA memory pool at 
0x9d00, size 32 MiB*
*[0.00] OF: reserved mem: initialized node ipu1-memory@9d00, 
compatible id shared-dma-pool*
*[0.00] Reserved memory: created CMA memory pool at 
0x9f00, size 8 MiB*
*[0.00] OF: reserved mem: initialized node dsp2-memory@9f00, 
compatible id shared-dma-pool*
*[0.00] cma: Reserved 24 MiB at 0xfe40*
*[0.00] OMAP4: Map 0xffd0 to (ptrval) for dram barrier*
*[0.00] Hit pending asynchronous external abort (FSR=0x1211) 
during first unmask, this is most likely caused by a firmware/bootloader 
bug.*
*[0.00] DRA752 ES2.0*
*[0.00] random: get_random_bytes called from 
start_kernel+0xb4/0x470 with crng_init=0*
*[0.00] percpu: Embedded 15 pages/cpu s32396 r8192 d20852 u61440*
*[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 
464192*
*[0.00] Kernel command line: console=ttyS2,115200n8 
root=PARTUUID=351f25a0-02 rw rootfstype=ext4 rootwait*
*[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 
bytes)*
*[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 
bytes)*
*[0.00] Memory: 1673056K/1863680K available (10240K kernel code, 
335K rwdata, 2800K rodata, 2048K init, 268K bss, 34976K reserved, 155648K 
cma-reserved, 1283072K highmem)*
*[0.00] Virtual kernel memory layout:*
*[0.00] vector  : 0x - 0x1000   (   4 kB)*
*[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)*
*[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)*
*[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)*
*[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)*
*[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)*
*[0.00]   .text : 0x(ptrval) - 0x(ptrval)   (12256 kB)*
*[0.00]   .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)*

[beagleboard] PWM using eCAP module in PRU-ICSS

2020-07-19 Thread Vedant Paranjape 

Hi, 
I wanted to use PRU-ICSS's eCap module to generate PWM signals, It is 
something I want to implement in my GSoC project. I referred to AM335x TRM 
 section 15.3, It has a 
detailed description of how to use ECAP to generate PWM signals at section 
15.3.3.5. 
Since pru_ecap.h was missing bit fields required to use PWM mode, as 
described in the TRM (15.3.3.5.1) I defined those required bit fields from 
register descriptions in the TRM (15.3.4). Here's the new header I defined: 
https://github.com/VedantParanjape/pru-ecap-pwm/blob/master/include/am335x/pru_ecap.h

According to the register value (Table 15-100 and Example 15-13 of the TRM) 
needed to be set to get it working, I set the registers in my code. Here is 
my main code which drives the eCap module to generate PWM: 
https://github.com/VedantParanjape/pru-ecap-pwm/blob/master/main0.c

I am using pru-gcc version: 





*pru-gcc (GCC) 10.0.1 20200315 (experimental)Copyright (C) 2020 Free 
Software Foundation, Inc.This is free software; see the source for copying 
conditions.  There is NOwarranty; not even for MERCHANTABILITY or FITNESS 
FOR A PARTICULAR PURPOSE.*
Command to compile: 
*pru-gcc main0.c -o pwm -I./inlude/ -I./include/am335x/ -mmcu=am335x.pru0*

Command to load binary and start PRU:

*cp pwm /lib/firmware/am335x-pru0-fw *

*config-pin p9.42 pru_ecap *
*echo start > /sys/class/remoteproc/remoteproc0/state *

When I load the binary, it loads without any issue, but i fail to get 
output on p9.42 pin, which is the pr1_ecap pin. I check with a multimeter, 
It shows Nada, zero Volts.

I am using a BeagleBone Black Wireless: 
*Linux beaglebone 4.19.94-ti-r45 #1buster SMP PREEMPT Thu Jun 18 19:18:41 
UTC 2020 armv7l GNU/Linux*

This the output on running *(sudo show-pins | sort*) 
https://pastebin.com/r2128R9b
This is my *uEnv.txt*: https://pastebin.com/99qxs8NN

Regards,
Vedant Paranjape

-- 
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/b8d99fed-89f1-4a93-9d17-74e0cb991692n%40googlegroups.com.

[beagleboard] Re: PWM using eCAP module in PRU-ICSS

2020-07-19 Thread Vedant Paranjape 
Hi,
I need to add one more thing to this. On running *sudo 
/opt/scripts/tools/version.sh, *this is the output: 
https://pastebin.com/tgwb3u3S

Regards,
Vedant Paranjape
On Monday, July 20, 2020 at 1:36:48 AM UTC+5:30 Vedant Paranjape wrote:

>
> Hi, 
> I wanted to use PRU-ICSS's eCap module to generate PWM signals, It is 
> something I want to implement in my GSoC project. I referred to AM335x TRM 
>  section 15.3, It has a 
> detailed description of how to use ECAP to generate PWM signals at section 
> 15.3.3.5. 
> Since pru_ecap.h was missing bit fields required to use PWM mode, as 
> described in the TRM (15.3.3.5.1) I defined those required bit fields from 
> register descriptions in the TRM (15.3.4). Here's the new header I defined: 
> https://github.com/VedantParanjape/pru-ecap-pwm/blob/master/include/am335x/pru_ecap.h
>
> According to the register value (Table 15-100 and Example 15-13 of the 
> TRM) needed to be set to get it working, I set the registers in my code. 
> Here is my main code which drives the eCap module to generate PWM: 
> https://github.com/VedantParanjape/pru-ecap-pwm/blob/master/main0.c
>
> I am using pru-gcc version: 
>
>
>
>
>
> *pru-gcc (GCC) 10.0.1 20200315 (experimental)Copyright (C) 2020 Free 
> Software Foundation, Inc.This is free software; see the source for copying 
> conditions.  There is NOwarranty; not even for MERCHANTABILITY or FITNESS 
> FOR A PARTICULAR PURPOSE.*
> Command to compile: 
> *pru-gcc main0.c -o pwm -I./inlude/ -I./include/am335x/ -mmcu=am335x.pru0*
>
> Command to load binary and start PRU:
>
> *cp pwm /lib/firmware/am335x-pru0-fw *
>
> *config-pin p9.42 pru_ecap *
> *echo start > /sys/class/remoteproc/remoteproc0/state *
>
> When I load the binary, it loads without any issue, but i fail to get 
> output on p9.42 pin, which is the pr1_ecap pin. I check with a multimeter, 
> It shows Nada, zero Volts.
>
> I am using a BeagleBone Black Wireless: 
> *Linux beaglebone 4.19.94-ti-r45 #1buster SMP PREEMPT Thu Jun 18 19:18:41 
> UTC 2020 armv7l GNU/Linux*
>
> This the output on running *(sudo show-pins | sort*) 
> https://pastebin.com/r2128R9b
> This is my *uEnv.txt*: https://pastebin.com/99qxs8NN
>
> Regards,
> Vedant Paranjape
>

-- 
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/f33e6877-fe45-4d9b-b42c-dd8d4b5091e9n%40googlegroups.com.

[beagleboard] Re: BBW not booting when serial to USB cable connected

2020-07-19 Thread Dennis Lee Bieber 
On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh
 wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


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

Re: [beagleboard] Re: BBW not booting when serial to USB cable connected

2020-07-19 Thread 'Mark Lazarewicz' via BeagleBoard 
Virtual Box support of SUB driver's was squirrelly 2 years ago.If I'm not 
mistaken at one point Mr Robert refused to support builds.
I was  able to get it to work but the flakiness of serial output wasn't worth 
the aggravation 

Sent from Yahoo Mail on Android 
 
  On Sun, Jul 19, 2020 at 7:51 PM, Dennis Lee Bieber 
wrote:   On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh
 wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

    Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

    Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

    I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


-- 
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/58q9hfdcb0idakr5a77iamv34qm4cb4ilc%404ax.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/1350777360.2861083.1595210466223%40mail.yahoo.com.

Re: [beagleboard] Re: BBW not booting when serial to USB cable connected

2020-07-19 Thread 'Mark Lazarewicz' via BeagleBoard 

Try disabling the driver in win10 before starting virtual  box before starting 
VM then in Linux VM check which try enumerated and connect  to it was the fix I 
think.  With multiple USB devices it would change if I remember and you  might  
Google which VB version supports SUB best, Again that was several years 
backThis phenomenon was easily  found and described  by googling 
Sent from Yahoo Mail on Android 
 
  On Sun, Jul 19, 2020 at 9:01 PM, 'Mark Lazarewicz' via 
BeagleBoard wrote:   Virtual Box support of SUB 
driver's was squirrelly 2 years ago.If I'm not mistaken at one point Mr Robert 
refused to support builds.
I was  able to get it to work but the flakiness of serial output wasn't worth 
the aggravation 

Sent from Yahoo Mail on Android 
 
  On Sun, Jul 19, 2020 at 7:51 PM, Dennis Lee Bieber 
wrote:   On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh
 wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

    Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

    Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

    I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


-- 
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/58q9hfdcb0idakr5a77iamv34qm4cb4ilc%404ax.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/1350777360.2861083.1595210466223%40mail.yahoo.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/1930140602.2868269.1595210819228%40mail.yahoo.com.

Re: [beagleboard] Re: BBW not booting when serial to USB cable connected

2020-07-19 Thread jonnymo 
Are you plugging both USB cables directly to your PC or are you using a
Powered USB Hub?
I would suggest using a powered USB hub in this case if you were not using
one already or power the BBW via the barrel jack.


Cheers,

Jon




On Sun, Jul 19, 2020 at 7:07 PM 'Mark Lazarewicz' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

>
> Try disabling the driver in win10 before starting virtual  box before
> starting VM then in Linux VM check which try enumerated and connect  to it
> was the fix I think.  With multiple USB devices it would change if I
> remember and you  might  Google which VB version supports SUB best, Again
> that was several years back
> This phenomenon was easily  found and described  by googling
>
> Sent from Yahoo Mail on Android
> 
>
> On Sun, Jul 19, 2020 at 9:01 PM, 'Mark Lazarewicz' via BeagleBoard
>  wrote:
> Virtual Box support of SUB driver's was squirrelly 2 years ago.
> If I'm not mistaken at one point Mr Robert refused to support builds.
>
> I was  able to get it to work but the flakiness of serial output wasn't
> worth the aggravation
>
> Sent from Yahoo Mail on Android
> 
>
> On Sun, Jul 19, 2020 at 7:51 PM, Dennis Lee Bieber
>  wrote:
> On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Rishabh
>  wrote:
>
> >I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
> >10. I am trying to use a PL2303HXA serial to USB cable to get the serial
> >output to my terminal in Ubuntu. I am doing this to view U-Boot.
> >
>
> Wonder if Win10 may be getting in the way... The driver for the HXA is
> no longer supported in Win10.
> http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
> """
> NOTE:
>
> Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
> versions.
> """
>
> I don't know how VirtualBox handles USB devices -- if they pass through
> to the guest OS as raw devices, or if VBox is intercepting the guest I/O
> and mapping through the host OS...
>
> https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA
>
>
> --
> 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/58q9hfdcb0idakr5a77iamv34qm4cb4ilc%404ax.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/1350777360.2861083.1595210466223%40mail.yahoo.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/1930140602.2868269.1595210819228%40mail.yahoo.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/CAG99bkoxYfQ2Q0qFFstWgKgQOEoTeAg358Zytx3F1qDS0qnj8A%40mail.gmail.com.

Re: [beagleboard] BBW not booting when serial to USB cable connected

2020-07-19 Thread 'Mark Lazarewicz' via BeagleBoard 
Did you  try this using a Windows serial terminal as well?Your fatal error is 
in linux terminal in virtual machineLet us know if there  is a difference and 
use a powered hub or power supply  as was suggested 

Sent from Yahoo Mail on Android 
 
  On Sun, Jul 19, 2020 at 2:54 PM, Rishabh wrote:   
Hi,
I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 10. I 
am trying to use a PL2303HXA serial to USB cable to get the serial output to my 
terminal in Ubuntu. I am doing this to view U-Boot.

Whenever the serial to USB is connected, the board doesn't boot up.  

When the serial to USB cable is connected and I run 

picocom -b 115200 /dev/ttyUSB0 

the terminal waits for data on the port. As soon as I try to power up the board 
with the micro-USB cable, I get a fatal error and the serial port connection 
gets lost.
picocom v2.2

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

Type [C-a] [C-h] to see available commands

Terminal ready

FATAL: term closed


The board boots up only when the serial to USB cable is disconnected from the 
PC.
I tried to connect the serial to USB after powering up the board and that 
powers off the board. I am not sure why but the two connections (serial to USB 
and micro-USB power cable) seem to be mutually exclusive. I would appreciate 
any suggestions on how to resolve this issue.
Thanks,Rishabh


-- 
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/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%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/1586234867.2880589.1595215261151%40mail.yahoo.com.

[beagleboard] Re: U-boot serial console output disabled

2020-07-19 Thread Robert Cachro 
I guess the real question is, how do we update the Beaglebone's MLO and 
u-boot.img if we are running the OS from eMMC?

Thanks,
Robert

On Friday, July 17, 2020 at 5:25:19 PM UTC-5, Robert Cachro wrote:
>
> Hi,
>
> In an effort to mitigate a potential security vulnerability, I am 
> attempting to disable u-boot Serial Console output which I am monitoring 
> via FTDI. This can be done by modifying the source of U-Boot to configure 
> the device for silent booting (
> https://github.com/rickyzhang82/u-boot4bbb/blob/master/doc/README.silent)
>
> I am running Debian 9.9 Stretch IoT on a Beaglebone Black Wireless.
>
> Here is what I have done thus far:
> -
> *Download U-boot*
> ---
> wget ftp://ftp.denx.de/pub/u-boot/u-boot-2019.04.tar.bz2
> tar -xjf u-boot-2019.04.tar.bz2
> cd u-boot-2019.04/
> ## from https://rcn-ee.com/repos/git/u-boot-patches/
> wget -c 
> https://github.com/eewiki/u-boot-patches/raw/master/v2019.04/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> wget -c 
> https://github.com/eewiki/u-boot-patches/raw/master/v2019.04/0002-U-Boot-BeagleBone-Cape-Manager.patch
>
> patch -p1 < 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> patch -p1 < 0002-U-Boot-BeagleBone-Cape-Manager.patch
> -
> *Modify U-boot to disable console output*
> -
> cd /u-boot-2019.04/include/configs
> vim am335x_evm.h
> (add bolded)
> *#define CONFIG_SILENT_CONSOLE*
> *#define CONFIG_SYS_DEVICE_NULLDEV*
> *#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC*
> …
> #define CONFIG_EXTRA_ENV_SETTINGS \
> DEFAULT_LINUX_BOOT_ENV \
> DEFAULT_MMC_TI_ARGS \
> DEFAULT_FIT_TI_ARGS \
> "bootpart=0:2\0" \
> "bootdir=/boot\0" \
> "bootfile=zImage\0" \
> "board_eeprom_header=undefined\0" \
> "fdtfile=undefined\0" \
> *"silent=1\0" \*
> "console=ttyO0,115200n8\0" \
> -
> *Compile*
> -
> cd ../..
> make ARCH=arm CROSS_COMPILE=${CC} distclean
> make ARCH=arm CROSS_COMPILE=${CC} am335x_evm_defconfig
> make ARCH=arm CROSS_COMPILE=${CC}
> ls -l MLO u-boot.img
> -
> *Update u-boot on image*
> -
> dd if=MLO of=/dev/mmcblk1 bs=512 seek=256 count=256 conv=notrunc
> dd if=u-boot.img of=/dev/mmcblk1 bs=512 seek=768 count=1024 conv=notrunc
> -
> *Reboot*
> -
>
>
> However, the serial console which I am monitoring via FTDI cable still 
> shows output.
>
>
> Any thoughts? 
>
> I think the final step, where I update u-boot on my current image, may not 
> be done correctly.
>
>
> Thank you,
>
> Robert
>
>

-- 
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/261cf27a-d530-4898-a88b-b8d845e82e90o%40googlegroups.com.