Older versions of Eagle can do 3D exports. The process flow I have used with
Eagle6 is -
Generate a ENM file from the ULP exporter.
Convert the ENM to a suitable 3D file format STEP
Import there STEP file into MCAD
There are suppose to be ULPs that can generate a SAT but that triggers a bug
i
On Monday, November 13, 2017 11:00:06 Stephane Charette wrote:
> Not familiar with Bluetooth. I own several BBBW and BBGW devices. Is there
> a way to interconnect the devices using Bluetooth?
>
> What would that mean -- does Bluetooth provide an IP address? Is there an
> interface I can access
Kirk,
What bus are you using (SPI or I2C)? Both are "slow" buses which can sleep on
you. In addition, are you using the FIFO?
Scheduling your reads and using a fast enough SPI setting along with the FIFO
should let you acquire at 3.2KHz w/o drops.
On Tuesday, August 02, 2016 15:17:02 Kirk wro
>From a pin allocation prospectively, allocating the right McASP pins may
introduce other problems (pin sharing, etc). The ADCs have dedicated analog
pins to avoid this.
For basic ("telephony quality") audio, the ADCs are quite work able. Things
you need to consider are -
- Signal conditioning
The ADC is a SAR ADC. Overclocking it is likely to have side effects on the
analog end of things which will reduce accuracy.
Ignoring that it is a very bad idea to keep doing things in userland:
On Monday, June 20, 2016 18:06:09 John Syne wrote:
> That is a totally different issue. You were read
On Monday, April 04, 2016 16:05:47 John Syne wrote:
> Yeah, this is the approach used by the I2C Slave Framework. So
> traditionally, the McSPI driver registers with the SPI Framework as an SPI
> Master. Now through DT config, we could have the McSPI driver register with
> the SPI Framework as an
On Monday, April 04, 2016 13:13:48 John Syne wrote:
> > On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote:
> >
> > On Monday, April 04, 2016 12:04:56 John Syne wrote:
> >> I’m not sure that is correct. The master will normally send a command and
> >> then your slave driver will have to respond
On Monday, April 04, 2016 12:04:56 John Syne wrote:
> I’m not sure that is correct. The master will normally send a command and
> then your slave driver will have to respond with relevant packet. The
> protocol will have to be well defined.
None of that is required by SPI (in the most basic form
Getting it to work is not hard. (Had it working for a project.) To get to work
reliably at a high clock rate requires debugging the DMA or working out a
protocol where timing isn't as tricky. As a slave the master can start
clocking at anytime and unless the FIFO (or DMA) is preloaded with the e
Not to add add data points to the flames but -
That example code in that link works fine. Was able to use that sample code to
build a rpmsg simulator for other hw using the PRU. The PRU firmware creates 2
rpmsg channels that gets messages sent between then. Setup is:
Kernel driver A is a I2C dri
You might want think more about this then the peep hole approach.
Rather then running things in userland and relying on user id isolation; a
better way is to write a kernel driver that exposes a very specific and
limited interface. GPIOs are directly toggling hardware which means there are
more
You are going about this with blinders on. Unless you are writing baremetal or
kernel code (which most of the languages you listed are not really targeted
toward), you should be asking about writing to serial devices.
You are on Linux and the Linux interfaces for serial ports (which UARTs are)
A few other bits of information is needed to get to the bottom of this.
- When you run the code on PRU0, what is running on PRU1? Do you put it in
reset or at least have it doing something that cannot interfere?
- Is everything in the local memory to the PRU in use or in the shared memory?
- Is
If the goal is to recover data, it might be easier to get the eMMC mounted on
an adapter board (instead of risking another BeagleBone) so it can be read
from a PC or another card reader.
Or for the really adventureous - remove the eMMC and do a dead wiring to a
disassembled uSD to SD adapter.
On Friday, October 09, 2015 17:09:32 William Hermans wrote:
> Look, I'm no EE, but do things the right way . . . if you start putting too
> much current or voltage on the wrong pins. You'll end up frying the
> processor. Then no doubt start telling the BBB is garbage because you were
> not up to th
Depending on exactly what is needed (current draw, etc), there is a way to
generate a 5V pulse without a transistor. I didn't see any specs on what is
needed in this thread so be sure to verify what you are doing against the
specs of all the components involved.
The VBUS line on the USB host si
On Thursday, August 27, 2015 08:10:17 'Vassilis Mantas' via BeagleBoard wrote:
> Ok, i work over a color sorting project in food industry with minimum cost.
> I have decided to use BeagleboneBlack and OpenCV.
> The problem occured is the camera...
>
> As far as i know (google) my only option is a
On Tuesday, April 07, 2015 15:21:00 Drew Fustini wrote:
> anyone see a cape with cap touch functionality?
>
> along the lines of:
> Adafruit 12 x Capacitive Touch Shield for Arduino - MPR121
> https://www.adafruit.com/products/2024
>
> if not, i'm think i might give a crack at making a cape with
18 matches
Mail list logo
