| Age | Commit message (Collapse) | Author |
|---|
|
vsnprintf is a common string function that could be used in many places.
Using both vsnprintf in libc and vsnprintf in the RTT could make a
bigger image. Moreover, if newlib is not enabled when compiling with
GCC, referencing vsnprintf will lead to link error:
.../arm-none-eabi/lib/armv7-ar/thumb/softfp/libc.a(lib_a-sbrkr.o):
In function `_sbrk_r':
sbrkr.c:(.text._sbrk_r+0xc): undefined reference to `_sbrk'
collect2: error: ld returned 1 exit status
Using rt_vsnprintf could avoid such problem.
|
|
finsh: unregister rx_indicate when closing the device
|
|
Because the device could still remain opened when closed by finsh, the
old rx_indicate is useless for finsh. Some buggy driver will still
generate rx_indicate even after the device has been closed. So FinSh
should unregister the rx_indicate when releasing the old device.
|
|
|
|
|
|
|
|
|
|
|
|
rt_event_recv: add a check on the option flag
|
|
Simulator
|
|
Either RT_EVENT_FLAG_AND or RT_EVENT_FLAG_OR should be set in the option
flag. If none of them is present, the waiting thread will never be
resumed.
|
|
|
|
|
|
This gives ways for bsp to set it's own RTT_CC.
|
|
|
|
|
|
Building is only the first step. Correctness is what we need. There are
already many GCC builds for other bsp so GCC building for simulator is
not important. So I use clang-analyze to check all the source codes in
simulator project. Hope it will help us.
|
|
When CROSS_TOOL or 'RTT_CC' env is setted to 'clang-analyze', it will
use Clang to check the codes.
|
|
Bsps can use the clang analyzer as a tool:
env = Environment(toolpath=[os.path.join(RTT_ROOT, 'tools',
'tools')], tools = ['clang-analyze'])
When building the project, the static analyzer will be called to check
all the C code. The warnings are print to stderr.
|
|
The `clang -fsyntax-only` will give us additional warning messages in
the console.
|
|
Simulator get it's way to Travis CI ready.
|
|
This could not only make a cleaner SConstruct, but could also benefit
RTGUI building.
|
|
sim/posix: move rt_hw_context_switch_interrupt after it's definition
|
|
This fix a compile error in Clang.
|
|
stm32f10x: fix the rtgui initialization
|
|
The rtgui_system_server_init prototype is wrong. And if we use
RT_USING_COMPONENTS_INIT, there is no need to call
rtgui_system_server_init again.
|
|
log_trace: cleanup
|
|
|
|
finsh: use alias in the variable definition
|
|
Simulator linux
|
|
With this patch, one could define two alias for the same function like:
FINSH_FUNCTION_EXPORT_ALIAS(rt_hw_cpu_reset, reboot, reboot the cpu);
FINSH_FUNCTION_EXPORT_ALIAS(rt_hw_cpu_reset, __cmd_reboot, reboot the cpu);
Suitable for being used in MSH/Finsh.
|
|
SDL may use DFS to open files. It should be run after
rt_components_init.
|
|
rt_hw_sdl_start should wait untill the rtgui_graphic_set_device is
called int the sdl_loop. Use pthread_cond_wait to achieve this in Linux.
|
|
Some fix for the portal device
|
|
When forwarding rx/tx callback from the underlaying device(pipe), the
"dev" argument should be the portal. So the portal callback could think
itself as called.
|
|
It does not make sense to open portal without a flag. One should open a
portal with RT_DEVICE_OFLAG_RDWR in most cases.
|
|
finsh/cmd: add description for new pipe and portal device
|
|
|
|
Portal device
|
|
Portal is a device that connect devices. Currently, you can only connect
pipes in portal. Pipes are unidirectional. But with portal, you can
construct a bidirectional device with two pipes.
|
|
Pipe have many differences with char device. The main difference is
altough pipe have both read and write, it is unidirectional in nature.
|
|
Ringbuffer and Pipe
|
|
|
|
Some reader(FinSh again) would like to block on a semaphore which is
released in rx_indicate. So we should invoke rx_indicate in
_rt_pipe_resume_reader.
|
|
The previous implementation will always blocks the reader/writer.
However, at least FinSh would expect the device to be nonblocking ---
read should return 0 when there is no data in it.
|
|
Add the APIs that will discard the old data when rb is full.
|
|
RT_RINGBUFFER_SIZE could mean "the size of the whole buffer", "the size
of the empty space" or "the size of the data". Moreover, it's never a
micro anymore. Change it to rt_ringbuffer_data_len before it's too late.
Also, RT_RINGBUFFER_EMPTY is changed to rt_ringbuffer_space_len.
|
|
|
|
device/pipe: add rt_pipe_{init,detach}
|
|
|
