FlexCAN linux driver for freescalle iMX6dl - linux-device-driver

is there an open source FlexCAN Linux driver for the iMX6dl SOM ?
if so where can i get it ?
Thanks.

It's already in upstream in drivers/net/can/flexcan.c
Kconfig excerpt:
CAN_FLEXCAN
tristate "Support for Freescale FLEXCAN based chips"
depends on ARM || PPC
---help---
Say Y here if you want to support for Freescale FlexCAN.

Related

Stop SE Linux from Enforcing on Android AOSP

I need to stop SE Linux from enforcing, from the earliest possible time in the Android boot sequence.
I had read that a kernel parameter of "selinux=0" would stop this. It doesn't:
smarc_mx8mq:/ # cat /proc/cmdline
selinux=0 console=ttymxc2,115200 earlycon=imxuart,0x30880000,115200 init=/init video=HDMI-A-1:1080x1920-32#60 androidboot.console=ttymxc0 androidboot.hardware=freescale androidboot.fbTileSupport=enable cma=1280M androidboot.primary_display=imx-drm firmware_class.path=/vendor/firmware transparent_hugepage=never loop.max_part=7 buildvariant=eng ...
smarc_mx8mq:/ # getenforce
Enforcing
What can I do to absolutely stop SE Linux from enforcing from the start of the boot sequence? (I can have root shell access and I can change the kernel config or any other part of the AOSP build.)
What can I do to absolutely stop SE Linux from enforcing from the start of the boot sequence? (I can have root shell access and I can change the kernel config or any other part of the AOSP build.)
I turn off selinux in BoardConfig.mk by setting:
BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive
Then after building and target flashingcat /proc/cmdline shows androidboot.selinux=permissive:
hikey960:/ # cat /proc/cmdline
androidboot.hardware=hikey960 firmware_class.path=/vendor/firmware loglevel=15 efi=noruntime
overlay_mgr.overlay_dt_entry=hardware_cfg_enable_android_fstab androidboot.selinux=permissive
The solution is to use androidboot.selinux=permissive instead of selinux=0.
I've read that androidboot.selinux=disabled will work too.

Launch MongoDB built from source on ARM

I followed this tutorial to compile a MongoDB on a raspberry pi. I ended up with the content of the tarball which is on the same repo.
The unpacked archive has the following structure:
mongo-embedded-sdk-4.0.4
include lib share
mongo-embedded-sdk-4.0.4/include:
libbson-1.0 libmongoc-1.0 mongo_embedded mongoc_embedded
mongo-embedded-sdk-4.0.4/include/libbson-1.0:
bson bson.h
mongo-embedded-sdk-4.0.4/include/libbson-1.0/bson:
bcon.h bson-context.h bson-json.h bson-oid.h bson-value.h
bson-atomic.h bson-decimal128.h bson-keys.h bson-reader.h bson-version-functions.h
bson-clock.h bson-endian.h bson-macros.h bson-string.h bson-version.h
bson-compat.h bson-error.h bson-md5.h bson-types.h bson-writer.h
bson-config.h bson-iter.h bson-memory.h bson-utf8.h bson.h
mongo-embedded-sdk-4.0.4/include/libmongoc-1.0:
mongoc mongoc.h
mongo-embedded-sdk-4.0.4/include/libmongoc-1.0/mongoc:
mongoc-apm.h mongoc-error.h mongoc-init.h mongoc-socket.h mongoc-topology-description.h
mongoc-bulk-operation.h mongoc-find-and-modify.h mongoc-iovec.h mongoc-ssl.h mongoc-uri.h
mongoc-change-stream.h mongoc-flags.h mongoc-log.h mongoc-stream-buffered.h mongoc-version-functions.h
mongoc-client-pool.h mongoc-gridfs-file-list.h mongoc-macros.h mongoc-stream-file.h mongoc-version.h
mongoc-client-session.h mongoc-gridfs-file-page.h mongoc-matcher.h mongoc-stream-gridfs.h mongoc-write-concern.h
mongoc-client.h mongoc-gridfs-file.h mongoc-opcode.h mongoc-stream-socket.h mongoc.h
mongoc-collection.h mongoc-gridfs.h mongoc-rand.h mongoc-stream-tls-libressl.h
mongoc-config.h mongoc-handshake.h mongoc-read-concern.h mongoc-stream-tls-openssl.h
mongoc-cursor.h mongoc-host-list.h mongoc-read-prefs.h mongoc-stream-tls.h
mongoc-database.h mongoc-index.h mongoc-server-description.h mongoc-stream.h
mongo-embedded-sdk-4.0.4/include/mongo_embedded:
v1
mongo-embedded-sdk-4.0.4/include/mongo_embedded/v1:
mongo_embedded
mongo-embedded-sdk-4.0.4/include/mongo_embedded/v1/mongo_embedded:
mongo_embedded.h
mongo-embedded-sdk-4.0.4/include/mongoc_embedded:
v1
mongo-embedded-sdk-4.0.4/include/mongoc_embedded/v1:
mongoc_embedded
mongo-embedded-sdk-4.0.4/include/mongoc_embedded/v1/mongoc_embedded:
mongoc_embedded.h
mongo-embedded-sdk-4.0.4/lib:
cmake libbson-1.0.so.0 libmongo_embedded.so libmongoc-1.0.so.0 libmongoc_embedded.so
libbson-1.0.so libbson-1.0.so.0.0.0 libmongoc-1.0.so libmongoc-1.0.so.0.0.0 pkgconfig
mongo-embedded-sdk-4.0.4/lib/cmake:
libbson-1.0 libmongoc-1.0
mongo-embedded-sdk-4.0.4/lib/cmake/libbson-1.0:
libbson-1.0-config-version.cmake libbson-1.0-config.cmake
mongo-embedded-sdk-4.0.4/lib/cmake/libmongoc-1.0:
libmongoc-1.0-config-version.cmake libmongoc-1.0-config.cmake
mongo-embedded-sdk-4.0.4/lib/pkgconfig:
libbson-1.0.pc libmongoc-1.0.pc
mongo-embedded-sdk-4.0.4/share:
doc mongo-c-driver
mongo-embedded-sdk-4.0.4/share/doc:
mongo_embedded mongoc_embedded
mongo-embedded-sdk-4.0.4/share/doc/mongo_embedded:
LICENSE-Community.txt LICENSE-Embedded.txt THIRD-PARTY-NOTICES
mongo-embedded-sdk-4.0.4/share/doc/mongoc_embedded:
LICENSE-Community.txt LICENSE-Embedded.txt
mongo-embedded-sdk-4.0.4/share/mongo-c-driver:
uninstall.sh
When I installed it from a package I just had to run
dbPath="/home/pi/app/mongodb_data"
mongod --dbpath "$dbPath" &
Question:
How can I launch the MongoDB to listen on a port?
The tutorial you have followed is for building MongoDB as a library to embed in your application (aka MongoDB Mobile). This embedded build does not provide a standalone server daemon (mongod); you have to link this library directly into your application. The output of the embedded SDK build is the required development header files (include/*.h) and compiled library files (lib/*.so).
For more context, see the original blog post related to the repo you found: Embedded MongoDB 4.0 on Raspberry Pi.
How can I launch the MongoDB to listen on a port?
This requires a build of the normal MongoDB community server. You could try to follow the server build instructions on Build MongoDB from source or look for a precompiled binary for your O/S distro.
Note that Raspberry Pi isn't a generally supported target for the server so you will likely encounter some challenges (particularly on 32-bit O/S). The standard MongoDB server is designed to run on 64-bit hardware with more resources than are typical on a Pi.

How to use cam with matlab under Ubuntu16.04

My os is Ubuntu16.04, and Matlab vision is 2015b, I installed OS Generic Video Interface and USB Webcams,and I got this after run imaqhwinfo:
InstalledAdaptors: {'dcam' 'gentl' 'gige' 'linuxvideo'}
MATLABVersion: '8.6 (R2015b)'
ToolboxName: 'Image Acquisition Toolbox'
ToolboxVersion: '4.10 (R2015b)'
but while I run obj = videoinput('linuxvideo',1);preview(obj);I got this:
Error using videoinput (line 233) There are no devices installed for the specified ADAPTORNAME. See IMAQHWINFO.
and I also cannot run webcam:
No webcams have been detected. Please ensure the webcam is connected to the system.
how to solve this ? thanks for your help!

How to compiled native_pgsql in gammu?

I have configured gammurc and gammu --identify is working. But I received error when I do gammu-smsd -c smsdrc
Here the following error :
gammu-smsd: the native_pgsql driver was not compiled in!
When I run gammu-smsd -v it's tell this :
Compiled in Features :
OS Support :
- ALARM
- WINDOWS_SERVICE
- EVENT_LOG
Backend services :
- NULL
- FILES
- ODBC
I'am using windows and pgsql
how do I fix this problem ? and
How do I compiled native_pgsql ?
thanks
You can use ODBC driver instead. It's only driver which works without additional dependencies on Windows.
To have Gammu built with native PostgreSQL driver on Windows, see our compilation instructions. Gammu will automatically search for the libraries in common locations, but you might end up needing to enter POSTGRES_INCLUDE_DIR and POSTGRES_LIBRARY manually in CMake.

openocd **Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED**

I am trying to setup a eclipse development environment to work with stm32f303 nucleo 32 board.
http://www.st.com/en/evaluation-tools/nucleo-f303k8.html
So far, the all the tools seems to be correctly installed and working: I have succefully compiled and started openocd debugger for stm32f4 discovery and when I connect stm32f303 nucleo 32 board and start openocd, the led on the board indicates that it is connected. (I have flashed the board.)
The thing is openocd get lost when I do step by step debugging and this seems related to the message openocd gives me when started (look for bold line):
Open On-Chip Debugger 0.9.0 (2015-05-19-12:09)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
**Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED**
Info : STLINK v2 JTAG v27 API v2 SWIM v15 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.239293
Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints
Does someone know how to fix usb driver in that case, or it is possible that something else cause the problem?
In case you experience this issue on Linux, you have to configure udev rules to work with the device. Find the 99-openocd.rules included with the source distribution of openOCD under Contributions. Connect your ST-Link USB-device and run 'lsusb' from a terminal, it will list something like this:
Bus 004 Device 009: ID 0483:3748 STMicroelectronics ST-LINK/V2
Notice the value behind ID, you want to check the 99-openocd.rules to see if there is a matching entry supporting the device, in the above case it's this one:
# STLink v2
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", MODE="664", GROUP="plugdev"
Copy this file to your /etc/udev/rules.d configuration directory and reboot your machine. Then try debugging again.
The OpenOCD distribution includes some libusb drivers, and recommends to run the zadig.exe tool to activate them. This will solve your problem.
http://zadig.akeo.ie/
As #silverdr mentioned in the comments, disconnecting the device and reconnecting it worked for me.