Serialization problem using OpenWRT on mips board as application part.

RE: Serialization problem using OpenWRT on mips board as application part.

Alan Klimala — Wed, 16 Sep 2020 07:02:59 GMT

Will docker config file be enough? If so then here you go:

FROM ubuntu:latest

MAINTAINER Alan Klimala <a.klimala@mbdsoft.pl>

# Get neccessary dependencies
#############################
RUN apt-get update -qq &&\
    apt-get install -y \
		bash \
		bc \
		binutils \
        build-essential \
		bzip2 \
        curl \
		cpio \
        file \
        gawk \
		gcc \
		g++ \
        gettext \
        git \
		gzip \
        libncurses5-dev \
        libssl-dev \
		make \
		mercurial \
		nano \
		ninja-build \
		patch \
		perl \
        python2.7 \
        python3 \
        rsync \
		sed \
        subversion \
        sudo \
        swig \
		tar \
        unzip \
        wget \
        zlib1g-dev \
        && apt-get -y autoremove \
        && apt-get clean \
        && rm -rf /var/lib/apt/lists/*

# Compile OpenWRT build environment
###################################
WORKDIR /
RUN git clone https://github.com/openwrt/openwrt.git
WORKDIR /openwrt
RUN ./scripts/feeds update -a \
	&& ./scripts/feeds install -a
COPY ./menuconfig.config /openwrt/.config
ENV FORCE_UNSAFE_CONFIGURE=1
RUN make

# Compile vcpkg tool from Nordic Semiconductor
##############################################
WORKDIR /home
RUN git clone https://github.com/NordicPlayground/vcpkg.git 
WORKDIR /home/vcpkg 
RUN ./bootstrap-vcpkg.sh \
	&& ./vcpkg integrate install \
	&& ./vcpkg install sdl2 curl asio catch2 \
	&& ./vcpkg install --head spdlog
ENV VCPKG_ROOT=/home/vcpkg
ENV PATH=$VCPKG_ROOT:$PATH
RUN echo "set(CMAKE_C_COMPILER mipsel-openwrt-linux-musl-gcc)" >> ./triplets/x64-linux.cmake
RUN echo "set(CMAKE_CXX_COMPILER mipsel-openwrt-linux-musl-g++)" >> ./triplets/x64-linux.cmake
	
# Register OpenWRT SDK
#############################
ENV STAGING_DIR=/openwrt/staging_dir
ENV TOOLCHAIN_DIR=$STAGING_DIR/toolchain-mipsel_24kc_gcc-8.4.0_musl
ENV LDCFLAGS=$TOOLCHAIN_DIR/usr/lib
ENV LD_LIBRARY_PATH=$TOOLCHAIN_DIR/usr/lib
ENV PATH=$TOOLCHAIN_DIR/bin:$PATH
#ENV CC=mipsel-openwrt-linux-gcc
#ENV CXX=mipsel-openwrt-linux-g++

# Prepare libnrf package
##################################
#WORKDIR /home
#RUN mkdir -p packages/libnrf
#COPY ./pc-ble-driver/Makefile /home/packages/libnrf/Makefile
#WORKDIR /openwrt
#RUN cp ./feeds.conf.default ./feeds.conf \
#	&& echo "src-link vemmio /home/packages" >> feeds.conf
#RUN ./scripts/feeds update -a \
#	&& ./scripts/feeds install -a

# Uncomment below if you want 
# to have libNRF built.
##################################
#WORKDIR /home/packages/libnrf
#RUN rm Makefile && \
#	git clone https://your-link-to-pc-ble-driver .
#COPY ./pc-ble-driver/Makefile /home/packages/libnrf/Makefile
#WORKDIR /openwrt
#COPY ./libnrf_menuconfig.config /openwrt/.config
#RUN make

WORKDIR /home
CMD ["bash"]

RE: Serialization problem using OpenWRT on mips board as application part.

kasiviswanathan — Thu, 03 Sep 2020 16:06:02 GMT

Hi Alan Klimala

I am also trying to do exactly the same but ran into an issue while compiling pc-ble-driver for x86_64 itself.

Can you pls share the steps which you used to cross compile pc-ble-driver for mips based board which could be run on openwrt ?

Thanks in advance,

Kasiviswanathan.V

RE: Serialization problem using OpenWRT on mips board as application part.

Kenneth — Thu, 23 Apr 2020 11:12:09 GMT

Hmm.. have you also looked at an oscilloscope to check the length of start and stop bits on UART?

Best regards,
Kenneth

RE: Serialization problem using OpenWRT on mips board as application part.

Alan Klimala — Wed, 22 Apr 2020 14:23:07 GMT

Hello Kenneth,

Thank you for your attention. Yes, I have doube checked power and wiring conditions. Hardware flow control is disabled by software. I have also compared data send between boards when using PCA10040 bassed application and OpenWRT based one and it seems like heart rate monitor examples send completely different data. I have attached serial analyzer output for both cases. pc-ble-driver based example sends six times such a frame:

While PCA10040 based app example sends to connectivity board data as follows:

Of course in a second example we have much more different frames as well as connectivity board responses, but event when looking at the begining one we can see there is some major difference.

RE: Serialization problem using OpenWRT on mips board as application part.

Kenneth — Wed, 22 Apr 2020 11:41:42 GMT

Have you checked the electrical connection by logic analyzer, for instance that you have a common GND wire, that VDD is same voltage, and that the UART pins are properly connected?

Also, how have you connected the flow control lines here? Have you disabled them in software, or have you just added pull down's on CTS and RTS pins to make the UART seem like it is always ready to receive data?

Have you connected an logic analyzer trace on the UART pins to compare working and failing setup? I would assume default the example is setup to use 115200baud, but I assume you have re-compiled the application here.

Best regards,
Kenneth