Hi!

I have a issue with PanelDue. I'm using 3.2 firmware version but I suspect that older firmwares also have the same issue.

Sometimes after reset touchscreen doesn't work at all. I tried to reset LCD plenty of time but it still happen(reset button, not power). I assumed that PanelDue is broken but I tried to reproduce it on second LCD and this issue still exist.
Only solution to make it work is power reset.

Then I released that the printed case is touching a touchscreen all the time. So if something is touching the screen and you reset the screen - touchscreen won't respond.

I prepared instructions and movie how to reproduce it
(https://youtu.be/uh4lXjrA4ks)

• put you finger or two on the touchscreen (all the time)
• in this same time click reset button
• after reset touchscreen won't respond at all

I've started diggind what is going on. It looks that ATSAM microcontroller works fine, but something is wrong with SSD1963. I tried to find schematic, but I found only old version when main microcontroller and display were seperate.

@reahax Did you try replace sd card? I compiled (I hope correct version) firmware and checked map file. According to stack in you M122 the issue is reading blocks.

@pavelsplavel
Turn on board -> put jumper on erase pins -> press restart button -> pull off jumper -> press restart button one more time.

After that procedure I hope the microcontroller will erased. If not check your jumper and reset button

Hi!

You have very old firmware (1.x). This is the reason why your script doesn't work. It is dedicated to newest firrmware (3.x) so you need to upgrade. I prefer use Bossa and USB cable
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

@Phaedrux internal SD card works great but external SD has issues.

PanelDue is not problem in this case.

I enabled debugPrint in CoreNG and M111 S1 P10 (Storage) in order to find bug.

This log below is while simulating and refreshing DWC (sd_mmc errors)

Read 1 1 97118<LF>
Read 1 1 97119<LF>
Read 1 1 9508<LF>
Read 1 1 97120<LF>
Read 1 1 97121<LF>
Read 1 1 97122<LF>
Read 1 1 97123<LF>
Read 1 1 97124<LF>
Read 1 1 97125<LF>
Read 1 1 97126<LF>
Read 1 1 97127<LF>
Read 1 1 9508<LF>
Read 1 1 97128<LF>
Read 1 1 97129<LF>
Read 1 1 97130<LF>
Read 1 1 97131<LF>
Read 1 1 97132<LF>
Read 1 1 97133<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 35840<LF>
Read 1 1 97134<LF>
Read 1 1 97135<LF>
Read 1 1 9508<LF>
Read 1 1 97136<LF>
Read 1 1 97137<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 35968<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 41088<LF>
Read 0 4 36096<LF>
Read 0 4 41216<LF>
Read 0 4 36100<LF>
sd_mmc_spi_adtc_start: cmd 12, arg 0x00000000, R1 timeout<LF>
<CR>sd_mmc_spi_adtc_start: cmd 12, arg 0x00000000, R1 timeout<LF>
<CR>Read 0 4 41220<LF>
Read 1 1 97138<LF>
Read 1 1 97139<LF>
Read 1 1 97140<LF>
Read 1 1 97141<LF>
Read 1 1 97142<LF>
Read 1 1 97143<LF>
Read 1 1 9508<LF>
Read 1 1 97144<LF>
Read 1 1 97145<LF>

I figured out that ctrl_access.c is vulnerable and two task might have access in the same time so there can be a race condition.

I also noticed that there is support for FreeRTOS but is disabled by default. I enabled FreeRTOS from FreeRTOS project and now it works flawlessly.

I'm testing this solution on my desk now, but I looks promising.
Now I can simulating and refreshing in the same time and I works stable. I can even upload files on internal SD card during simulating from external SD card - it takes a bit longer but it is still stable.

I did this modyfication on 2.05 firmware.

@droftarts
Yes, I posted about this issue
https://forum.duet3d.com/topic/21264/firmware-restart-while-refreshing-dwc-and-pausing

and confirmation
https://forum.duet3d.com/topic/21489/known-issue-unsafe-to-use-external-sd-card-slot

@alankilian
In M122 you have more precise information:

Stack: 0041f9c3 00459a3c 610f0200 3f800000 3d7df000 3edb6db7 b61cf800 49742404 3c3fdc9b 440739fd 40e190bc 0000bb9b 00000000 3e4fa932 41ddae4f 4e64e1c0 38533333 3f800000 3f800000 20000011 00000000 00000001 00000000 00000000 20002544 00000001 0041f9c3

Next step is download file with map file. You need to do it for your board and firmware version.
In your case it is this zip file https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Symbols-RepRapFirmware-Duet2.zip

There is .map file which include functions addresses in memory.
Then you need to compare your stack address and map file function address.

@droftarts
I haven't merged it yet but I'm going to pull request soon if you don't mind.

@robbe21 Ok, that's weird.
Can you post M122 anyway?

@robbe21
Did you try to replace endstop?

While homing Y axis try to put M122 in DWC console and put here output

@robbe21
Do you get any error/warning in DWC Console?

@robbe21 Hi!
We need your config.g and home#.g files

@alankilian
In M122 you have more precise information:

Stack: 0041f9c3 00459a3c 610f0200 3f800000 3d7df000 3edb6db7 b61cf800 49742404 3c3fdc9b 440739fd 40e190bc 0000bb9b 00000000 3e4fa932 41ddae4f 4e64e1c0 38533333 3f800000 3f800000 20000011 00000000 00000001 00000000 00000000 20002544 00000001 0041f9c3

Next step is download file with map file. You need to do it for your board and firmware version.
In your case it is this zip file https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Symbols-RepRapFirmware-Duet2.zip

There is .map file which include functions addresses in memory.
Then you need to compare your stack address and map file function address.

@flyingpig507
Hi!
Did you have similar issue before?
According to stack trace it looks like some sd card issue.
Let's replace this sd card.

@peta This path doesn't look good

@danielmar90

I think it is correct microcontroller.
Manufacturer number is ok, number of pins also.

@T3P3Tony Am I right?

@danielmar90
I'm from Poland so I can't help you but I thing there is someone who can

There is repair community so you can ask someone
https://forum.duet3d.com/topic/13875/community-repairs

@danielmar90

Hard to predict what happend but maybe some fan, heater short.
If you have warranty you don't need to worry but you need to wait for @Phaedrux.

If you don't have warranty you must replace microcontroller but it is very hard to do.

I can do it if you want but it depends which country you are.