User Activity

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Hi MMS The <qpc|qpcpp>/test/ example does not have a posix makefile to show how to build for posix. Thus, I have been trying to build /qp/qpcpp/examples/qutest/dpp/test_dpp with -DQ_UTEST=0 ld flag. The build keep failing, I have tried both: QP_PORT_DIR := $(QPCPP)/ports/posix-qutest and QP_PORT_DIR := $(QPCPP)/ports/posix ports. with the error below</qpc|qpcpp> When liking with posix-qutest QP_PORT_DIR := $(QPCPP)/ports/posix-qutest .o <command-line>: warning: "Q_UTEST" redefined <command-line>:...

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    That what I thought. I got confused reading this post linked below, about the timestamp. you stated: "Instead, the formatting of timestamps is represented as the TCL array $theFmt(tstamp)." https://sourceforge.net/p/qpc/discussion/668726/thread/feec2b7f/?limit=25#92e7

  • Modified a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Hi MSM From what I understand the QSPY timestamp is based on Tcl associative array and the size is define with QS_TIME_SIZE ? On my project QS_TIME_SIZE is 4, what is the best way to get human readable timestamp from the output? or is the timestamp just a timer-counter? Thanks Eddie

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Hi MSM From what I understand the QSPY timestamp is based on Tcl associative array and the size is define with QS_TIME_SIZE ? On my project QS_TIME_SIZE is 4, what is the best way to get human readable timestamp from the output? Thanks Eddie

  • Modified a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Hi Miro Thanks for the fast response. I tried the new update and got this out put _port.o build_posix/qstamp.o -lpthread set -e; while true; do \ echo "restarting build_posix/test_dpp"; \ build_posix/test_dpp "" 192.168.0.7:6601; \ done restarting build_posix/test_dpp <TARGET> ERROR cannot resolve host Name=:6601,Err=-2 <TARGET> ERROR invalid TCP socket restarting build_posix/test_dpp <TARGET> ERROR cannot resolve host Name=:6601,Err=-2 <TARGET> ERROR invalid TCP socket which is not correct. this...

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Hi Miro Thanks for the fast response. I tried the new update and got this out put _port.o build_posix/qstamp.o -lpthread set -e; while true; do \ echo "restarting build_posix/test_dpp"; \ build_posix/test_dpp "" 192.168.0.7:6601; \ done restarting build_posix/test_dpp <TARGET> ERROR cannot resolve host Name=:6601,Err=-2 <TARGET> ERROR invalid TCP socket restarting build_posix/test_dpp <TARGET> ERROR cannot resolve host Name=:6601,Err=-2 <TARGET> ERROR invalid TCP socket which is not correct. this...

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    to run the test I'm using the instructions provided in the make make_posix file make -f make_posix HOST=192.168.1.65:6601 # examples of invoking this Makefile: # make -f make_posix # make and run the tests in the current directory # make -f make_posix HOST=192.168.1.65:6601 # make and run the executable # make -f make_posix norun # only make but not run the tests # make -f make_posix clean # cleanup the build From the make print out it looks like HOST=192.168.1.65:6601 is being ignored as qutest...

  • Posted a comment on discussion Free Support on QP Real-Time Embedded Frameworks & Tools

    Yes, I used it as a guide.

View All

Personal Data

Username:
eddie1066
Joined:
2021-07-22 16:36:57

Projects

  • No projects to display.

Personal Tools