Build for Pico2

[TheKitty]

I am looking to use the pico2 branch to make an XT emulator for the upcoming Adafruit Fruit Jam board. It has the RP2350B and PSRAM, 2x USB Host (via a CH334F hub), DVI/HDMI out via HSTX, etc.

I created a bios-xt.rom merged XT ROM.

When I CMake, I get

I'm unsure what is made and where (I'm still learning CMake).

I would like to make a UF2.

Would it be possible in the README.md to add the pico2 build likes like you have for other builds, perhaps any other tips?

Thank you, Anne

[Daft-Freak]

I think the only extra thing it should need compared to PicoVision is PICO_BOARD set to an appropriate value. (Something RP2350-based so IS_PICO2 gets detected in the root CMakeLists.txt)

As an example I was last using: cmake -B build.pico2 -DCMAKE_BUILD_TYPE=Release -DPICO_SDK_PATH=path/to/pico-sdk -DPICO_BOARD=solderparty_rp2350_stamp_xl .

For other board configuration related bits, there's the PSRAM CS near the top of pico2/Main.cpp and the rest is in pico2/config.h.

(That's an interesting looking board, especially considering what I've been doing recently!)

[TheKitty]

Thank you. Hopefully the board will be out in not too long and I think many will find it fits their needs for many things.

[TheKitty]

I may have a compiler flag incorrect somewhere. In compiling or linking, I'm getting the error:
Error: selected processor does not support `mcrr p0,#4,r8,r3,c0' in Thumb mode

I have my tweaked CMakefiles I could provide.

[Daft-Freak]

That error is probably from somewhere in the SDK? (I don't think there's any assembly in here)

I'd guess some config related to 2040 vs 2350 is inconsistent, but don't have any ideas beyond that. Perhaps a case of having leftovers from a previous configure?

[TheKitty]

I'll look to revert my code - if you have a clean compile for the Stamp XL then I should be able to get a clean compile for my RP2350 board

[TheKitty]

I finally have the time to attempt a clean install. I'm targeting a clean install for the Stamp XL RP2350 before trying to change for the Fruit Jam. I did have to add -DPICO_PLATFORM=rp2350 to the first cmake statement on the command line, otherwise it complained about building for rp2040. Here are my current issues:

1. CMake Warning at pico-sdk/src/rp2_common/tinyusb/CMakeLists.txt:10 (message): TinyUSB submodule has not been initialized; USB support will be unavailable hint: try 'git submodule update --init' from your SDK directory (/mnt/c/Users/Anne/Documents/Work/Guide Work/emulators/average2/pico-sdk).

2. CMake Warning at pico-sdk/tools/Findpicotool.cmake:30 (message): No installed picotool with version 2.1.1 found - building from source It is recommended to build and install picotool separately, or to set PICOTOOL_FETCH_FROM_GIT_PATH to a common directory for all your SDK projects

3. fatal error: hardware/structs/hstx_ctrl.h: No such file or directory 8 | #include "hardware/structs/hstx_ctrl.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The issue is I installed picotool and cmake'd it. Likely I need a -DPICOTOOL_FETCH_FROM_GIT_PATH? I cannot find why it is choking on tinyusb. Finally I'd think the files for the Stamp XL would all be in the repo.

Thanks for all your help, Anne

[Daft-Freak]

Hmm, 2 can probably be ignored for now, 3 suggests that the platform is still getting misdetected somehow. (HSTX structs only existing in the SDK for 2340)

In case it helps, this is my CMake output from a new build dir:

$ cmake -B build.stamp2 -DCMAKE_BUILD_TYPE=Release -DPICO_SDK_PATH=$HOME/repos/pico/pico-sdk -DPICO_BOARD=solderparty_rp2350_stamp_xl .
PICO_SDK_PATH is /home/daftfreak/repos/pico/pico-sdk
Target board (PICO_BOARD) is 'solderparty_rp2350_stamp_xl'.
Using board configuration from /home/daftfreak/repos/pico/pico-sdk/src/boards/include/boards/solderparty_rp2350_stamp_xl.h
Auto-converting non-specific PICO_PLATFORM='rp2350' to 'rp2350-arm-s'
Defaulting platform (PICO_PLATFORM) to 'rp2350-arm-s' based on PICO_BOARD setting.
Defaulting compiler (PICO_COMPILER) to 'pico_arm_cortex_m33_gcc' since not specified.
Configuring toolchain based on PICO_COMPILER 'pico_arm_cortex_m33_gcc'
Defaulting PICO_GCC_TRIPLE to 'arm-none-eabi'
-- The C compiler identification is GNU 14.2.0
-- The CXX compiler identification is GNU 14.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/arm-none-eabi-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/arm-none-eabi-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/arm-none-eabi-gcc
Build type is Release
CMake Warning at /home/daftfreak/repos/pico/pico-sdk/tools/Findpicotool.cmake:30 (message):
  No installed picotool with version 2.1.1 found - building from source

  It is recommended to build and install picotool separately, or to set
  PICOTOOL_FETCH_FROM_GIT_PATH to a common directory for all your SDK
  projects
Call Stack (most recent call first):
  /home/daftfreak/repos/pico/pico-sdk/tools/CMakeLists.txt:138 (find_package)
  /home/daftfreak/repos/pico/pico-sdk/src/cmake/on_device.cmake:34 (pico_init_picotool)
  /home/daftfreak/repos/pico/pico-sdk/src/rp2350/boot_stage2/CMakeLists.txt:57 (pico_add_dis_output)
  /home/daftfreak/repos/pico/pico-sdk/src/rp2350/boot_stage2/CMakeLists.txt:98 (pico_define_boot_stage2)


Downloading Picotool
-- Found Python3: /usr/bin/python3.13 (found version "3.13.3") found components: Interpreter
TinyUSB available at /home/daftfreak/repos/pico/pico-sdk/lib/tinyusb/src/portable/raspberrypi/rp2040; enabling build support for USB.
BTstack available at /home/daftfreak/repos/pico/pico-sdk/lib/btstack
cyw43-driver available at /home/daftfreak/repos/pico/pico-sdk/lib/cyw43-driver
lwIP available at /home/daftfreak/repos/pico/pico-sdk/lib/lwip
mbedtls available at /home/daftfreak/repos/pico/pico-sdk/lib/mbedtls
Found fixed disk adapter BIOS
-- Configuring done (2.1s)
-- Generating done (0.1s)
-- Build files have been written to: /home/daftfreak/repos/PACE/build.stamp2

(I don't even have picotool installed, whoops)

[TheKitty]

I'm back to trying to get the build process working, starting with the Stamp XL then moving onto a custom RP2350.

For picotool, ensure the PICO_SDK_PATH is set
$ export PICO_SDK_PATH=full path to your pico sdk

For tinyusb, it must be in the pico-sdk/lib/tinyusb library
and git submodule update --init
so files like tusb.h are found

I am getting some CXX compile warnings about printf formats not matching the size of the variables (long vs int, etc). in Main and Storage

But yay, I can build the stampXL project (target PACEPico2) now.

Do you have suggestions for the syntax for adding yet another board? There will be some different pins for things like SD, PSRAM (8MB) and extra flash (16MB), HSTX output pins, sound interface, etc.

I do appreciate your patience with me. Anne

[Daft-Freak]

I was going to say it's a bit of a mess, but I just stole some bits from another project so all the pin config should be here now:
https://github.com/Daft-Freak/probably-average-computer-emulator/blob/pain/pico2/config.h

Though this may be slightly more complicated as I'm assuming your unreleased board won't have a config header in the SDK yet. 🤔

[TheKitty]

There is one that hasn't been merged https://github.com/raspberrypi/pico-sdk/pull/2363/files so I'll need to figure out where to put that

ah pico-sdk/src/boards/include/boards/

I copied /build.stamp2 to /build.fruitjam, I'm looking to change the right files for a new build

• cmake_install.cmake changed
• CPackConfig.cmake changed
• CPackSourceConfig.cmake changed

[Daft-Freak]

CMake really doesn't like you moving/copying build dirs, so it's likely going to be easier to reconfigure and create a new one with the correct PICO_BOARD.
cmake -B build.fruitjam -DPICO_BOARD=adafruit_fruit_jam [... other flags]

Then it should just be a case of adding a #elif defined(ADAFRUIT_FRUIT_JAM) block in the config.

(Bit late for this, but there's also a way to specify a custom folder for board headers -DPICO_BOARD_HEADER_DIRS=...)

[TheKitty]

In display.cpp:
` // HSTX outputs 0 through 7 appear on GPIO 12 through 19.
// Pinout on Pico DVI sock:
//
// GP12 D0+ GP13 D0-
// GP14 CK+ GP15 CK-
// GP16 D2+ GP17 D2-
// GP18 D1+ GP19 D1-

But in src/boards/include/boards/adafruit_fruit_jam.h, different choices were made:

#define ADAFRUIT_FRUIT_JAM_DVI_CKN_PIN 12
#define ADAFRUIT_FRUIT_JAM_DVI_CKP_PIN 13
#define ADAFRUIT_FRUIT_JAM_DVI_D0N_PIN 14
#define ADAFRUIT_FRUIT_JAM_DVI_D0P_PIN 15
#define ADAFRUIT_FRUIT_JAM_DVI_D1N_PIN 16
#define ADAFRUIT_FRUIT_JAM_DVI_D1P_PIN 17
#define ADAFRUIT_FRUIT_JAM_DVI_D2N_PIN 18
#define ADAFRUIT_FRUIT_JAM_DVI_D2P_PIN 19

It looks wonky how the HSTX lines are mapped
// Assign clock pair to two neighbouring pins:
hstx_ctrl_hw->bit[2] = HSTX_CTRL_BIT0_CLK_BITS;
hstx_ctrl_hw->bit[3] = HSTX_CTRL_BIT0_CLK_BITS | HSTX_CTRL_BIT0_INV_BITS;
for(uint lane = 0; lane < 3; ++lane) {
// For each TMDS lane, assign it to the correct GPIO pair based on the
// desired pinout:
static const int lane_to_output_bit[3] = {0, 6, 4};
int bit = lane_to_output_bit[lane];
// Output even bits during first half of each HSTX cycle, and odd bits
// during second half. The shifter advances by two bits each cycle.
uint32_t lane_data_sel_bits =
(lane * 10 ) << HSTX_CTRL_BIT0_SEL_P_LSB |
(lane * 10 + 1) << HSTX_CTRL_BIT0_SEL_N_LSB;
// The two halves of each pair get identical data, but one pin is inverted.
hstx_ctrl_hw->bit[bit ] = lane_data_sel_bits;
hstx_ctrl_hw->bit[bit + 1] = lane_data_sel_bits | HSTX_CTRL_BIT0_INV_BITS;
}
for(int i = 12; i <= 19; ++i)
gpio_set_function(i, GPIO_FUNC_HSTX);

Might there be an easier way?

[Daft-Freak]

That's the messiness I pushed a change for yesterday: 68ca952

So pull that and #define DVI_CLK_P ADAFRUIT_FRUIT_JAM_DVI_CKP_PIN etc. (I hope)

[TheKitty]

I added this to config.h, double checked, that the positive lines are on odd numbers, negative on even. But that doesn't appear to be the case with the logic that seems to indicate these pins are even numbers for the positive HSTX and positive for the HSTX N pins

#elif defined(ADAFRUIT_FRUIT_JAM)
#define SD_SCK 34
#define SD_MOSI 35
#define SD_MISO 36
#define SD_CS 39

#define DVI_CLK_P ADAFRUIT_FRUIT_JAM_DVI_CKP_PIN // 13
#define DVI_D0_P ADAFRUIT_FRUIT_JAM_DVI_D0P_PIN // 15
#define DVI_D1_P ADAFRUIT_FRUIT_JAM_DVI_D1P_PIN // 17
#define DVI_D2_P ADAFRUIT_FRUIT_JAM_DVI_D2P_PIN // 19

#define PSRAM_CS_PIN 47

[Daft-Freak]

Should work either way? A least in this case it's calculating 13 ^ 1 == 12 for the negative clock. (Also I think the thing I borrowed this code from was using positive on odd pins)