• 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
         

(08-25-2024 11:07 PM)John Ioannidis Wrote:  What's the point of telling us all this if you are not posting any code?

(08-25-2024 11:07 PM)John Ioannidis Wrote:  Also, why tell us about the hosting environment? The Pico SDK runs on pretty much everything. Is it really relevant what kind of power supply your Pi4 uses or how much storage it has?

(08-25-2024 11:07 PM)John Ioannidis Wrote:  What's the point of telling us all this if you are not posting any code?

(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:
[list]
[*]host computer
[list]
[*]Hardware

(08-27-2024 07:33 PM)Sylvain Cote Wrote:  I am able to connect on the multiple serial terminals with minicom but pyilper only uses ttyUSB devices and ignore the ttyACM ones.
Fortunately it works if I manually change pyilper configuration file and set it to "/dev/ttyACM2".
I just posted a request to Joachim to add the ttyACM devices to his PIL-Box serial interface configuration dialog.

(08-28-2024 12:44 PM)jsi Wrote:  The combo box entry for the PIL-Box serial device is editable. Therefore you can enter an arbitrary device name there instead of choosing a member of the list.

(08-28-2024 12:44 PM)jsi Wrote:  I will be happy to add ttyACMxx devices to the combo box list in the next pyILPER version.

(08-26-2024 07:24 AM)MeindertKuipers Wrote:  

(08-25-2024 11:07 PM)John Ioannidis Wrote:  What's the point of telling us all this if you are not posting any code?

No worries, there will be source code published of the version that will go out to the users of the Development Board. I do want to make certain that it is in a useable state. And my earlier offer still stands, if you are interested in the sources I will happily share it with you.

(08-29-2024 12:03 PM)MeindertKuipers Wrote:  Since the sources are in a more or less stable state (pending any feedback from Sylvain) I decided to make these public already at https://github.com/mjakuipers/TULIP-DevBoard. A binary for direct downloading in the Pico is in the build directory.

The usual disclaimer applies, use at your own risk. Also keep in mind that many parts are in development and half finished. Feedback is appreciated of course.

I still have not received my Pico 2 board, and I have some trouble getting the current sources to compile under the new SDK 2.0, and I am still using the SDK 1.51 for that.

(09-01-2024 02:42 PM)Sylvain Cote Wrote:  Testing update #2 ...

Minor-Issues:
→ some inconsistencies in messages and/or behavior.

Major-Issues:
→ IR-Printing and external ROM mapping.
→ That could be me, not understanding and/or not doing the things correctly and/or functionality missing in my beta firmware.