The Ultra96 is simply the most powerful embedded processor I've ever used!
When loaded with PYNQ, a Python environment that runs in Jupyter it turns
into a powerful platform for FPGA development. Using a Ultra96 is akin to
taking an A10 Warthog to a gunfight.
--
website:
Hey, just chipping in here. You could use TCP for Axis also, however, there
would be a bit of additional overhead on connections. I've created a little
line, called in setup.sh script, that switch from IPC <-> TCP:
echo 'Changing to Remote Mode'
sed -r '31 s/([^:]+).*/REMOTE=1/'
>
> Perhaps it would be possible to run MK armhf style compiled on the
>> Ultra96, how to go about testing that and is this a viable solution ?
>
> I meant run the armhf .debs on the Ultra96 board.
On Sunday, 25 August 2019 14:05:53 UTC+2, Michael Brown wrote:
>
> BTW:
>
> Beagleboard x15 is
BTW:
Beagleboard x15 is armv7-a --> armhf ?
It seems like the rpi3's can run armhf compiled software, I do not know if
this requires the whole os to be armhf compiled also ?
Perhaps it would be possible to run MK armhf style compiled on the Ultra96,
how to go about testing that and is this a
OK decided to attempt the RIP method and after a dependency nightmare (and
enabling a swap file) got a full compilation,
with the scripts/build_with_cnc method.
Ready to run full machinekit RIP
real18m56,876s
user
Holy
machinekit@mksocfpga-nano-soc:~$ halrun
msgd:0 running
rtapi:0 running
halrun: Realtime already running. Use 'halrun -U' to stop existing
realtime session.
machinekit@mksocfpga-nano-soc:~$ halrun -U
machinekit@mksocfpga-nano-soc:~$ halrun
msgd:0 stopped
rtapi:0 stopped
rtapi_msgd
On Sunday, August 25, 2019 at 11:54:32 AM UTC-4, c.gl...@cox.net wrote:
>
> The Ultra96 is simply the most powerful embedded processor I've ever used!
>
> When loaded with PYNQ, a Python environment that runs in Jupyter it turns
> into a powerful platform for FPGA development. Using a Ultra96
mk-hal deb for test with sserial parse only mod.
Due to the number of changes I choose to creative a conservative change
only modding the:
hm2_sserial_parse_md() function, this is what does the intial probing and
pin setting..
The file you should use I think is:
On Sun, Aug 25, 2019 at 6:01 PM c.glas...@cox.net
wrote:
>
> The CRAMPS.bbio file has a line commented out that drives a test led on the
> CRAMPS board.
> When this line is enabled by removing the # and run it provokes a series of
> error messages starting with P9_25 pinmux file not found!
>
I suppose I should also ask, where's the source?
On Sunday, August 25, 2019 at 4:01:29 PM UTC-7, c.gl...@cox.net wrote:
>
> The CRAMPS.bbio file has a line commented out that drives a test led on
> the CRAMPS board.
> When this line is enabled by removing the # and run it provokes a series
> of
Aug 25, 2019, 20:52 by mib.holotro...@gmail.com:
> OK decided to attempt the RIP method and after a dependency nightmare (and
> enabling a swap file) got a full compilation,
> with the scripts/build_with_cnc method.
>
> Ready to run full machinekit RIP
>
The CRAMPS.bbio file has a line commented out that drives a test led on the
CRAMPS board.
When this line is enabled by removing the # and run it provokes a series of
error messages starting with P9_25 pinmux file not found!
NOT GOOD!!
I'm presently running the latest RCN release --
12 matches
Mail list logo
