With the Cape plugged into the console version it gets to a certain point and
then shuts off.
U-Boot SPL 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +)
Trying to boot from MMC2
Loading Environment from EXT4... ** File not found /boot/uboot.env **
** Unable to read "/boot/uboot.env" from
On Fri, May 14, 2021 at 9:24 PM John Dammeyer wrote:
>
> I moved the MicroSD card over to the other Beagle. Booted and USB mouse and
> keyboard (Logitech wireless) work. The Logitech wireless was not discovered
> on the other Beagle.
>
>
>
> I think it may be sick.
>
>
>
>
>
> Last login: Fri
I moved the MicroSD card over to the other Beagle. Booted and USB mouse and
keyboard (Logitech wireless) work. The Logitech wireless was not discovered on
the other Beagle.
I think it may be sick.
Last login: Fri May 14 18:11:06 2021 from 192.168.0.137
debian@beaglebone:~$ sudo
Does USB work after 30-45 seconds? If so, still trying to debug that..
On Fri, May 14, 2021, 7:23 PM John Dammeyer wrote:
> Hi Robert,
> Not that set in stone really. Just that the last time I did one of those
> "you must upgrade to get support" I ended up buying a new edition of Derek
>
On Fri, May 14, 2021 at 6:09 PM Robert Nelson wrote:
>
> On Fri, May 14, 2021 at 4:58 PM John Dammeyer wrote:
> >
> > So here's the results of version.sh from both beagles. The rev 141
> > doesn't see the cape_CBB_Serial-r01 from Logic Supply as shown in the
> > photo. For convenience I've
On Fri, May 14, 2021 at 4:58 PM John Dammeyer wrote:
>
> So here's the results of version.sh from both beagles. The rev 141 doesn't
> see the cape_CBB_Serial-r01 from Logic Supply as shown in the photo. For
> convenience I've also included the side by side compare of the two files.
>
> Not
Thanks for future research.
Unfortunately GDB won't work when your board doesn't run.
For cost sensitive products using a OEM board isn't always an option.
In high volume pennies make a difference that's why ESP32 it's low cost and is
popular and I'm sure it now has a JTAG but yes GDB is an
Kasimir
PS try out ddd in top of gdb ..
easy to use, simple and efficient
'Mark Lazarewicz' via BeagleBoard schrieb am
Fr., 14. Mai 2021, 23:18:
> CCS/JTAG works for me . I have used FPGA arm cores and ESP32
> My position and opinion is unique in this group
> I see no value in a PRU UNLESS
CCS/JTAG works for me . I have used FPGA arm cores and ESP32 My position and
opinion is unique in this group I see no value in a PRU UNLESS every
peripheral is used on DSP/ARM and you need more peripherals I have seen that
done in a RTOS on ARM DSP PRU omapL178 very complex Motor controller
On Fri, May 14, 2021 at 1:46 PM johnd wrote:
>
> Ah. So it doesn't apply to Debian. Thanks
For Debian, it's enabled out of the box, just use config-pin to change
it from i2c to can..
If it doesn't work, report back with:
sudo /opt/scripts/tools/version.sh
Regards
--
Robert Nelson
Ah. So it doesn't apply to Debian. ThanksSent from my Samsung S10
Original message From: Andy Bergh
Date: 2021-05-14 11:36 a.m. (GMT-08:00) To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Configure CAN0 with buildroot I am not sure what you
mean with OS version?
I am not sure what you mean with OS version? This is a buildroot OS with
the Linux kernel version 4.19.63
On Fri, May 14, 2021 at 8:06 PM johnd wrote:
> Which OS version?
>
>
>
> Sent from my Samsung S10
>
>
> Original message
> From: Andy Bergh
> Date: 2021-05-14 10:49 a.m.
Which OS version?Sent from my Samsung S10
Original message From: Andy Bergh
Date: 2021-05-14 10:49 a.m. (GMT-08:00) To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Configure CAN0 with buildroot Hi,For if ever anyone
runs into this problem, setting the following
Hi,
For if ever anyone runs into this problem, setting the following in the
linux-menuconfig file fixes the problem (to load the can device):
CONFIG_CAN_C_CAN=y
CONFIG_CAN_C_CAN_PLATFORM=y
Cheers
On Fri, May 14, 2021 at 10:39 AM Andy Bergh wrote:
> Thank you for the reply and info John.
>
>
Hi Alaganraj,
I've used your device tree on the BBxm with kernel 5.0.19 but I supsect
that only 9 bits are captured instead of 12.
The doubt arise from the fact that even with Test Pattern I cannot see
white but the highest value is 511 which is a dark gray.
I'm missing something ? Here below
Hi all,
I'm using Beagleboardxm with MT9P031 senosr.
I can capture the frames but looking at the buffer saved with yavta I see
the maximum value is 511 instead of 4095 for a white. It seems tha only 9
bit are correctly read.
I'm using Kernel 5.0.19 and the sesor is correctly reegistered.
Inside
>
> Hi Mark,
prudebug did help a lot. I'm missing a good debug environment for PRU
development.
Up to now it's time consuming try
It's more easy to use FPGA on top of Raspberry or use ESP32, 2. core for
dedicated high speed functions. At the end I want to use the CPU in my own
hardware,
Thank you for the reply and info John.
The solution provided (in the link as well) is using the debian
distribution for the beaglebone, which has a ton of packages to assist with
the configuration of the BBB. My buildroot image does not even have a
package manager! It is less than 80MB in total
I've only used CAN1 since the I2C for Cape ID isn't something I wanted to lose.
The Beagle that was running with the CAN cape had its SD card die so I lost the
configuration information. But this site here does a pretty good job of
explaining what is needed.
Hi,
How can I use the CAN0 device with a Buildroot image?
I have a Beaglebone black rev C and have build an image using Buildroot. I
used the standard beaglebone_defconfig and installed can-utils as well as
iproute2.
My understanding is that the i2c2 pins should be reconfigured to be able to
20 matches
Mail list logo
