Posts made by Wulfsta

Just want to chime in and say that this is a really cool project, I’m impressed with the work!

@oliof yeah, that’s it. Huge pain to figure that out. I’ll add docs to klipper eventually, but it’s not my priority at the moment. Meanwhile it should be easy enough to figure out by looking at the schematics.

@oliof I posted a script to flash 1LC boards using OpenOCD and a Pi elsewhere on the forum.

I have it working with the following bash script:

SWCLK=25
SWDIO=24
SRST=18

echo "Exporting SWCLK and SRST pins."
echo $SWCLK > /sys/class/gpio/export
echo $SRST > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio$SWCLK/direction
echo "out" > /sys/class/gpio/gpio$SRST/direction

echo "Setting SWCLK low and pulsing SRST."
echo "0" > /sys/class/gpio/gpio$SWCLK/value
echo "0" > /sys/class/gpio/gpio$SRST/value
echo "1" > /sys/class/gpio/gpio$SRST/value

echo "Unexporting SWCLK and SRST pins."
echo $SWCLK > /sys/class/gpio/unexport
echo $SRST > /sys/class/gpio/unexport

echo "Ready for OpenOCD."

openocd -c "adapter driver bcm2835gpio; \\
bcm2835gpio peripheral_base 0xFE000000; \\
bcm2835gpio speed_coeffs 236181 60; \\
adapter gpio swclk $SWCLK; \\
adapter gpio swdio $SWDIO; \\
adapter gpio srst $SRST; \\
transport select swd; \\
set CHIPNAME samc21; \\
source [find target/at91samdXX.cfg]; \\
reset_config srst_only; \\
adapter speed 276; \\
init; \\
reset; \\
reset; \\
at91samd chip-erase; \\
at91samd bootloader 0; \\
program Duet3Bootloader-SAMC21.elf verify; \\
reset; \\
shutdown"

echo "Done."

This is adapted from here.

@dc42 said in Raspberry Pi 4 to Toolboard 1LC with OpenOCD:

@Wulfsta the debug build configuration I have for the Tool1LC is for running without the bootloader. To use it, you would need to remove the bootloader protection, then write it to flash memory via SWD. Then to use the tool board normally again, you would need to reinstall the bootloader, again via SWD. The only tool I have ever done this with is an Atmel ICE. So unless you already have one, I can't recommend this route.

Yeah, if I had one I’d just erase the chip using that… I do wonder why I can’t get OpenOCD working - maybe it’s the frequency or pulse width?

Edit: I should mention that I’m trying to connect under reset as the OpenOCD docs suggest, and still no luck.

@dc42 Could you provide a debug build I can use for this purpose? I don't want to set up all the tooling to build RRF...

@gloomyandy Ah yeah, I saw this page, but didn't have a close enough look at it. Thanks for the help though!

Similarly to this klipper PR, I'm looking for functionality that will correct for frame expansion as a function of temperature.

@gloomyandy I actually have no idea how to do this, and a cursory look at the docs didn't seem to suggest it's well-known; do you happen to have a reference that I could look at, or example of someone doing this? Or at least, a link to where this is located in the OpenOCD docs?

Seeing this thread, I really wish I had spent time making that band-aid test print use a bit less plastic...

@dc42 Aha! I pulled out an old v1.0 of the 1LC, and had no problem connecting to it with the Pi. Is this related to the swdclk pin being used to blink the STATUS LED? I would like to be able to flash any version of the 1LC from a Pi.

@dc42 I've had no luck - I built OpenOCD at the latest commit, and am still seeing the same issue. My only lead is that if I disconnect the swclk line I see the same error - perhaps a pull-up issue or similar hardware configuration I'm missing? Config for the latest version is as follows:

adapter driver bcm2835gpio
bcm2835gpio peripheral_base 0xFE000000
bcm2835gpio speed_coeffs 236181 60
adapter gpio swdio 24
adapter gpio swclk 25
adapter gpio srst 18

transport select swd
 
set CHIPNAME at91samc21g18
source [find target/at91samdXX.cfg]

reset_config srst_nogate
 
adapter srst delay 100
adapter srst pulse_width 100

adapter speed 400

I'd greatly appreciate it if someone with the same hardware could attempt to replicate what I'm seeing.

I'm trying to flash the 1LC using a Pi 4 and OpenOCD 0.11.0, but am seeing the following error:

Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
adapter srst pulse_width: 100

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : clock speed 400 kHz
Error: Error connecting DP: cannot read IDR

When running with -d, I see

...
Debug: 3824 504 bitbang.c:426 bitbang_swd_switch_seq(): bitbang_swd_switch_seq
Debug: 3825 504 bitbang.c:434 bitbang_swd_switch_seq(): JTAG-to-SWD
Debug: 3826 504 bitbang.c:394 bitbang_swd_exchange(): bitbang_swd_exchange
Debug: 3827 504 bitbang.c:457 bitbang_swd_read_reg(): bitbang_swd_read_reg
Debug: 3828 504 bitbang.c:394 bitbang_swd_exchange(): bitbang_swd_exchange
Debug: 3829 504 bitbang.c:394 bitbang_swd_exchange(): bitbang_swd_exchange
Debug: 3830 505 bitbang.c:479 bitbang_swd_read_reg(): JUNK DP read reg 0 = ffffffff
Debug: 3831 505 bitbang.c:507 bitbang_swd_read_reg(): No valid acknowledge: ack=7
Debug: 3832 505 bitbang.c:568 bitbang_swd_run_queue(): bitbang_swd_run_queue
Debug: 3833 505 bitbang.c:394 bitbang_swd_exchange(): bitbang_swd_exchange
Debug: 3834 505 bitbang.c:575 bitbang_swd_run_queue(): SWD queue return value: 07
...

My configuration is as follows:

adapter driver bcm2835gpio
bcm2835gpio_peripheral_base 0xFE000000
bcm2835gpio_speed_coeffs 236181 60
bcm2835gpio_swd_nums 25 24
bcm2835gpio_srst_num 18

transport select swd
 
set CHIPNAME at91samc21g18
source [find target/at91samdXX.cfg]

reset_config srst_nogate
 
adapter srst delay 100
adapter srst pulse_width 100

adapter speed 400

Tried this on two toolboards with different connections, same result. Can anyone help?

New thread here.

New thread for continuation of this issue: @dc42 @T3P3Tony

The replacement board I have is drifting in the same way as the original - any ideas about what the cause might be? I don't believe I'm outside of the operating specs on the documentation page.

I'm seeing this issue on the replacement board. Prior to the first print it measured the same as ambient, two short prints later (around six hours) the measurement is 11 degrees. Do you have any idea what might cause this? No enclosure during these prints, so it seems unlikely to be heat?

@t3p3tony Email sent.

@t3p3tony I get a value of 22.4 Celsius on temp1.

@dc42 As follows:

Sensor 1 (Nozzle) type PT1000 using pin 121.temp0, reading 0.5, last error: success, R:2200.0 L:-14 H:-8

Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.0beta6 (2021-11-06) and Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta6 (2021-11-06 11:56:11)

This is with the PT1000 plugged. If the L and H values look odd (I have no idea what is normal for these), it's due to trying an auto-calibration.

I'm seeing an issue where a known good pt1000 is reading near 0 on temp0 at ambient. Measuring the resistance across the pins yields 3.038 kOhms. This differs from temp1, where the resistance is 2.764 kOhms. I don't see any visible damage to the board - any advice?