Closed guidol70 closed 1 year ago
guidol70
commented
1 year ago @Isysxp for your dsk-images directory a bootable RT-11 V4.00 Image which contains
Isysxp
commented
1 year ago Dear Guido,
Many thanks for this image. There are some bits of FORTRAN missing (FORLIB) and I am not sure which floating point device that your FORTRA.SAV was built to support. Anyway, here is an RT11 v4 with FOCAL/BASIC/FORTRAN that suits the FIS implementation in the Pico code. I hadn't bothered to add this to the repo as most of this stuff is available on web. I did add a MINC image as this is a bit obscure ... and you need a VT105 to run it!!!!! Anyway, here is one of my working copies with all of the various bits and pieces for you to try. There are also some really short test programmes as well. NB DEMOF1 does not work .... this needs some extra components as well. Try FT1.FOR instead!
Hope it all works for you, regards, Ian.
From: Guido Lehwalder @.> Sent: 25 November 2022 11:08 AM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
@Isysxphttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3bc23355c1b84222080b08daced56d93%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049713467648372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xQrrAaktNB1VObnIoZH%2B2k8c3DA%2FoQC%2FQ3LVs7uq1iI%3D&reserved=0 for your dsk-images directory a bootable RT-11 V4.00 Image which contains
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1327340105&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3bc23355c1b84222080b08daced56d93%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049713467804668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hfg8vL3QLacxAjZaV%2FQAdVjvyQU6Bb8xwy6rwaqdGaU%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB7N2WIVNVYQR43TFGDWKCM37ANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3bc23355c1b84222080b08daced56d93%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049713467804668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VvxsG2ooOuLQwAOPODuBfqRVds2LGmBHvl4Tl3WJRs0%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Dear Guido, Many thanks for this image. There are some bits of FORTRAN missing (FORLIB) and I am not sure which floating point device that your FORTRA.SAV was built to support. Anyway, here is an RT11 v4 with FOCAL/BASIC/FORTRAN that suits the FIS implementation in the Pico code. I hadn't bothered to add this to the repo as most of this stuff is available on web. I did add a MINC image as this is a bit obscure ... and you need a VT105 to run it!!!!! Anyway, here is one of my working copies with all of the various bits and pieces for you to try. There are also some really short test programmes as well. NB DEMOF1 does not work .... this needs some extra components as well. Try FT1.FOR instead! Hope it all works for you, regards, Ian. […]
Dear Ian, on the .dsk where I copied FORTRAN from isnt a file named FORLIB :(
I did see the MINC image and also did found the instruction-page about it: https://pdp2011.sytse.net/wordpress/howto/minc-rk05/ and https://pdp2011.sytse.net/wordpress/building-a-rk-minc-disk/
I didnt see an attachment - so could you please recheck and tell me where I could find your working copy ;)
Many Thanks in advance
PS: Thats the Listing from the Fortran-"Source"-image:
.DIR RK1:
SWAP .SYS 27P 02-Sep-87 RT11SJ.SYS 79P 15-Jan-88
RT11XM.SYS 106P 19-Dec-87 DD .SYS 5P 02-Sep-87
DY .SYS 4P 02-Sep-87 LS .SYS 5P 02-Sep-87
SL .SYS 17P 02-Sep-87 TT .SYS 2P 02-Sep-87
VM .SYS 3P 02-Sep-87 DU .SYS 8P 02-Sep-87
LD .SYS 8P 02-Sep-87 DYX .SYS 4P 19-Dec-87
DL .SYS 5 17-Oct-84 LDX .SYS 8P 19-Dec-87
VMX .SYS 3P 19-Dec-87 BAX .SYS 7P 19-Dec-87
DDX .SYS 5P 19-Dec-87 DLX .SYS 5P 19-Dec-87
DUX .SYS 9P 19-Dec-87 LSX .SYS 5P 19-Dec-87
SLX .SYS 20P 19-Dec-87 DIR .SAV 19 02-Sep-87
PIP .SAV 30 02-Sep-87 DUP .SAV 49 02-Sep-87
RESORC.SAV 25 02-Sep-87 KED .SAV 58 02-Sep-87
UCL .SAV 16 02-Sep-87 CREF .SAV 6 02-Sep-87
SRCCOM.SAV 26 02-Sep-87 BASIC .SAV 53 04-Apr-83
MACRO .SAV 61 02-Sep-87 DUMP .SAV 9 02-Sep-87
SYSLIB.OBJ 216 24-Mar-87 FORTRA.SAV 206 24-Mar-87
KERMIT.SAV 182 02-Apr-86 KERMIT.HLP 148 13-Apr-86
FOCAL .SAV 36 30-Nov-84 STARTX.COM 1 28-Mar-99
STARTS.COM 1 28-Mar-88 BASIC .DSK 1000P 28-Mar-98
INFO .TXT 2 28-Mar-88 BAS .SAV 53 04-Apr-83
42 Files, 2532 Blocks
17850 Free blocksDear Guido,
MINC stuff: glad you found it. Sytse has done a lot of work on this and developed a rather cool FPGA system. FORLIB.OBJ seems to be rather hard to get hold of. I think mine is from an RX02 image for an 11/23 system (EIS+FIS and no FPP). It is remotely possible that it might have been from one of my own RX02 floppies. I did back some up a long time ago...... I am intrigued by your image in that I wonder where BASIC.DSK came from???? Also, not sure about FOCAL.SAV ... there are various versions of this ... see disk. FOCALS = single precision floats, FOCALD = double precision and there is also a FOCAL8 (8K) version. See manual: DEC-11-LFOCA-F-D_FOCAL-11_Users_Manual_Sep75.pdf (archive.org)https://ia902305.us.archive.org/8/items/bitsavers_decpdp11laFOCAL11UsersManualSep75_9536714/DEC-11-LFOCA-F-D_FOCAL-11_Users_Manual_Sep75.pdf. These have been built using a software FP and will run on anything eg 11/05.
I suspect that github stripped the attachment. Here is a Googledrive link. https://drive.google.com/file/d/1lQYGWGchnlpxWW3iWP-5wPoNOhH2pvkF/view?usp=share_link
Hope you can download this time, regards, Ian.
From: Guido Lehwalder @.> Sent: 25 November 2022 6:32 PM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Dear Guido, Many thanks for this image. There are some bits of FORTRAN missing (FORLIB) and I am not sure which floating point device that your FORTRA.SAV was built to support. Anyway, here is an RT11 v4 with FOCAL/BASIC/FORTRAN that suits the FIS implementation in the Pico code. I hadn't bothered to add this to the repo as most of this stuff is available on web. I did add a MINC image as this is a bit obscure ... and you need a VT105 to run it!!!!! Anyway, here is one of my working copies with all of the various bits and pieces for you to try. There are also some really short test programmes as well. NB DEMOF1 does not work .... this needs some extra components as well. Try FT1.FOR instead! Hope it all works for you, regards, Ian. […]
Dear Ian, on the .dsk where I copied FORTRAN from isnt a file named FORLIB :(
I did see the MINC image and also did found the instruction-page about it: https://pdp2011.sytse.net/wordpress/howto/minc-rk05/https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpdp2011.sytse.net%2Fwordpress%2Fhowto%2Fminc-rk05%2F&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C0994d728e7434d06496e08dacf1372e8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049979676836170%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hVVSjXmL8RCurzUDNnT%2Fb5r03GThBapkkKxjcr3eTiM%3D&reserved=0 and https://pdp2011.sytse.net/wordpress/building-a-rk-minc-disk/https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpdp2011.sytse.net%2Fwordpress%2Fbuilding-a-rk-minc-disk%2F&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C0994d728e7434d06496e08dacf1372e8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049979676836170%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2F5uX75MbIBgm39dS3t2fiqHyCLiz6c9LzpfMT3yG%2B8s%3D&reserved=0
I didnt see an attachment - so could you please recheck and tell me where I could find your working copy ;)
Many Thanks in advance
PS: Thats the Listing from the Fortran-"Source"-image:
.DIR RK1:
SWAP .SYS 27P 02-Sep-87 RT11SJ.SYS 79P 15-Jan-88
RT11XM.SYS 106P 19-Dec-87 DD .SYS 5P 02-Sep-87
DY .SYS 4P 02-Sep-87 LS .SYS 5P 02-Sep-87
SL .SYS 17P 02-Sep-87 TT .SYS 2P 02-Sep-87
VM .SYS 3P 02-Sep-87 DU .SYS 8P 02-Sep-87
LD .SYS 8P 02-Sep-87 DYX .SYS 4P 19-Dec-87
DL .SYS 5 17-Oct-84 LDX .SYS 8P 19-Dec-87
VMX .SYS 3P 19-Dec-87 BAX .SYS 7P 19-Dec-87
DDX .SYS 5P 19-Dec-87 DLX .SYS 5P 19-Dec-87
DUX .SYS 9P 19-Dec-87 LSX .SYS 5P 19-Dec-87
SLX .SYS 20P 19-Dec-87 DIR .SAV 19 02-Sep-87
PIP .SAV 30 02-Sep-87 DUP .SAV 49 02-Sep-87
RESORC.SAV 25 02-Sep-87 KED .SAV 58 02-Sep-87
UCL .SAV 16 02-Sep-87 CREF .SAV 6 02-Sep-87
SRCCOM.SAV 26 02-Sep-87 BASIC .SAV 53 04-Apr-83
MACRO .SAV 61 02-Sep-87 DUMP .SAV 9 02-Sep-87
SYSLIB.OBJ 216 24-Mar-87 FORTRA.SAV 206 24-Mar-87
KERMIT.SAV 182 02-Apr-86 KERMIT.HLP 148 13-Apr-86
FOCAL .SAV 36 30-Nov-84 STARTX.COM 1 28-Mar-99
STARTS.COM 1 28-Mar-88 BASIC .DSK 1000P 28-Mar-98
INFO .TXT 2 28-Mar-88 BAS .SAV 53 04-Apr-83
42 Files, 2532 Blocks
17850 Free blocks
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1327775565&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C0994d728e7434d06496e08dacf1372e8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049979676992367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WZdea8zkWaqlceOKqrH6z%2FacwquGnIetXeVQl4H%2F49s%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB6ZJZYR6NPELIYFEODWKEA43ANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C0994d728e7434d06496e08dacf1372e8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638049979676992367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zSoj96vRtlc7sEsicR5YeUxbINJWlYqZX6kVWVKDwLs%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Sytse has done a lot of work on this and developed a rather cool FPGA system. I am intrigued by your image in that I wonder where BASIC.DSK came from???? I suspect that github stripped the attachment. Here is a Googledrive link. Hope you can download this time, regards, Ian.
Dear Ian, the BASIC.DSK on the DSK-Image was already there from where I got my BASIC.SAV from. Its from the RL02_0-9.DSK inside the directory /rlc21e/subsets of http://www.pdp11gy.com/neu/rlv28e.zip
Maybe the BASIC.DSK was a "solution" to transfer more than one file into(?) RT-11? When copying a external file via ptr-device (ptr for import or ptp for export)) and then mouting/assign it internally to RT-11 it could be a solution to "transfer" more than one file at a time. see the one-file-solution at https://github.com/bombasticbob/PDP11
copy_file_to_and_from_dsk_image.txt
This archive/page ist from the "pdp11gy" named Reinhard Heuberger, which also does create via FPGA pdp11-replacement-computers and Disk-Emulations - see http://pdp11gy.com/indexE.html
At this time I could download your image. Many Thanks for that. The BASIC seems to be a older version than mine (which is from a v5.04 disk).
Do you have a working Backspave-Key? My putty/TeraTerm Terminal is sending Ctrl-H which doesnt work (but is working in simh under Linux).
BTW: You can safely overclock (like my fork of RunCPM for the pico) the pdp11/40 for a 1/5 power-up when changing set_sys_clock_khz(200000, true) to set_sys_clock_khz(250000, true) in your Pico_1140.cxx (around line 86) ;)
RunCPM (CP/M Emulator) for the Pico: https://github.com/guidol70/RunCPM_RPi_Pico
guidol70
commented
1 year ago @Isysxp Today I did found a RK05-Image with RT-11 v5.04F (5.4F) and its booting on the pdp11/40 Pico :) I copied the programming languages onto the image and they do work. OK - the old BASIC (BASIC V01B-0) from v3/v4 doenst work anymore , but the BASIC-1/RT-11 v2.1 does work like before.
At boot-time the autostart-command R MSCPCK doenst give a output like under simh in Linux:
.R MSCPCK
?MSCPCK-I-MU0-FW Rev Level is 005/HW Rev Level is 001
?MSCPCK-W-TQK50 controller below FW Rev 4/HW Rev 6Do you know where I can change these startup-command like TYPE V5USER.TXT R MSCPCK
V4.x did convert lowercase characters to uppercase at the prompt, but v5.x doenst do that and do work with lowercase. Is there a setting to reactivate the uppercase-mode?
Isysxp
commented
1 year ago Dear Guido,
Firstly, thanks for the V5F disk image. This contains a lot of useful stuff. I reckon that the bit that is missing is the RT11 C compiler and libraries. I suspect that they may be on another volume. I do have a copy somewhere. Anyway, to use C you need lower case input. This is configured in the TT handler derived from TT.MAC. As this is not a system disk, it is not there. So, I assume this disk was built for C development. Also, I think there may be an UC/LC option during a build of V5F. Please note the system responses .... they are in mixed case. For example here is the contents of STARTS.COM
!.MODULE STARTS,03,<BL/SJ Startup command file) ! ! Select the editor of your choice. Take the default (KED) unless you are ! not using a VT100 compatible terminal. If you are using an incompatible ! terminal (or a hard copy terminal) select the following command. ! !SET EDIT EDIT ! ! Get the revision levels of your MU's, if you have them ! R MSCPCK
Note mixed case.......
You can't change the TT handler to upper case but you can just put caps lock on if you wish. The start-up files for RT11 are in START*.COM. S for SJ monitor F for FB X for XM. Edit them as you see fit. MSCPK is an app to display info about MSCP disk controllers. This app doesn't have any.
Regards, Ian.
From: Guido Lehwalder @.> Sent: 27 November 2022 9:10 PM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
@Isysxphttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceaba229183ba4bedb6e008dad0bbcc14%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638051802994849883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ECUoNLy8qrMgW2%2BilY86OVmzIiIXjUhwPCmpGK%2BPkno%3D&reserved=0 Today I did found a RK05-Image with RT-11 v5.04F (5.4F) and its booting on the pdp11/40 Pico :) I copied the programming languages onto the image and they do work. OK - the old BASIC (BASIC V01B-0) from v3/v4 doenst work anymore , but the BASIC-1/RT-11 v2.1 does work like before.
[pdp1140_Pico_RT11_V504f_54f]https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F5121124%2F204158968-9ddb9396-6ad1-4abb-b0b2-d42fbf1bf783.jpg&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceaba229183ba4bedb6e008dad0bbcc14%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638051802994849883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2F5gf9x1SIG9rfPx21RgNg2%2BvLXt8a1uX9mQO%2BguKw18%3D&reserved=0 [RT11_V5_Help_me]https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F5121124%2F204158977-7eb8f8bc-6279-4b79-9611-eae2744c2392.jpg&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceaba229183ba4bedb6e008dad0bbcc14%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638051802994849883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3mY26GKG0OyeeortfqQxbi1OdVsMBM60fXcBGQ%2BWMhg%3D&reserved=0
At boot-time the autostart-command R MSCPCK doenst give a output like under simh in Linux:
.R MSCPCK ?MSCPCK-I-MU0-FW Rev Level is 005/HW Rev Level is 001 ?MSCPCK-W-TQK50 controller below FW Rev 4/HW Rev 6
Do you know where I can change these startup-command like TYPE V5USER.TXT R MSCPCK
V4.x did convert lowercase characters to uppercase at the prompt, but v5.x doenst do that and do work with lowercase. Is there a setting to reactivate the uppercase-mode?
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1328340696&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceaba229183ba4bedb6e008dad0bbcc14%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638051802994849883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EU%2FP%2FwZUVope%2FT9NzToAFPVMxMjqA3rFKT2Pf379RD8%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB2N6OMA5J5IBFWTLSLWKPE33ANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceaba229183ba4bedb6e008dad0bbcc14%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638051802994849883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zJU738P2HGgC3SOp5j8g00O7eYPe8iCnVF2h69NmHxw%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago BTW: a short question at the end... Is it OK when I do get the followinf warning while compiling?:
[ 81%] Building C object CMakeFiles/Pico_1140.dir/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c.obj In function 'gen_numname', inlined from 'dir_register' at /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2573:4: /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2048:15: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] 2048 | ns[i] = '~'; | ~~~~~~^~~~~ /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c: In function 'dir_register': /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2019:14: note: at offset -1 into destination object 'ns' of size 8 2019 | BYTE ns[8], c; | ^~
Dear Ian, while searching for some error-messages while booting and some file-commands I replaced the no-OS-FatFS-SD-SPI-RPi-Pico with the latest commit from the 21th of November. carlk3 moved from FatFS from ff14a to ff15. With that I didnt get the warnings above anymore while compiling Pico_1140 ;)
But with the V4.x and V5.x Disk-Images I do get some messages/warnings/erros from kl/kt/uibus:
Booting file:rt11v400c.dsk
Ready
rk11::read16 invalid read 777460
rk11::read16 invalid read 777440
kl11: read from invalid address 777550
kl11: read from invalid address 777500
Booting file:rt11v504f_54f.dsk
Ready
unibus: read16 from odd address 000001
kl11: read from invalid address 777500
rk11::read16 invalid read 777440
rk11::read16 invalid read 777460
kl11: read from invalid address 777550
.copy v5user.txt v5user.bkp
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000403
unibus: read16 from odd address 000403
.protect v5user.txt
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000403
unibus: read16 from odd address 000403
======================================
.rename /setdate:19:oct:88 SINUS.BAS
To ? SINUS.BAS
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000377
unibus: read16 from odd address 000401
unibus: read16 from odd address 000403
unibus: read16 from odd address 000403
======================================
hang then now after reboot
======================================
.rename /setdate:19:oct:88 SINUS.BAS
To ? SINUS.BAS
.
======================================The messages on boot are every time the same, but sometimes I do get the problem while using file-commands and then the system hang - BUT when I want to retry that after a reboot the file-commands do work :(
I used a 8GB and 32GB Sandisk Ultra (normal SD - 40MB/sec) and a Sandisk 32GB Extreme (MicroSD) with no difference on the boot-messages.
Do you got an Idea about this and why sometimes it will give the messages on file-commands and then hang and sometimes it just work.
On simh on Linux I didnt get these messages (so the images seem to be OK) or is there a special size needed for the RK-Image on the Pico_1140?
BTW: Working Backspace on the V4-image works with "SET TT SCOPE" and sending Ctrl-? (127) with putty for Backspacd (and not Ctrl-H) and got KED working with this new Blog-Entry from "Big Dan"
Kind regards Guido
Isysxp
commented
1 year ago Dear Guido,
This is as I had feared. The new version of FatFS.... compiles fine but this causes disk errors. I would note that the changes between the 2 versions are enormous. I suspect they have got something wrong somewhere. The changes are so extensive that finding any errors is near impossible. I would suggest the using this release is not a good idea.
Further to the errors that are printed, RT11 is searching for additional KL11 and RK11 controllers so these are expected. You can patch these out if you wish. The odd address trap with the V5 disk is expected as there is a TST @#1 instruction at location 1264 in the boot phase. This will cause an odd address trap. Why they would do this I do not know!!!! Things like this can be part of a CPU identification phase.
Personally, fixing warnings in 3rd party code is not really necessary as in this case, it does not cause a problem. And see 79095 – [7 regression] spurious stringop-overflow warning (gnu.org)https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79095 79095 – [7 regression] spurious stringop-overflow warninghttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=79095 The warning is reproducible with the test case below. The memset call is inserted by the loop distribution pass. The pass should avoid inserting memcpy/memmove/memset calls with excessively large arguments (> SIZE_MAX / 2) because they are certainly incorrect and, if executed, will lead to buffer overflow and memory corruption. gcc.gnu.org
Regards, Ian.
From: Guido Lehwalder @.> Sent: 28 November 2022 1:20 PM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
BTW: a short question at the end... Is it OK when I do get the followinf warning while compiling?:
[ 81%] Building C object CMakeFiles/Pico_1140.dir/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c.obj
In function 'gen_numname',
inlined from 'dir_register' at /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2573:4:
/home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2048:15: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
2048 | ns[i] = '~';
| ~~^~~~~
/home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c: In function 'dir_register':
/home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/ff14a/source/ff.c:2019:14: note: at offset -1 into destination object 'ns' of size 8
2019 | BYTE ns[8], c;
| ^~
Dear Ian, while searching for some error-messages while booting and some file-commands I replaced the no-OS-FatFS-SD-SPI-RPi-Pico with the latest commit from the 21th of November. carlk3 moved from FatFS from ff14a to ff15.https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcarlk3%2Fno-OS-FatFS-SD-SPI-RPi-Pico%2Fpull%2F40&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cab164376021742bd44aa08dad143489a%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052384150111338%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=17SQIWuQdjKIjxzl3K0ZNJIFesUVObQ%2BUXfqoXxCXYc%3D&reserved=0 With that I didnt get the warnings above anymore while compiling Pico_1140 ;)
But with the V4.x and V5.x Disk-Images I do get some messages/warnings/erros from kl/kt/uibus:
Booting file:rt11v400c.dsk Ready rk11::read16 invalid read 777460 rk11::read16 invalid read 777440 kl11: read from invalid address 777550 kl11: read from invalid address 777500
Booting file:rt11v504f_54f.dsk Ready unibus: read16 from odd address 000001 kl11: read from invalid address 777500 rk11::read16 invalid read 777440 rk11::read16 invalid read 777460 kl11: read from invalid address 777550
.copy v5user.txt v5user.bkp unibus: read16 from odd address 000377 unibus: read16 from odd address 000401 unibus: read16 from odd address 000377 unibus: read16 from odd address 000401 unibus: read16 from odd address 000403 unibus: read16 from odd address 000403
.protect v5user.txt unibus: read16 from odd address 000377 unibus: read16 from odd address 000401 unibus: read16 from odd address 000377 unibus: read16 from odd address 000401 unibus: read16 from odd address 000403 unibus: read16 from odd address 000403
The messages on boot are every time the same, but sometimes I do get the problem while using file-commands and then the system hang - BUT when I want to retry that after a reboot the file-commands do work :(
I used a 8GB and 32GB Sandisk Ultra (normal SD - 40MB/sec) and a Sandisk 32GB Extreme (MicroSD) with no difference on the boot-messages.
Do you got an Idea about this and why sometimes it will give the messages on file-commands and then hang and sometimes it just work.
On simh on Linux I didnt get these messages (so the images seem to be OK) or is there a special size needed for the RK-Image on the Pico_1140?
BTW: Working Backspace on the V4-image works with "SET TT SCOPE" and sending Ctrl-? (127) with putty for Backspacd (and not Ctrl-H) and got KED working with this new Blog-Entry from "Big Dan"https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbigdanzblog.wordpress.com%2F2022%2F11%2F22%2Fimplementing-vt100-terminal-emulation-with-pidp-11%2F&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cab164376021742bd44aa08dad143489a%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052384150111338%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tA%2BLh4HL86kvmscPUDqIiQZnYBW3B%2FeROkabeJkhZ%2FQ%3D&reserved=0
Kind regards Guido
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1329080468&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cab164376021742bd44aa08dad143489a%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052384150111338%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LcgjiP1Hq9aOZ86LcaY24c10ERNI1p3pzwrMdnOUZKw%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB2JR4HTNQXF65XRQSTWKSWQZANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cab164376021742bd44aa08dad143489a%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052384150111338%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Yh7f%2FMjZqHjvxxis7l6cEkxLG%2F5XWfyD8H%2FpFCwsz3c%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Dear Guido, This is as I had feared. The new version of FatFS.... compiles fine but this causes disk errors. I would note that the changes between the 2 versions are enormous. I suspect they have got something wrong somewhere. The changes are so extensive that finding any errors is near impossible. I would suggest the using this release is not a good idea.
Dear Ian, OK I have to recheck if I do get filesystem-errors with FatFS ff14a or only with the "new" FatFS ff15. I was searching only because of the odd read messages, but when they are expected and not harmful I will go back to FatFS ff14a - also because the RC2040-project (as I inspected the source) also do use the FatFS ff14a First I thought the RC2040-project may use another driver for accessing FAT. Maybe the Author of the RC2040-project has some additional ideas for using FatFS? - because he also did built a Pico-SD-IDE-Interface with ff14a for the RC2014.
For now I will disable printing these messages (in kl.cxx, rk.cxx and unibus.cxx), because many other are also commented out.
Isysxp
commented
1 year ago Dear Guido,
Having found the disk errors, I did some further checks to see if any other things might be a problem. From this, I have corrected some code in kb11.h for the ADC instruction. I haven't re-tested the new FatFS library as yet. But this error does cause some problems when compiling FORTRAN programmes. Specifically, the odd address faults you sent in your previous e-mail. So, please re-sync kb11.h before checking the new FatFS.
Regards, Ian.
From: Guido Lehwalder @.> Sent: 28 November 2022 6:45 PM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Dear Guido, This is as I had feared. The new version of FatFS.... compiles fine but this causes disk errors. I would note that the changes between the 2 versions are enormous. I suspect they have got something wrong somewhere. The changes are so extensive that finding any errors is near impossible. I would suggest the using this release is not a good idea.
Dear Ian, OK I have to recheck if I do get filesystem-errors with FatFS ff14a or only with the "new" FatFS ff15. I was searching only because of the odd read messages, but when they are expected and not harmful I will go back to FatFS ff14a - also because the RC2040-project (as I inspected the source) also do use the FatFS ff14ahttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FExtremeElectronics%2FRC2040%2Ftree%2Fmain%2FFatFs_SPI&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C58bcbbd68bab4d1937b708dad170afb0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052579155576932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=un9i6m3MVTkv6fS5GQoXQMi2NPTn1FZ0h8HAgCULY6I%3D&reserved=0 First I thought the RC2040-project may use another driver for accessing FAT. Maybe the Authorhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FExtremeElectronics&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C58bcbbd68bab4d1937b708dad170afb0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052579155576932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QjQClXsRCUuYf%2FqBPGe82DrCsInPdgVfvADYx%2BizjHI%3D&reserved=0 of the RC2040-project has some additional ideas for using FatFS?
For now I will disable printing these messages, because many other are also commented out.
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1329580698&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C58bcbbd68bab4d1937b708dad170afb0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052579155576932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yhNIN%2FBIpMu1DdJl5Tpk3CBKz%2BbCfwEDCESPyLaqlr0%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB25K3D7OX2FKIOYXJ3WKT4TRANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C58bcbbd68bab4d1937b708dad170afb0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638052579155576932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=k%2Bja0xx5zx%2BPocp6HHq%2FcnX4xHhQaKldYdMHcxs7fl0%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Dear Guido, Having found the disk errors, I did some further checks to see if any other things might be a problem.
So, please re-sync kb11.h before checking the new FatFS.
Dear Ian, I re-synced that kb11.h and now its compiling (with FatFS ff14a) ;) Kin Regards Guido
guidol70
commented
1 year ago I haven't re-tested the new FatFS library as yet.
Dear Ian, if you dont want to use the ff15-version then I have a little present for you ;) I did a compare of the ff.c from ff14a and the ff15 and did create a patched version of the ff14a-version, which didnt give these warnings while compiling.
The content of the .zip should be put in /Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/
The patches file is in the source-directory as ff.c & ff_pacthed.c and the original one is as a copy under the name ff_original.c
Did comile for me without problems - but I cant give a warranty ;)
Kind Regards Guido
Isysxp
commented
1 year ago Dear Guido,
Well, this is an interesting suggestion, The minimal patch is:
Line 2047: while (seq); to while (i && seq);
Firstly, this confirms that the problem is due to GCC and secondly, this is such a small change that I will accept this. I note this change in the new SdFat library. I have to admit that I would not have thought of this!!!! I will add this patch to the repo but I think it is still worth a re-check of the new library with the ADC patch to see if it is OK. If so, I will update the whole library in the repo.
Regards, Ian.
From: Guido Lehwalder @.> Sent: 29 November 2022 9:12 AM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
I haven't re-tested the new FatFS library as yet.
Dear Ian, if you dont want to use the ff15-version then I have a little present for you ;) I did a compare of the ff.c from ff14a and the ff15 and did create a patched version of the ff14a-version, which didnt give these warnings while compiling.
The content of the .zip should be put in /Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/
The patches file is in the source-directory as ff.c & ff_pacthed.c and the original one is as a copy under the name ff_original.c
Did comile for me without problems - but I cant give a warranty ;)
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1330314398&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceb5c531da236440e015008dad1e9e0b7%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638053100979289253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l8YLis2ZHUN1iLbuRE7vsDEB7kXS5BClkUIH0VNUFp8%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB3TLV526AXN2R356X3WKXCIXANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ceb5c531da236440e015008dad1e9e0b7%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638053100979289253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IQHWaovtxAp8wOp22FXJy2fvvLKh%2BhjFzi61%2Bb6EeDM%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Dear Guido, Well, this is an interesting suggestion, The minimal patch is: Line 2047: while (seq); to while (i && seq); ...secondly, this is such a small change that I will accept this. I note this change in the new SdFat library. I have to admit that I would not have thought of this!!!! I will add this patch to the repo but I think it is still worth a re-check of the new library with the ADC patch to see if it is OK. If so, I will update the whole library in the repo.
Dear Ian, in RT-11 V5.04 I had on my 32GB Cards the problem that after editing the STARTF.COM I cant save it. It gave me an error and hang:
KED STARTf.COM
change last line
from R MSCPCK
to !R MSCPCK
on EXIT (PF1(Gold)-7-ENTER)
Command: exit
R2: 0x4
Error
rkstep: failed to seekon RT-11 V4.00C I could edit/save the STARTF.COM without problems. On a 8GB Card booth did work.
As a test I reformated the 32GB Cards with Windows (not wth the SD Card Formatter) to exFAT&FAT32 and then the edit of the STARTF.COM in RT-11 V5.04 also did work. Bad that it is so inconsistent :(
On a 32GB Card I also had a very strange boot at one time:
RT-11FB V05.04 F
sd_wait_token: timeout
/home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/sd_driver/sd_card.c:815 Read timeout
rkstep: failed to seekHow came this path of my Linux in the Pico .UF2?
Kind Regards Guido
Isysxp
commented
1 year ago Dear Guido,
So far as I can tell, there can be problems with various types of SDcards in various combinations. I use a 32GB SanDisk card and it seems to be OK. Again, the error you are seeing is from a call to the FatFS library. I suspect that this is a communication problem. Particularly if it is intermittent. The commonest cause of things like this are the connections between the board and the SDcard. On the page: carlk3/no-OS-FatFS-SD-SPI-RPi-Pico: A FAT filesystem with SPI driver for SD card on Raspberry Pi Pico (github.com)https://github.com/carlk3/no-OS-FatFS-SD-SPI-RPi-Pico they do suggest using some pull resistors etc. and I would note ... keep the connecting wires short!
Regards, Ian.
From: Guido Lehwalder @.> Sent: 29 November 2022 4:24 PM To: Isysxp/Pico_1140 @.> Cc: Ian Schofield @.>; Mention @.> Subject: Re: [Isysxp/Pico_1140] [Info] SPI-Connection on a "normal" Pico for pdp1140 (Issue #1)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Dear Guido, Well, this is an interesting suggestion, The minimal patch is: Line 2047: while (seq); to while (i && seq); ...secondly, this is such a small change that I will accept this. I note this change in the new SdFat library. I have to admit that I would not have thought of this!!!! I will add this patch to the repo but I think it is still worth a re-check of the new library with the ADC patch to see if it is OK. If so, I will update the whole library in the repo.
Dear Ian, in RT-11 V5.04 I had on my 32GB Cards the problem that after editing the STARTF.COM I cant save it. It gave me an error and hang:
KED STARTf.COM
change last line from R MSCPCK to !R MSCPCK on EXIT (PF1(Gold)-7-ENTER)
Command: exit R2: 0x4 Error rkstep: failed to seek
on RT-11 V4.00C I could edit/save the STARTF.COM without problems. On a 8GB Card booth did work.
As a test I reformated the 32GB Cards with Windows (not wth the SD Card Formatter) to exFAT&FAT32 and then the edit of the STARTF.COM in RT-11 V5.04 also did work. Bad that it is so inconsistent :(
On a 32GB Card I also had a very strange boot at one time:
RT-11FB V05.04 F sd_wait_token: timeout /home/pi/pico/Pico_1140/Pico_1140_DC/no-OS-FatFS-SD-SPI-RPi-Pico-master/FatFs_SPI/sd_driver/sd_card.c:815 Read timeout rkstep: failed to seek
How came this path of my Linux in the Pico .UF2?
Kind Regards Guido
— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F1%23issuecomment-1330908443&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3e3ad09137f54a9f244708dad2262a71%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638053358602338403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vuQdBuTa4dKAmFFAV88hEvN7JMrxYw6xrJ73SL8SbD0%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB45MLJ6MBBUOTXV4ELWKYU3DANCNFSM6AAAAAASHTREQM&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3e3ad09137f54a9f244708dad2262a71%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638053358602338403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=55dmdOIm0sCwmPOyIzIuAmBwHFJfK3J%2BsV06tvSllKg%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
guidol70
commented
1 year ago Dear Guido, Again, the error you are seeing is from a call to the FatFS library. I suspect that this is a communication problem. Particularly if it is intermittent. The commonest cause of things like this are the connections between the board and the SDcard. On the page: carlk3/no-OS-FatFS-SD-SPI-RPi-Pico: A FAT filesystem with SPI driver for SD card on Raspberry Pi Pico (github.com)https://github.com/carlk3/no-OS-FatFS-SD-SPI-RPi-Pico they do suggest using some pull resistors etc. and I would note ... keep the connecting wires short!
Dear Ian, I did already read the page about the no-OS-FatFS-SD-SPI-RPi-Pico. My SDCard-Adapter has already resistors and a own power-stepdown-converter (5V to 3.3V).
I used the combination of the adapter/Pico/Breadboard on different projects (RunCPM and RC2040) without any SDCard-Issues.
RC2040 does use also no-OS-FatFS-SD-SPI-RPi-Pico and RunCPM does use the Arduino-Library SDFat.
SDFat does use 19Mhz against the 12Mhz I did read in the Pico_1140 Source (400Khz init for LOW and 12Mhz for HIGH).
So normally the connections should be OK, because I use only 10cm short Breadboard-Wires (with shorter ones I could connect the SDCard-Adapter to the Pico ;) )
But to be sure I now doubled the cables for SPI-Data, Power and GND form the Pico to the SDCard-Adapter :)
I will keep an eye if it runs now better...
PS: I did take a look at RT-11 v5.7, but it seems much to big for an RK05-Device :( and within simh I also didnt get ot installed on a RL-device. For v5.04 I copied the v5.7-version of ked to my v5.04-rk-image :)
Kind regards Guido
guidol70
commented
1 year ago @Isysxp Dear Ian, I tweaked the startup-screen-design a little bit ;) and now we have the latest v5.07 (5.7) . but as SB and not F To get BASIC, FOCAL and FORTRAN on the image I had to remove the Online-Index for the Handbooks (INDEX.) and the SYGEN.* files - but kept them in a copy without the languages.
@Isysxp Many Thanks for this software! :) Because I didnt have a Sparkfun Things Plus RP2040 and you wrote:
I checked the schematics and did create a tablesheet and some pictures how to connect the SDCard via SPI-Bus like on the Thins Plus.
Il will add these if anyone other may als recreate this with a normal RPi Pico (or PicoW).
My Connection tablesheet:
The pictures I extracted from the Sparkfun Things Plus Schematic:
and a schematic and real Picture of my pdp1140.Pico on the Breadboard
If you want, you can take/use whis pictures on your page ;)
BTW: a short question at the end... Is it OK when I do get the followinf warning while compiling?: