ERROR(CMD16-TAD59-NAL63): ! Failed to load "helloWorld.axf"

Hi Balerion

Glad to hear that you can now access the peripherals via the debugger :)

It is puzzling that you can read/write the clock manager block from C code, but only read (and not write) the UART.

Peripheral registers are sometimes sensitive to the width of the memory access by the processor.  For example, a 32-bit peripheral register might only be accessible with 32-bit read/write instructions (LDR/STR), and 8/16/64-bit accesses won't work.

Sorry, I don't know the size of the UART registers in your hardware, or whether they have access size constraints like this.  Suggest you check which load/store instructions are being generated when you compile your code.  You can do this by setting a breakpoint in your code just before you try to write to the UART, then open the Disassembly view.  You can then single-step at assembly level through the code (press F10 to toggle between single-stepping at instruction level and source-code level) and check whether it is working correctly.

If the UART registers are sensitive to the width of the memory access by the processor, then you might need a cast in your C code to force a particular access size load/store instruction to be generated, e.g. "*(short *)" for 16-bit LDRB/STRB.

As I mentioned before, you can also use the Debugger CLI to force a particular access size read/write, which can be useful for testing.

Also check that you have marked the peripherals as "volatile" in your C code.

Stephen

Hi Balerion

Glad to hear that you can now access the peripherals via the debugger :)

It is puzzling that you can read/write the clock manager block from C code, but only read (and not write) the UART.

Peripheral registers are sometimes sensitive to the width of the memory access by the processor.  For example, a 32-bit peripheral register might only be accessible with 32-bit read/write instructions (LDR/STR), and 8/16/64-bit accesses won't work.

Sorry, I don't know the size of the UART registers in your hardware, or whether they have access size constraints like this.  Suggest you check which load/store instructions are being generated when you compile your code.  You can do this by setting a breakpoint in your code just before you try to write to the UART, then open the Disassembly view.  You can then single-step at assembly level through the code (press F10 to toggle between single-stepping at instruction level and source-code level) and check whether it is working correctly.

If the UART registers are sensitive to the width of the memory access by the processor, then you might need a cast in your C code to force a particular access size load/store instruction to be generated, e.g. "*(short *)" for 16-bit LDRB/STRB.

As I mentioned before, you can also use the Debugger CLI to force a particular access size read/write, which can be useful for testing.

Also check that you have marked the peripherals as "volatile" in your C code.

Stephen

Hi Stephen, 

Thanks for your response. I am currently able to RW to peripherals. That is why I wanted to send a byte from Uart0. I configured its baud rate, parity, stop bit and fifos. Then, I tried to send data from uart but there occured a problem. In console it says "NCONT ERROR in ACK for access 0: ACK = 0x01" Since, I programmed my qspi flash with .jic file which contains .sof and .hex(First stage bootloader) that is why u-boot is writing something from uart0 to my terminal. I don't know what the problem here is. Do you have any idea about it?

Best Regards,

Balerion.

Hi again,

Sorry, I have no knowledge of the peripherals on the Intel platforms.  You'll need to ask on the Intel forums.

Stephen

Hi Stephen, 

Thanks for everything. This post can be marked as solved.

Best Regards,

Balerion