I think from copy/paste

P22 Variables. "Command" missing. Some cause errors, though many don't.

  Quote  

A variable name or a label must not be the same as a command, function or one of the following keywords: THEN, ELSE,
GOTO, GOSUB, TO, STEP, FOR, WHILE, UNTIL, LOAD, MOD, NOT, AND, OR, XOR, AS.

Edit.
p26  String Operators:
<> < > <= =< >= =>
Inequality, less than, greater than, less than or equal to, less than or
equal to (alternative version), greater than or equal to, greater than or
equal to (alternative version) In order of ASCII value.
Edited 2025-06-06 11:51 by phil99

OPTION NOCHECK [ON|OFF] temporary option in the code but not in the manual.
Looks to prevent the test for CNTRL+C and Interrupts after each each command.

p 161:


'mode'?

Michael

p 161:


should be:SPRITE WRITE [#b, x, y,[,mode
should be:SPRITE WRITE [#]b, x, y,[,mode]



p 105:


"%, x, y [,col]" ??


p 70:


... very confusing.

Michael
Edited 2025-06-08 06:00 by twofingers

Page 13 - I/O pin limits
I'm probably just being pedantic...

The RP2040 has a maximum total GPIO current, source or sink, of 50mA including the QSPI

The RP2350 has a maximum total GPIO current, source or sink, of 100mA in addition to the QSPI. You get slightly more than twice the current capability.

Note that these currents are shared across all pins:
50mA across 26 pins for the Pico
100mA across 26 pins for the Pico 2
100mA across 48 pins for the RP2350B

1. p14:

  Quote  

Versions with VGA video @ 640x400 resolution have the clock set to 252MHz however this can be changed using OPTION RESOLUTION to 252MHz, 315MHz or 378MHz.

This confused me since the wording suggests that you might use OPTION RESOLUTION to directly set the clock speed, whereas in reality the clock being set is a side-effect.

The wording for the next sentence regarding HDMI I think is better.

2. I think the documentation for OPTION RESOLUTION is inconsistent, the documentation for the command (p98) lists resolutions of 720, 800 and 848 but these don't seem to appear in earlier table(s), e.g. p31, p66.

I wonder if it would be better to just document the resolutions, their modes and the corresponding CPU frequencies just once in an appendix and for everywhere else just to reference that.

Best wishes,

Tom

VGA is correct, HDMI is wrong as it can also change the frequency for 640x480 mode using OPTION RESOLUTION. Other resolutions are fixed frequency

  Quote  

Versions with Video @ 640x400 resolution have the clock set to 252MHz however this can be changed using OPTION RESOLUTION to 252MHz, 315MHz or 378MHz.  
At other video resolutions the clock speed is fixed at 283.2MHz, 324MHz, 360MHz or 372MHz depending on the video resolution selected and this cannot be changed.  

  Quote  

I think the documentation for OPTION RESOLUTION is inconsistent, the documentation for the command (p98) lists resolutions of 720, 800 and 848 but these don't seem to appear in earlier table(s), e.g. p31, p66.

I wish you had raised this earlier   Manual is with Geoff for tidying - hopefully not too much wasted effort

I can't see anywhere what PIO stands for.

  LouisG said  

I can't see anywhere what PIO stands for.

Programmed Input/Output
Regards
MIchael

@louisg

The rp2040 and rp2350 chips have ARM processors, but also smart IO pins. These smart IO pins can do elementary functions without ARM involvement. Programable.

Volhout

p86

MMTOPIC$ should be MM.TOPIC$ (missing dot)

Perhaps a bit late, but a possible addition. The manual could be changed to read:-

  Manual, Functions said  

INPUT$(nbr, [#]fnbr)
 This function will return as many characters as are in the file or receive buffer up to ‘nbr’, removing them from the buffer.

Edited 2025-06-12 11:17 by phil99

  twofingers said  

p86

MMTOPIC$ should be MM.TOPIC$ (missing dot)

That's on pg. 89 of my copy.

Page 120, GUI TEST LCDPANEL - test also works on VGA an HDMI (all Modes).

Page 151

32 bits should be 64 bits, I think.

p. 149 (Typo)

  Quote  

You can use the MEMORY PACK command to
create the arrays from a normal 40956 element integer array.

sould be: 4096 !

An example would be helpful, as it's not clear whether all elements must be filled. It's also unclear how to use a second array or how to overwrite or delete the sound data (not the array!).

  toml_12953 said  

  twofingers said  

p86

MMTOPIC$ should be MM.TOPIC$ (missing dot)

That's on pg. 89 of my copy.

Correct!
Michael

PEEK(FLOAT and POKE FLOAT both still refer to 32bit instead of 64bit.

Jim

Missing function in the manual:

Page 171 - 172:

DEVICE(MOUSE channel,funct)

  Quote  

X the X coordinate (0 to MM.HRES-1)
Y the Y coordinate (0 to MM.VRES-1)
L the state of the left mouse button
R the state of the right mouse button
M the state of the middle mouse button (wheel click)
D 1 if there has been a double click of the left mouse button

"W" is missing!, I discovered this by accident. W gives the wheel position, which is really handy!

Greetings
Daniel

I guess the new manual is going to be updated with these corrections ?