• Lower power consumption. The behaviour for low power standby modes still have to be tested, but these are expected to be better than the RP2040
• Better performance, allowing the clock speed to be lowered for even lower power consumption
• About 2* the amount of SRAM, which opens a number of new (future) options
• The TULIP application is not affected by the RP2350's errata
  

(08-24-2024 02:12 AM)Sylvain Cote Wrote:  The board was delivered last week and the final assembly was completed early this week.

My complete test setup is:

• host computer
  
  • Hardware
    
    • Raspberry Pi 4 Model B Rev 1.5 - 8GB RAM - Cortex-A72 with 4 cores (aka RP4B)
    • Armor Case Passive Cooling or Active Cooling
    • 128GB microSDXC SAMSUNG PRO Endurance
    • Raspberry Pi 15W USB-C Power Supply
    • Optional: mouse, keyboard and monitor. -> video: micro-HDMI-male_to_standard-HDMI-female_adapter and a standard-HDMI-male-male_cable
      
  • Software
    
    • Raspberry OS 64-bit → installed on microSD card with Raspberry Pi Imager
      OS: Debian GNU/Linux 12 (bookworm) | Kernel: Linux 6.6.31+rpt-rpi-v8 | Architecture: arm64
    • Special configuration:
      
      • default headless video set to 1280x1024
      • wired network static configuration for: IP, default gateway and DNS
      • default vnc server running
      • RealVNC client installed
        
  • Optional: Development & Debugging
    
    • Raspberry Pi Debug Probe
    • Raspberry Pi Pico development tools C/C++ SDK
      installation script
      
      Code:
      

      mkdir -p ~/temp
cd ~/temp
wget https://raw.githubusercontent.com/raspberrypi/pico-setup/master/pico_setup.sh
chmod +x pico_setup.sh
./pico_setup.sh
    • testing → follow instructions given in the Raspberry Pi Debug Probe documentation
      
      • install a Raspberry Pi Pico 1 (RP2040) on a breadboard
      • connect the Raspberry Pi Debug Probe to the Pico to the SWD connector
      • connect the Raspberry Pi Debug Probe to the Pico to the RP2040 GPIO RX/TX/GND pins
      • connect the Raspberry Pi Debug Probe to the USB port of the Raspberry Pi 4
      • compiled application files location
        
        • blink → ~/temp/pico/pico-examples/build_pico/blink
        • hello world serial → ~/temp/pico/pico-examples/build_pico/hello_world/serial
          
      • notes
        
        • OpenOCD, SWD, GPIO serial port and GDB works perfectly
        • I have tested several applications and did not find any issue
          
  • Virtual HP-IL
    
    • lifutils (utilities runs natively)
      installation steps
      
      Code:
      

      mkdir -p ~/temp
cd ~/temp
git clone https://github.com/bug400/lifutils.git
cd lifutils
mkdir rp4b
cmake -DCMAKE_BUILD_TYPE=Release -S . -B rp4b
cd rp4b
make
sudo make install
    • pyilper (application run natively, no virtual machine needed, well .... apart from cpython of course)
      installation steps
      
      Code:
      

      python3 -‑version                   // installed with the OS and I get version 3.11.2
python3 -m venv ~/py311
source ~/py311/bin/activate
python -m pip install --upgrade pip
pip install pyserial
pip install pyilper
      testing:
      
      
      1. connect PIL-Box to RP4B → serial port added: /dev/ttyUSB0
      2. start pyilper → from command line
         
         Code:
         

         source ~/py311/bin/activate
pyilper -‑clean -‑instance test
      3. configure pyilper to use /dev/ttyUSB0
      4. adds and configure virtual IL devices
      5. leave pyilper
      6. restart pyilper → from command line
         
         Code:
         

         source ~/py311/bin/activate
pyilper --instance test
      7. test virtual devices with an HP-41/71B/75
         

Tulip4041

• tomorrow
  

edit: typos & formatting

(09-28-2024 01:32 PM)Etienne Victoria Wrote:  Based on the Pico pitch and the picture of the board, my guess is 2,54mm spacing.

But just wanted to confirm

Etienne

(08-24-2024 02:12 AM)Sylvain Cote Wrote:  

Code:

python3 -‑version                   // installed with the OS and I get version 3.11.2
python3 -m venv ~/py311
source ~/py311/bin/activate
python -m pip install --upgrade pip
pip install pyserial
pip install pyilper

testing:
[list=1]
[*]connect PIL-Box to RP4B → serial port added: /dev/ttyUSB0
[*]start pyilper → from command line

Code:

source ~/py311/bin/activate
pyilper -‑clean -‑instance test

[*]configure pyilper to use /dev/ttyUSB0
[*]adds and configure virtual IL devices
[*]leave pyilper
[*]restart pyilper → from command line

Code:

source ~/py311/bin/activate
pyilper --instance test

[*]test virtual devices with an HP-41/71B/75

(10-16-2024 07:18 AM)MeindertKuipers Wrote:  Good luck building it, and let me know how it goes. Most of the orders are now on their way or have already arrived. For the Pico2, just pick the right webshop, after the initial wait I had no issues getting my hands on multiple units.
Remember that I do NOT recommend to solder the Pico2 to the PCB. Currently only versions without header are available, but please solder headers to the Pico and sockets on the PCB. Unsoldering the Pico is almost impossible in case of problems.
If you want to experiment with your own code I do recommend to solder a header to the debug interface and use a Pico Probe. I use this all the time and it is just one or two mouse clicks in VS Code to compile and run a new version without having to go into BOOTSEL mode.

(10-27-2024 03:22 PM)MeindertKuipers Wrote:  Just uploaded all sources again to https://github.com/mjakuipers/TULIP-DevBoard. The new firmware binary is in the TULIP4041-P2 build directory again (the .uf2 file).

Latest changes:
- serial port connects and disconnects are reported in the CLI
- PILBox connect status changes are reported in the CLI
- TRANSMIT ERR still occurs when there is a serial connection but no virtual IL device (PILBOX status is TDIS). This is intentional
- The HP-IL scope now shows the tracer sample counter for better correlation. There may be some jitter

About the trace counter: this is generated in real time for each HP41 T0-T0 cycle, even when the tracer is not connected, disabled or when samples are filtered. The shown trace samples lag behind the calculator activity.

Have fun and let me know your feedback.

(10-27-2024 07:44 PM)Craig Bladow Wrote:  

Code:


  CDC Port 3 [HPIL] connected                                                   
  WARNING: No virtual HP-IL device connected, HP-IL loop may be open          
  PILBox mode changed to COFF / Controller OFF                                  
  PILBox mode changed to COFI / Controller OFF with IDY

The warning line seems out of place, given that pyILPER was just connected.

(10-28-2024 09:54 AM)MeindertKuipers Wrote:  

(10-27-2024 07:44 PM)Craig Bladow Wrote:  

Code:


  CDC Port 3 [HPIL] connected                                                   
  WARNING: No virtual HP-IL device connected, HP-IL loop may be open          
  PILBox mode changed to COFF / Controller OFF                                  
  PILBox mode changed to COFI / Controller OFF with IDY

The warning line seems out of place, given that pyILPER was just connected.

It is indeed a bit out of place, I thought about this. But the firmware is too quick and sees a serial port connection and issues the warning before it has seen the PILBox conncting. I might try a timer on the warning, but that is not very straightforward,

(10-28-2024 05:13 PM)Craig Bladow Wrote:  Something like:

Code:


  CDC Port 3 [HPIL] connected                                                   
  WARNING: No virtual HP-IL device connected, HP-IL loop may be open  
  HP-IL state changed to CONNECTED        
  PILBox mode changed to COFF / Controller OFF                                  
  PILBox mode changed to COFI / Controller OFF with IDY

(10-28-2024 05:13 PM)Craig Bladow Wrote:  Something like:

Code:


  CDC Port 3 [HPIL] connected                                                   
  WARNING: No virtual HP-IL device connected, HP-IL loop may be open  
  HP-IL state changed to CONNECTED        
  PILBox mode changed to COFF / Controller OFF                                  
  PILBox mode changed to COFI / Controller OFF with IDY