@Corjan @Ralph
Hi guys, wasn't sure exactly where to put this - so it ended up here
Ok,
can you please look into the details on the Hardware ID list for the PICO ?.
You list GPIOs 23 24 and 25 as available.
This is incorrect.
GPIO23 is used internally as a control for the power converter control (hence not available and not connected externally).
GPIO24 is used internally as a USB connect VBUS recognition (hence not available and not connected externally).
GPIO25 is used for the on board LED and is not available and not connected externally and not recommended for use at all - ( according to the datasheet.) - I am sure it 'could' be used with caution - but is only accessible via the TP5 PAD, not via a general board connector.
Many thanks, Joe
Attached documents links -
Datasheet -
https://datasheets.raspberrypi.org/pico ... asheet.pdf
Schematic -
.
Raspberry PICO - incorrect details on Hardware id list.
Raspberry PICO - incorrect details on Hardware id list.
Joe. CISSP, MSc.
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi,
Thx, will have a look at this next week.
Corjan
Thx, will have a look at this next week.
Corjan
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi Corjan, Forgot to mention, GPIO 29 is also not available for usage (ADC3) and is not brought out to the external connectors. It is a VSYS/3 via a simple potential divider input to the 2040 used for basic supply voltage monitoring.
They are the only 4 of the 30 GPIO (including ADC) that are not available to the user on the external connectors leaving 26 IO in total available of which 3 are also capable of ADC.
Joe
Joe. CISSP, MSc.
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi,
Updated wiki. Thanks again for response,
Corjan
Updated wiki. Thanks again for response,
Corjan
Re: Raspberry PICO - incorrect details on Hardware id list.
Thanks Corjan, that is superb, thankyou, really appreciated. This board deserves to be pushed as much as possible as it is simply amazing.
Can I please ask if it may be possible to enable messageport to ever work on the PICO ?
It uses the CDC protocol and would not follow standard baudrate assignments.
As in - https://arduino-pico.readthedocs.io/en/ ... erial.html
and - https://siminnovations.com/forums/viewt ... age#p37137
It may not be possible, but would be absolutely amazing if you could get it to work with messageport with some custom code as the general Arduino support is excellent.
(Sorry to bother you again .. ... I will turn the light out as I leave )
Thanks
Joe
Can I please ask if it may be possible to enable messageport to ever work on the PICO ?
It uses the CDC protocol and would not follow standard baudrate assignments.
As in - https://arduino-pico.readthedocs.io/en/ ... erial.html
and - https://siminnovations.com/forums/viewt ... age#p37137
It may not be possible, but would be absolutely amazing if you could get it to work with messageport with some custom code as the general Arduino support is excellent.
(Sorry to bother you again .. ... I will turn the light out as I leave )
Thanks
Joe
Joe. CISSP, MSc.
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi,
Not sure if the Pico is already supported by the Arduino framework?
If so, there is nothing stopping it from working.
Corjan
Not sure if the Pico is already supported by the Arduino framework?
If so, there is nothing stopping it from working.
Corjan
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi,
Looking at the links, it seems weird to me that the Serial baud rate is ignored.
A USB based virtual COM port still has a baud rate I would say...
Corjan
Looking at the links, it seems weird to me that the Serial baud rate is ignored.
A USB based virtual COM port still has a baud rate I would say...
Corjan
Re: Raspberry PICO - incorrect details on Hardware id list.
Agreed Corjan, it seems to be assigned via CDC, the port is not an issue, the baud rate seems to be, and not accessible via the 'serial add' in Arduino. - also, the serial baud rate is simply ignored in the serial monitor interface in the IDE. (yet works perfectly - but, you can change baud rates all you like in the monitor and it is simply ignored)
It certainly does seem to be a CDC peculiarity. Perhaps you would be kind enough to test and you will see ?. I believe it is a general CDC issue in the way it works - not just arduino.
As you rightly say, it DOES have an assigned baud rate but is seems to be not accessible via normal means. As for arduino support for the PICO, it is really good. As said, is compiles perfectly for messageport but simply cannot be seen due to the com port.
Joe. CISSP, MSc.
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi,
Just tried it, and somehow I am able to send data from Pico -> PC, but not the other way around.
Also with default Serial examples and Serial monitor.
Also from AM, I cannot write to the virtual USB COM port, it doesn't give an error, but simply responds that it didn't write anything.
Seems to be issue in Arduino framework.
Corjan
Just tried it, and somehow I am able to send data from Pico -> PC, but not the other way around.
Also with default Serial examples and Serial monitor.
Also from AM, I cannot write to the virtual USB COM port, it doesn't give an error, but simply responds that it didn't write anything.
Seems to be issue in Arduino framework.
Corjan
Re: Raspberry PICO - incorrect details on Hardware id list.
Hi Corjan.
It seems (to me with my very limited knowledge of this level or programming) to be a general issue unless approached in a specific way. - as CDC can be used for different device conversions etc. - ie - serial to parallel etc..
As for the pico to PC - I have had no issue (as far as I can remember) with external terminal type programs - but admit, I have not tried the response. They all seem to receive info FROM the PICO, yet, the baud rate setting on the terminal program on the PC makes no difference. ???
I came across this - way above my paygrade.. but the author is the guy behind USB complete - the bible.
It may be totally worthless info....
http://janaxelson.com/usb_virtual_com_port.htm
It seems (to me with my very limited knowledge of this level or programming) to be a general issue unless approached in a specific way. - as CDC can be used for different device conversions etc. - ie - serial to parallel etc..
As for the pico to PC - I have had no issue (as far as I can remember) with external terminal type programs - but admit, I have not tried the response. They all seem to receive info FROM the PICO, yet, the baud rate setting on the terminal program on the PC makes no difference. ???
I came across this - way above my paygrade.. but the author is the guy behind USB complete - the bible.
It may be totally worthless info....
http://janaxelson.com/usb_virtual_com_port.htm
Joe. CISSP, MSc.