First of all I am very new to application development with ST-Electronic device shields.
I have following devices with me,
X-NUCLEO-NFC05A1
NFC expansion shield Nucleo 64 : F401RE board.
I was doing some samples with ARM Mbed online compiler.
I want to access external NFC tag's content via NFC05A1 expansion board in ARM Mbed. However, I was not able to find a correct library for NFC05A1 expansion board in ARM Mbed. But, I found a sample and a library for different version of NFC shield : https://os.mbed.com/components/X-NUCLEO-NFC01A1/ and this is not compatible with the NFC05A1.
I was wondering whether there is a library which I can use in ARM Mbed to access NFC functionality in X-NUCLEO-NFC05A1 board.
Note: I found a following CUBE sample for this expansion board but, I do not think this can be used in ARM Mbed as a library.
https://www.st.com/content/st_com/en/products/embedded-software/mcu-mpu-embedded-software/stm32-embedded-software/stm32cube-expansion-packages/x-cube-nfc5.html
Related
I've decided to make the step up from using PIC to ARM Cortex-M but having trouble finding an equivalent to the PICKIT to program it.
After googling the net I have been given loads of options but have no idea what to buy.
Can anyone out there give me any advise on what to buy?
I'm so used to buying a PIC16F microcontroller, using MPLAB and the PICKIT 3 I'm unsure about what I need.
I like the ST-Nucleo and the slightly more complex ST Discovery. They are inexpensive (start at around $13), versions for just about all STM32 series, built-in ST-LINK debug pod, and have Arduino style header connectors.
You can program it using free or commercial IDE/compilers, mBed compilers, and even the Arduino IDE. You can start with using the free CubeMX graphical generator to generate initialization code.
So literally all you have to spend minimally is just a $13 kit and a USB cable to get started.
I want to use FreeRTOS for PIC32MX120F064H using MPLABX IDE. I tried a lot but couldn't find any simple LED blinking project for this specific microcontroller that I am using. I even tried demo projects given by FreeRTOS but they are for specific microcontrollers and doesn't work with my microcontroller. I only need the project structure (meaning what/how files to include) and a simple LED blinking demo. I know from the FreeRTOS site that we have to include task.c, queue.c and list.c as basic files but I tried everything but no luck. Please somebody help me with this.
The FreeRTOS.org site has a page describing how to convert a demo from one device in an MCU family to another device in the same family. Alternatively have the MPLAB Harmony tool create a FreeRTOS project for your chip.
I just searched about an open-source library to use of my project to build a voice controlled robot and found CMUsphinx. but my robot will build on ARM based microcontroller and I have not Linux or Windows on it. Is it possible to use CMUsphinx on ARM based microcontrollers? How can I do it?
Is there any better options instead of using CMUsphinx on ARM uControllers?
Actually, you can use a variant of CMUSphinx, known as PocketSphinx, on ARM devices. Most resources focus on Raspberry Pi, as it's a very popular ARM target.
The instructions for installing on a Raspberry Pi are here:
http://cmusphinx.sourceforge.net/2016/06/should-you-select-raspberry-pi-3-or-raspberry-pi-b-for-cmusphinx/
There's a voice assistant for Raspberry Pi that uses CMUSphinx:
http://cmusphinx.sourceforge.net/2014/04/jasper-personal-assistant-for-raspberry-pi/comment-page-1/
And, there's a recent blog post about running on the Raspberry Pi here:
http://cmusphinx.sourceforge.net/2016/06/should-you-select-raspberry-pi-3-or-raspberry-pi-b-for-cmusphinx/
Is it possible to use CMUsphinx on ARM based microcontrollers?
No, it's not possible to use CMUSphinx on microcontrollers.
but my robot will build on ARM based microcontroller
Consider using more powerful CPU, it will help you with other tasks like navigation or network sync as well.
My experience with micocontrollers and electronics is limited to ATmega Controllers, programmed in C and some tranistors and displays, nothing too special.
However, I want to get my hardware one step smaller, and want to start using the BLE Nano for all Bluetooth related projects.
For a first example project I'd like to create a bluetooth enabled temperature sensor with a small display.
As Display I chose the 0.96" OLED Display from Adafruit, which features a SSD1306 Controller. Adafruit offers a library for it (here: https://github.com/adafruit/Adafruit_SSD1306 ) but it is not clear to me, if I can use this library together with the BLE Nano.
I realized that I was to fixated on using the arduino library for my "normal" project.
There are other libraries out there, for example on github, which are written in plain c and should therefore be easier tot adapt for different platforms.
The Adafruit library is an Arduino library, so you would need to register your BLE Nano module in order to gain access to Red Bear's pre-release Arduino library - See the "Using Arduino" section of the "Getting Started with nRF51822" page
I'm using Arm DS-5 and Xilinx SDK for developing programs on Zynq board.
I'm trying to boot Zynq 702 board from Qspi Flash.
What I've done so far is generating FSBL project from Xilinx SDK, and combining it with my application using Bootgen tool in SDK, then program it into the flash.
There are several questions in my mind.
DS-5 produces an .axf file, Bootgen requires an .elf file. Can I use
the .axf file by just changing its extension to .elf or do I require
some more steps?
Is there a tool that shows the inner structure of an .axf file?
Showing what is where?
And how can I debug if I managed to boot from QSPI. For example I want to debug my application from the beginning of FSBL, is it possible? Because in Qspi Boot, When I power on the board, my application would start running and when I connect with JTAG, it would be in somewhere in my application.
An AXF might have some extra ARM-toolchain magic in it (I'm not sure off-hand), but at heart it's an ELF file - the ARM toolchain provides fromelf for poking around inside them, but other tools like readelf and objdump also work.
I'm not familiar with the Zynq platform so I don't know any specific debugger tricks, but a general one is just to put an infinite loop at the start of your code (possibly using volatile or inline asm trickery if necessary to prevent optimisation) - once the debugger's connected and broken into it, you just move the PC past the loop and continue.
You can totally halt QSPI-booted Zynq via JTAG and do whatever you want with it. However, there are some quirks. Sometimes Zynq goes into some kind of lockup, and JTAG doesn't work at all, and you need to power-cycle before retrying. Some not-so-well-written peripherial might die after starting software over JTAG, so you might need to re-load bitstream first. And there are some Vivado-related bugs (like the one where you cannot re-flash the board unless you downgrade to 2017.2 or change MIO2-6 pulls or patch the FSBL) but i'm not sure if they apply in your case.