I am looking a way to debug renesas Rxv2 core architecture mcu, is there a way I can debug these mcu in ozone or there is any other tool ?
Related
I'm trying to figure out if .Net Core 3.1 will run on an Orange Pi Zero.
I need to create an app for it which reads/writes to both the serial port and GPIO ports, and since the only programming language I know is C#, my two options are Mono or .Net Core. I'd prefer .Net Core if possible...
From what I've read, for .Net Core to run on an ARM CPU, the CPU must be at least ARMv7.
I see the Orange Pi Zero uses an AllWinner H2 SOC, which has an ARM Cortex-A7 CPU, which implements the ARMv7-A architecture.
So I think it should work... Could anyone please confirm this? Thanks
Based on
https://github.com/dotnet/iot/issues/751
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2408
looks like it runs.
Is it possible to run Esper CEP in an LPC4088 microcontroller with a 120 MHz ARM Cortex-M4 core?
I wonder if it is possible to it under JVM or using Nesper for .NET.
Esper needs a 1.8 or higher JVM. As long as that hardware can run a JVM you should be ok. Nesper needs a certain minimum .NET CLR, same there.
I need to use an STM32F4 MCU with Laird BL651 Bluetooth 5.0 module.
As I realized this module is not the regular simple AT Command module, but rather a Cortex-M microcontroller (Nordic nRF52810) with BT Stack. I have a 1.5 year experience with STM32 and the Cube firmware package, but have no experience either Bluetooth 5.0 nor Nordic products. So my question is basically, how to start the developement. I have found Nordic SDK but I am clueless, what information I will need hierinafter and where can I found sample codes.
Looking forward for the replies.
Thanks
Samu
As with most embedded development, your first step is to get any simple (prewritten) example to work, and then after that start either tailoring that example to your use case or creating a new one from scratch. For the BL651 you'll need to read up a bit on the Nordic SDK as well as Bluetooth Low Energy in general. Below are some useful references that will help you get started:-
Bluetooth Low Energy References
Bluetooth Low Energy: A Primer
Getting Started with Bluetooth Low Energy
Introduction to BLE
Nordic Development References
nRF5 Getting Started
nRF5 Series: Developing with SEGGER Embedded Studio
Introduction to Nordic SDK v16.0.0
I hope this helps.
I'm trying to understand how to cross-compile for a Raspberry PI3.
First, let me check if I understood correctly the meaning of the cross-compiling: is it to compile for a hardware that is different from the machine I'm building my application? This means, building for example a linux application from a windows system?
Second, all the tutorials I found required the building of QT for the target platform. Is this because to build a QT application I need the target-hardware-specific-built-version of QT libraries? Why there are no pre-built versions?
Third, I don't understand why a raspberry image is required in all the tutorials I could find.
Those are some of the tutorials I found, I found really strange that such a long setup is needed to cross-compile an application and I'm just wondering if what I'm trying to do (compile from a Linux machine a raspberry-pi3 QT application) is what those articles are really describing.
Tutorial 1, Tutorial 2, QT official embedded device page
You are correct, cross-compiling is building on one type of hardware (Host) to run on a different type of hardware (Target).
If you are willing to go for a commercial version of Qt, Qt will provided a turnkey solution (Boot to Qt) for developing on a specific Raspberry Pi. By turn-key, I mean they have all the target tools for cross compiling and the correctly built libraries for the target, etc. It's not cheap, and probably not the way to go for the hobbyist.
If you go with the open source (free) version of Qt, you will need to do most of the setup work yourself. The reason you are having a hard time finding everything built for you are mostly related to two things: The size of the distribution, and what you are building for what (i.e. which Qt version for which Raspberry Pi and which Raspberry Pi Linux version and which drivers, etc.).
The Raspberry Pi image is needed as you need the correct libraries to build Qt against. The cross-compilation tools need to link against the target (Raspberry Pi) images.
Yes, it is a long process to setup a Qt cross compilation environment, but it only needs to be done when once for each Qt version. Once you have setup the environment, building and deploying a Qt application on the target Raspberry Pi is really quite fast and easy.
I am trying to connect a Qt client to a LabVIEW server (acquiring analog signals). Can this be done with data sockets ?
Datasockets is an NI technology. It would depend if you can find a Datasocket library that you can call from Qt. I am not well-versed in Qt, but if it possible to call a C++ dll, then this is definitely available with Measurement Studio.
An simpler solution may be just to use TCP/IP which both LabVIEW(for sure) and Qt (presumably) support.
If you need further help, post more details about your app here, or on NI's forums.
Cheers!