FYI...my contact at Octavo informed me today that the industrial version of
the cSIP currently has a lead time of 6 weeks. They are flying off the
shelves.
On Sunday, January 31, 2021 at 4:40:14 PM UTC-7 d...@kulp.com wrote:
>
>
> On Jan 30, 2021, at 10:36 PM, Richard Sewell wrote:
>
> Thanks
lSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature>
>
> On Thu, Jan 14, 2021 at 5:54 PM, acheesehead
> > wrote:
> Ray,
>
> Thanks for the detailed response. Greatly appreciated!
>
> What was wrong with your schematic? And how did you get it to sh
:38:24 AM UTC-7 acheesehead wrote:
> Sorry. Can't share our design. Proprietary. No thermal issues as of yet,
> but we are not running intensive software. I do plan on inspecting using a
> thermal camera in real time sometime soon.
>
> On Tuesday, January 26, 2021 at 3:56:29
to share the high level design of the board. How do you deal
> with the heat issue
>
> Cheers
>
> frank
>
> On Wednesday, January 27, 2021 at 1:47:39 AM UTC+11 acheesehead wrote:
>
>> We have designed a board based upon the Octavo Systems cSIP, which is a
>>
We have designed a board based upon the Octavo Systems cSIP, which is a
step beyond the SIP. They added eMMC, EEPROM and a MEMS oscillator. Many
layout issues go away using their solution. I have worked extensively with
the Octavo folks. Very nice people. What I understand is that the company
work correclty until I edited
> this file then both showed up after deisgnated in the interfaces file. If
> you need to know more about what to edit... reply and I'll help.
>
> Regards,
> Ray
>
>
>
>
>
>
>
>
> On Thursday, January 14, 2021, 9:02:48 AM
485000.mdio:02,
> irq=POLL)
> debian@beaglebone:~$
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.14.108-ti-r131 #1buster SMP PREEMPT Tue Mar 24 19:18:36
> UTC 2020 armv7l GNU/Linux
> debian@beaglebone:~$ cat /etc/debian_version
> 10.3
>
>
> uname -r
> ca
I meant dmesg | grep mdio. Here is output.
beaglebone:~$ dmesg | grep mdio
[1.319622] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus
freq 100
[1.319638] davinci_mdio 4a101000.mdio: detected phy mask ffef
[1.338962] libphy: 4a101000.mdio: probed
[1.338993]
We have a custom board based upon the BBB. Added a second phy at MDIO
address 5. Modified device tree to mux pins and set up phys. When the board
boots I do a grep on dmesg for mdop/ I see a mask 0xffef, when I should
see a mask of 0xffcf. I am having trouble understanding where this
Nimbelink makes a cape that works
well. https://nimbelink.com/products/skywire-beaglebone-black-cape/
On Friday, January 1, 2021 at 7:48:35 AM UTC-7 Chris Green wrote:
> I want to get a 4G mobile data connection for my Beaglebone Black
> (which is on a boat in France).
>
> Has anyone done this
Look at gPTP.
On Wednesday, July 15, 2020 at 7:29:55 AM UTC-6, jaka.k...@gmail.com wrote:
>
> Current Beaglebone Black images offer support for high resolution timers
> in Linux kernel. They are controlled by ktime.h library and depend on
> system's clocks (CLOCK_MONOTONIC, CLOCK_REALTIME,...).
I am trying to get an AC 1200 adapter working on a BBB running Debian 9.8
(Linux 4.9.45-ti-r57). I tried the instructions referenced here:
https://askubuntu.com/questions/1018375/how-do-i-install-driver-for-rtl88x2bu
I get this error. Anybody know how to get this device working?
Kernel
Please share your uEnv and code. An output of the console during boot would
be helpful as well. I am struggling with the same problem on the Octavo Red
development board (a PocketBeagle with more stuff). Oscilloscope hooked up
to SPI_CS1. No pulses when doing a transfer and the signal is
That is cool!
On Wednesday, November 28, 2018 at 12:53:13 PM UTC-7, Jason Kridner wrote:
>
> Yeah, we don't exactly do the best job of getting the word out about
> BeagleBones in space. It has been done several times now, including at
> least one payload upon the ISS that I believe is still
You could write a memory compare check in MLO to see that the file is
indeed loaded correctly to help debug the problem. I wrote a routine to
write the memory address to each cell in memory and then compare. Not
totally comprehensive for stuck bits, but gave a warm fuzzy that memory was
Try reformatting SD card or use a new one. Copy MLO to the card *first*.
Use a known good MLO. It is signed by a special TI utility.
On Sunday, November 26, 2017 at 11:44:50 AM UTC-7, mike.ma...@gmail.com
wrote:
>
>
>> TI has not changes anything in StarterWare since BBB, so I don't expect a
MLO looks for uboot.bin. MLO can be rewritten to look for your application
or rename your application to uboot.bin. I chose to rewrite MLO, but forget
why. Was many years ago on Beagleboard Xm.
On Saturday, November 25, 2017 at 4:44:51 AM UTC-7, mike.ma...@gmail.com
wrote:
>
> Hi,
>
> I'm
A likely culprit is the power supply.
On Friday, November 24, 2017 at 7:55:56 AM UTC-7, Graham wrote:
>
> I have two PocketBeagles.
>
> Both are exhibiting random reboots, two to four times per day. No
> indication in syslog as to any cause or problem. No pattern to
> the reboots. Can happen
I have installed on several versions of BBB.
On Friday, November 17, 2017 at 2:46:23 AM UTC-7, AVR wrote:
>
> Please can you tell me for what revision BBB your QNX image?
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
I had no issue ordering from Digikey as Robert suggested. USPS says it will
be here Mon.
On Saturday, September 23, 2017 at 7:52:26 PM UTC-6, Eric Keller wrote:
>
> This happens at Mouser every time there is a new 'bone. It gets sorted
> eventually.
>
>
> On Sat, Sep 23, 2017 at 1:01 PM,
Sent you email with the files.
On Friday, July 14, 2017 at 1:20:54 PM UTC-6, set...@gmx.de wrote:
>
> Hey Acheesehead,
>
> funny name :) I'm sitting here with the same problem and want to use the
> adc of beaglebone black with qnx. But i cant figure out how it will work.
> C
Try this image,
https://drive.google.com/file/d/0BzU1D_qKT1dfUFpfclBGMU1SeWc/view?usp=sharing.
If it boots, then you are in business. I can send you the source tree if
this works. It will look for a file called rc.emmc located on the dos
partition of the eMMC to run additional stuff.
On
I switched to Debian. 3.8.13+. Went through the same steps, with no luck. I
have another USB Wifi device as well. It is a 148F:5370 Ralink 5370. Messed
with that a bit and got it to work. Thanks all!
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
5V, 3A wall wart.
On Saturday, May 13, 2017 at 5:14:15 PM UTC-6, William Hermans wrote:
>
> Todd, how are you powering your board ? Hopefully not via USB . . .
>
> On Sat, May 13, 2017 at 4:10 PM, acheesehead <achee...@gmail.com
> > wrote:
>
>> Yes, small dongle. It
Yes, small dongle. It is plugged into a powered USB hub. Disabled HDMI in
uEnv.txt. Rebooted and still no joy.
I tried the Debian image on the Chipsee DVD earlier today and no luck there
either, but could easily switch back to that. Other choices on the DVD
include Linux-EZSDK and Android. I
Thanks for your help William. I will try to somehow upgrade the image.
On Saturday, May 13, 2017 at 1:55:25 PM UTC-6, William Hermans wrote:
>
>
>
> On Sat, May 13, 2017 at 12:53 PM, acheesehead <achee...@gmail.com
> > wrote:
>
>> root@beaglebone-exp:~# opkg list-i
not work
> ;) It should work however.
>
> On Sat, May 13, 2017 at 12:33 PM, acheesehead <achee...@gmail.com
> > wrote:
>
>> root@beaglebone-exp:~# opkg list | grep ralink
>> linux-firmware-ralink -
>> 1:0.0+r8-gitAUTOINC+c530a75c1e6a472b0eb9558310b
root@beaglebone-exp:~# opkg list | grep ralink
linux-firmware-ralink -
1:0.0+r8-gitAUTOINC+c530a75c1e6a472b0eb9558310b518f0dfcd8860-r8.1 -
linux-firmware version
0.0+r8-gitAUTOINC+c530a75c1e6a472b0eb9558310b518f0dfcd8860-r8
On Saturday, May 13, 2017 at 1:31:30 PM UTC-6, William Hermans wrote:
Neither command exists on my system. Nor is it connected to the Internet. I
am connected directly to my laptop with an Ethernet cable. I have the
Chipsee 7" display and installed the Angstrom image on the DVD that came
with the display. I did reboot.
On Saturday, May 13, 2017 at 1:12:14 PM
Built the kernel according
to https://eewiki.net/display/linuxonarm/BeagleBoard with v4.9.x-rt
(Longterm 4.9.x + Real-Time Linux) and Root File System (small flash). It
gets to Waiting for root device /dev/mmcblk0p2... and hangs there.
Any suggestions?
Thanks!
.
--
For more options, visit
More info, from disassembled image, abort occurs in enter_kernel at 9e4:
09e0 <__enter_kernel>:
9e0: e3a0 mov r0, #0 ; 0x0
9e4: e1a0f004 mov pc, r4
On Tuesday, February 21, 2017 at 12:14:10 PM UTC-7, acheesehead wrote:
>
> Using JTAG to trace the problem, I found t
Using JTAG to trace the problem, I found that the code aborts at
0x820009e4, after eventually running a bunch of code in the 0xc000 area
of memory. The DM3730 TRM shows this region as reserved, so I am a bit
confused as to what could be there. Any suggestions on how to debug this?
:34 PM, acheesehead <achee...@gmail.com
> > wrote:
> > Using these instructions:
> >
> > https://eewiki.net/display/linuxonarm/BeagleBoard
> >
> > On the ./build_kernel.sh step, the script runs for a while and then a
> > configuration screen appears. I am n
Using these instructions:
https://eewiki.net/display/linuxonarm/BeagleBoard
On the ./build_kernel.sh step, the script runs for a while and then a
configuration screen appears. I am not sure what to change at that point.
.config - Linux/arm 4.9.8 Kernel Configuration
...
debug: [console=ttyO2,115200n8 root=PARTUUID=-02 ro rootfstype=ext4
rootwait] ...
debug: [bootz 0x8200] ...
Starting kernel ...
On Monday, February 13, 2017 at 11:33:26 AM UTC-7, acheesehead wrote:
>
> I am porting RT Linux 4.9.7 to a custom board. When u-boot tries to load
> /
: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
On Wednesday, February 8, 2017 at 1:39:01 PM UTC-7, RobertCNelson wrote:
>
> On Wed, Feb 8, 2017 at 2:33 PM, acheesehead <achee...@
, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as
> in Robert C. Nelson's page
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
> Here is what I get during boot, tried on a real Beag
Got around that problem. My uEnv.txt file was wrong.
On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as
> in Robert C. Nelson's page
> https://eewiki.net/display/linuxonarm
I built Linux RT for a custom board based upon Beagleboard xM exactly as in
Robert C. Nelson's page https://eewiki.net/display/linuxonarm/BeagleBoard.
Here is what I get during boot, tried on a real Beagleboard xM and get the
same behavior. The booting stops at a u-boot prompt.
U-Boot SPL
Angstrom image for the xM does not have the pinmux mechanism, which was
what prompted me to use the latest Linux version. Should keep me busy for a
while.
On Friday, February 3, 2017 at 12:47:25 PM UTC-7, acheesehead wrote:
>
> We have a board based upon the Beagleboard xM rev. C. We hav
in my pinmux pdf file. So yes, 4.x versus 3.8.x,
>> for gpio banks are definitely off by one. Looks like for 3.8.x kernel gpio
>> banks start at gpio1, and I know for a fact that gpio banks in 4.x start at
>> gpio0.
>>
>> Anyway, very good chance your overlay file i
Tried your workflow today without success. Everything is OK up to the lsmod
| grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel
expert, so I don't know how to troubleshoot why the other entries aren't
showing up.
I didn't see any activity on the oscilloscope either.
On
Thanks William. I'll try out your instructions on Mon.
On Thursday, December 1, 2016 at 10:50:19 PM UTC-7, William Hermans wrote:
>
>
> On Thu, Dec 1, 2016 at 10:39 PM, acheesehead <achee...@gmail.com
> > wrote:
>
>> In all of the examples that I have seen,
In all of the examples that I have seen, the P9.x -> GPIO bank.port
translates to GPIO (bank +1).port between lines in the overlay script.
On Wednesday, November 30, 2016 at 8:58:19 PM UTC-7, Sebastián Sáez wrote:
>
> Hi!
>
> I'm trying to read temp with a ds18b20 sensor. I try with a few
I also am having no luck. I created an overlay:
root@beaglebone:~# cat w1-p9-13.dts
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black",
"ti,beaglebone-green";
part-number = "BB-W1";
version = "00A0";
/* state the resources this cape uses */
This site has no logo versions: https://specialcomp.com/beaglebone/index.htm
I have got several boards from them. Have never had a problem with them.
On Friday, April 15, 2016 at 8:12:56 AM UTC-6, Fred Patrick wrote:
>
> The price on Amazon has gone fro $55 to $85 in the last month. Element14
>
I just downloaded and built the latest 'experimental' QNX 6.6 BSP for BBB.
Got the same errors. Turns out that the permissions of files in
install/sbin and install/bin needed to change. Once I changed their
permissions, all goes well. The build script does not mount the SD card or
the eMMC, so
These lines in the .build file should start the SD and eMMC:
###
## MMC/SD driver
###
display_msg Starting MMC/SD driver...
# MMC 0 pio
#
I am using QNX 6.50 on the BBB and have no problems.
Are the executables in question on a FAT32 partition? If so, execute
permissions can't be set. Are you booting from SD card or eMMC? What do
your partition tables look like on your boot device (fdisk view)? What is
the output of the mkifs
Use a flash drive or SD card.
On Sunday, October 4, 2015 at 5:18:34 AM UTC-6, 멘지 wrote:
>
> I'm using Putty
>
> and i want to file transfer to my PC (window 7)
>
> I want to run only the C language, without a separate program.
>
> The file is 200kb bmp files.
>
> Is there any way ??
>
> BBB was
SCP the file.
On Sunday, October 4, 2015 at 5:18:34 AM UTC-6, 멘지 wrote:
>
> I'm using Putty
>
> and i want to file transfer to my PC (window 7)
>
> I want to run only the C language, without a separate program.
>
> The file is 200kb bmp files.
>
> Is there any way ??
>
> BBB was installed Debian
back. Luckily, I have spares.
On Tuesday, September 22, 2015 at 7:43:36 PM UTC-6, Przemek Klosowski wrote:
>
> On Tue, Sep 22, 2015 at 10:39 AM, acheesehead <achee...@gmail.com
> > wrote:
>
>> I went through security with one and TSA thought it was suspicious. They
&
I went through security with one and TSA thought it was suspicious. They
put it under the X-Ray machine and stared at it for about a minute. It has
been confused since then. Sometimes boots, sometimes not. While a brief
exposure is probably OK. A prolonged exposure might fry something.
On
I am stuck. I did the following commands on several different machines with
different OSs.
git clone git://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
MACHINE=beaglebone ./oebb.sh config beaglebone MACHINE=beaglebone ./oebb.sh
update MACHINE=beaglebone ./oebb.sh bitbake
Here is some code from a Beagleboard (not Beaglebone) the register bases
and pin configs will be different, but it should give you an idea of how to
control a PWM using QNX. It is *not* a driver in the QNX sense, but a
low-level approach.
#include stdlib.h
#include stdio.h
#include stdint.h
Got it!
Steps 1 2 are not necessary. The rest is pretty straight-forward.
On Wednesday, March 11, 2015 at 2:27:30 PM UTC-6, acheesehead wrote:
I want to read the BBB ADC inputs using the QNX operating system. As no
driver is provided in the QNX BSP, I need to write low-level C code to do
We are trying to change the boot order to support booting from MMC2 and
MMC1, which requires swapping the boot resistors on the BOOT0 and BOOT1
lines. We are having trouble finding R125. Is there an assembly drawing
available for the BeagleBoard xM that would show us this?
Thanks in advance.
57 matches
Mail list logo
