Need a little help/advice on PanelDUE on coding it

JoergS5

@vlad Hi, you could put a hardware debugger/analyzer between Paneldue and Duet following the procedure of https://github.com/technik-gegg/SMuFF-Ifc

A Former User

@vlad chapter 12 may help http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-6500-32-bit-Cortex-M3-Microcontroller-SAM3S4-SAM3S2-SAM3S1_Datasheet.pdf (although, at a glance there doesnt appear to be a dedicated debug header onboard)

JoergS5

@bearer JTAG seems to be not completely exposed on the Duet: https://forum.duet3d.com/topic/6023/using-jtag-with-the-duet-wifi so it may be impossible to use it. But I did not try yet.

dtpteunissen

@bearer and @JoergS5 i'm also looking for a way to debug the firmware while running it on the LCD. I'm having a hard time to find any schematics for PanelDue 5i.
Any pointers to where i could find those?

With a schematic i can figure out how to connect a debugger to the screen.

A Former User

Yeah, at a glance it seemed like neither jtag or serial debug wire was brought out to a header, but i didn't crossrefrence all the pins against the schematic, left as an excercie for the reader sort to speak.

A Former User

@dtpteunissen said in Need a little help/advice on PanelDUE on coding it:

I'm having a hard time to find any schematics for PanelDue 5i.

Havent seen, but I can't image they're very different to the v3 board https://raw.githubusercontent.com/dc42/PanelDue/master/PCB/V3.0/PaneDue-3.0-schematic.png

Between the code and the board should be doable to work out any major differences if any.

dc42

@bearer said in Need a little help/advice on PanelDUE on coding it:

@dtpteunissen said in Need a little help/advice on PanelDUE on coding it:

I'm having a hard time to find any schematics for PanelDue 5i.

Havent seen, but I can't image they're very different to the v3 board https://raw.githubusercontent.com/dc42/PanelDue/master/PCB/V3.0/PaneDue-3.0-schematic.png

Between the code and the board should be doable to work out any major differences if any.

The schematic for the SAM4S part of the PanelDue 5i and 7i is identical to the non-integrated version.

dtpteunissen

@dc42 said in Need a little help/advice on PanelDUE on coding it:

@bearer said in Need a little help/advice on PanelDUE on coding it:

@dtpteunissen said in Need a little help/advice on PanelDUE on coding it:

I'm having a hard time to find any schematics for PanelDue 5i.

Havent seen, but I can't image they're very different to the v3 board https://raw.githubusercontent.com/dc42/PanelDue/master/PCB/V3.0/PaneDue-3.0-schematic.png

Between the code and the board should be doable to work out any major differences if any.

The schematic for the SAM4S part of the PanelDue 5i and 7i is identical to the non-integrated version.

Thank you for the info. I checked the schematic, and its not possible to connect a JTAG or SWD debugger to the microcontroller since the needed pins are also connected to the LCD.

dc42

Actually it's not impossible. PB6/SWDIO goes to X4 the expansion connector, so it's free. PB7/SWCLK goes to RST on the LCD connector, so you could cut that trace and connect to it. The LCD may not need the reset signal, but if it does you could add a push button. You would need to modify the startup code not to program the bus matrix to use those pins as GPIO.

But I've never had to resort to a debugger when developing PanelDue code.

Vlad

@dc42 @bearer thank you guys. Quite a bit to digest now!

dtpteunissen

@dc42 said in Need a little help/advice on PanelDUE on coding it:

Actually it's not impossible. PB6/SWDIO goes to X4 the expansion connector, so it's free. PB7/SWCLK goes to RST on the LCD connector, so you could cut that trace and connect to it. The LCD may not need the reset signal, but if it does you could add a push button. You would need to modify the startup code not to program the bus matrix to use those pins as GPIO.

But I've never had to resort to a debugger when developing PanelDue code.

I was considering that as well, but i'm a bit hesitant about modifying the PCB by cutting traces.

But this helped! Thanks