Hi Tim,
Try to enable the debug in the menuconfig:
Build Setup --->
Debug Options --->
[*] Enable Debug Features
[*] Enable Error Output
[*] Enable Warnings Output
[*] Enable Informational Debug Output
[*] CAN Debug Features
[*] CAN Error Output
[*] CAN Warnings Output
[*] CAN Informational Output
BR,
Alan
On 5/7/21, Tim <t...@jti.uk.com.invalid> wrote:
> Hi,
>
>
>
> SAMA5D27 (custom board) - trying to complete the port and also check that
> the CAN interface works on the board, so I'm trying to use the CAN example
> app.
>
>
>
> The drivers appear to be registered (I see /dev/can0 and /dev/can1) but the
> CAN example app crashes when trying to open /dev/can0 and I can't see why.
>
>
>
> I am hindered in debugging this fully as yet since:
>
>
>
> a. I am new to Nuttx and haven't yet sussed how to enable any low level
> debug-type stuff (I have used menuconfig to enable anything that seems to
> be
> related but I'm sure I missed stuff)
> b. I haven't yet coerced my Eclipse IDE (under Windows 10, but code
> configured and compiled using Windows WSL) to "see" the source code
> properly
> to enable me to insert breakpoints (Segger J-link). Not wedded to Eclipse,
> but it is a known entity for me and at least downloads/runs/debugs the
> board!)
>
>
>
> Can anyone point me in the direction of why, or a way to find out why, the
> call to open the device would crash the board rather than return an error?
> Other devices (such as Flexcom USARTs open OK and work - well, after I
> fixed
> some arch issues for Flexcoms on the SAMA5 anyway!!). The board-specific
> code (sam_can.c) I am using is based on the code for the sama5d2-xult board
> and seems pretty trivial, and largely similar to many other architectures
> and boards.
>
>
>
> Many thanks,
>
>
>
> Tim.
>
>
>
>
