Produced no output to $stdout.

[Neroone]

Hi,

I am new to PIC microcontrollers and I am trying to write unit tests for PIC18F86K22. I use a xc8 compiler. I found your project using a PIC and xc8 compiler while browsing. I am trying to use ceedling and I have tried to use some of your files and added a simple c file and test file. When I run ceedling test:all on Ubuntu 16.04, I get the following error.
ERROR: Test executable "test_lights.out" failed.

Produced no output to $stdout.
And exited with status: [0] (count of failed tests).
This is often a symptom of a bad memory access in source or test code. and no out.txt is created. Also, in simlog.txt I notice that the program has failed. Can you please help me figure out why I get this error.
Thanks.
testproject.zip

[asanza]

Hi,
I think you test are compiling just fine, they are just not being executed.

Looking into the log of the test fixture (test/support/simlog.txt), it seems that your simulator is not loading the firmware, but I cannot figure out why.

program build/test/TestBuild.elf
Programming target...
Program failed.

Could you just check that the TestBuild.elf file exists, and try to load it manually in the mplab simulator,
may be give you more clues.

[Neroone]

Hi,
The testBuild.elf does exist and I tried running from the mdb command line. The program was not executed.

I tried changing the .elf to .hex in sim_instructions.txt and the out.txt was created this time(with some garbled letters).
and simlog.txt had the following
program build/test/TestBuild.hex
Programming target...
Program succeeded.
run

break unity.c:1168
unity.c:1168 could not be resolved to an address
wait 5000
quit
Stop at
address:0xf0e2

I am still getting the error from ceedling:test all

ERROR: Test executable "test_lights.out" failed.

Produced no output to $stdout.
And exited with status: [0] (count of failed tests).
This is often a symptom of a bad memory access in source or test code.

Any suggestions?

[asanza]

Hi,
Yes a couple of points:

1. break unity.c:1168 was an ugly hack in order to exit the simulator when unity exits.
   I couldn't figure out other way. You can look where is the exit line in your unity.c and
   locate the breakpoint there.

2. Unity (and ceedling) work printing the unit tests data to stdout (which in the microcontroller, or simulator is the serial port.) The file sim_instructions.txt contain following line:

set uart1io.outputfile		test/support/out.txt

Which is a specific configuration for the processor I am using. You should check that the simulator supports uart1io for your processor. (look mplabx settings).

Also the processor should be configured in order to redirect stdout to the serial port for the printf functions to work. I did that in the files support_uart.c. There are two functions, first the putchar function that is needed for stdout redirection ( I don't remember if there is other thing you need, so check it in the stdout redirection section of the compiler documentation), and the init_uart function which configures the processor registers. This Init_uart should be called after each test (in thet setUp functions).

[Neroone]

Thank you so much for your help. I was able to it to program the target. My extended instruction set had to be turned off. So that works. I am not able to get the UART output. 1. The PIC18F86K22 does have two UARTs. and I run it on Ubuntu 16.04. So the lines set uart1io.uartioenabled true set uart1io.output file set uart1io.outputfile test/support/out.txt seems correct. 2. I have impllemented both putch() and support_init_uart() *code for support_uart.c file* that I modified for my PIC. void putch(char data) { while ( !TXIF) continue; TXREG = data; } *3. When I run ceedling test:all I get the error* *ERROR: Test executable "test_lights.out" failed.*

*Produced no output to $stdout.* And exited with status: [0] (count of failed tests). This is often a symptom of a bad memory access in source or test code.

Now the *out.txt shows up* and I only use TestBuild.elf now and is populated but I get no test summary on the command line and rake is aborted. *4. And when I look at the simlog.txt I see the following error message.* break unity.c:1184 unity.c:1184 could not be resolved to an address wait 5000 quit Stop at address:0xf0c0 file:/home/usha/Software/SoftVueTest4/test/support/support_uart.c source line:59 *The line 59 is while ( !TXIF).* I am not able to figure out what is failing now as there is no output on the command line with the Test Summary. I have also attached all the files that I am using. *Thanks again,* *Usha*

…

On Sat, Nov 4, 2017 at 1:48 PM, Diego Asanza ***@***.***> wrote: Hi, Yes a couple of points: 1. break unity.c:1168 was an ugly hack in order to exit the simulator when unity exits. I couldn't figure out other way. You can look where is the exit line in your unity.c and locate the breakpoint there. 2. Unity (and ceedling) work printing the unit tests data to stdout (which in the microcontroller, or simulator is the serial port.) The file sim_instructions.txt contain following line: set uart1io.outputfile test/support/out.txt Which is a specific configuration for the processor I am using. You should check that the simulator supports uart1io for your processor. (look mplabx settings). Also the processor should be configured in order to redirect stdout to the serial port for the printf functions to work. I did that in the files support_uart.c. There are two functions, first the putchar function that is needed for stdout redirection ( I don't remember if there is other thing you need, so check it in the stdout redirection section of the compiler documentation), and the init_uart function which configures the processor registers. This Init_uart should be called after each test (in thet setUp functions). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfuA1J805oKcehOaDU94hmDKABTqQ7UZks5szKOBgaJpZM4QNKqf> .