Access to functions and data in the bootrom. More...

Macros

#define ROM_TABLE_CODE(c1, c2)   ((c1) | ((c2) << 8))
 Return a bootrom lookup code based on two ASCII characters. More...
 

Functions

static uint32_t rom_table_code (uint8_t c1, uint8_t c2)
 Return a bootrom lookup code based on two ASCII characters. More...
 
void * rom_func_lookup (uint32_t code)
 Lookup a bootrom function by its code. More...
 
void * rom_data_lookup (uint32_t code)
 Lookup a bootrom data address by its code. More...
 
bool rom_funcs_lookup (uint32_t *table, unsigned int count)
 Helper function to lookup the addresses of multiple bootrom functions. More...
 
static __force_inline void * rom_func_lookup_inline (uint32_t code)
 Lookup a bootrom function by code. This method is forcibly inlined into the caller for FLASH/RAM sensitive code usage. More...
 
void rom_reset_usb_boot (uint32_t usb_activity_gpio_pin_mask, uint32_t disable_interface_mask)
 Reboot the device into BOOTSEL mode. More...
 
static void rom_connect_internal_flash ()
 Connect the SSI/QMI to the QSPI pads. More...
 
static void rom_flash_exit_xip ()
 Return the QSPI device from its XIP state to a serial command state. More...
 
static void rom_flash_range_erase (uint32_t addr, size_t count, uint32_t block_size, uint8_t block_cmd)
 Erase bytes in flash. More...
 
static void rom_flash_range_program (uint32_t addr, const uint8_t *data, size_t count)
 Program bytes in flash. More...
 
static void rom_flash_flush_cache ()
 Flush the XIP cache. More...
 
static void rom_flash_enter_cmd_xip ()
 Configure the SSI/QMI with a standard command. More...
 

Detailed Description

Access to functions and data in the bootrom.

This header may be included by assembly code

Macro Definition Documentation

◆ ROM_TABLE_CODE

#define ROM_TABLE_CODE (   c1,
  c2 
)    ((c1) | ((c2) << 8))

Return a bootrom lookup code based on two ASCII characters.

These codes are uses to lookup data or function addresses in the bootrom

Parameters
c1the first character
c2the second character
Returns
the 'code' to use in rom_func_lookup() or rom_data_lookup()

Function Documentation

◆ rom_connect_internal_flash()

static void rom_connect_internal_flash ( )
inlinestatic

Connect the SSI/QMI to the QSPI pads.

Restore all QSPI pad controls to their default state, and connect the SSI/QMI peripheral to the QSPI pads.

On RP2350 if a secondary flash chip select GPIO has been configured via OTP OTP_DATA_FLASH_DEVINFO, or by writing to the runtime copy of FLASH_DEVINFO in bootram, then this bank 0 GPIO is also initialised and the QMI peripheral is connected. Otherwise, bank 0 IOs are untouched.

◆ rom_data_lookup()

void * rom_data_lookup ( uint32_t  code)

Lookup a bootrom data address by its code.

Parameters
codethe code
Returns
a pointer to the data, or NULL if the code does not match any bootrom function

◆ rom_flash_enter_cmd_xip()

static void rom_flash_enter_cmd_xip ( )
inlinestatic

Configure the SSI/QMI with a standard command.

Configure the SSI/QMI to generate a standard 03h serial read command, with 24 address bits, upon each XIP access. This is a slow XIP configuration, but is widely supported. CLKDIV is set to 12 on RP2350. The debugger may call this function to ensure that flash is readable following a program/erase operation.

Note that the same setup is performed by flash_exit_xip(), and the RP2350 flash program/erase functions do not leave XIP in an inaccessible state, so calls to this function are largely redundant on RP2350. It is provided on RP2350 for compatibility with RP2040.

◆ rom_flash_exit_xip()

static void rom_flash_exit_xip ( )
inlinestatic

Return the QSPI device from its XIP state to a serial command state.

On RP2040, first set up the SSI for serial-mode operations, then issue the fixed XIP exit sequence described in Section 2.8.1.2 of the datasheet. Note that the bootrom code uses the IO forcing logic to drive the CS pin, which must be cleared before returning the SSI to XIP mode (e.g. by a call to _flash_flush_cache). This function configures the SSI with a fixed SCK clock divisor of /6.

On RP2350, Initialise the QMI for serial operations (direct mode), and also initialise a basic XIP mode, where the QMI will perform 03h serial read commands at low speed (CLKDIV=12) in response to XIP reads.

Then, issue a sequence to the QSPI device on chip select 0, designed to return it from continuous read mode ("XIP mode") and/or QPI mode to a state where it will accept serial commands. This is necessary after system reset to restore the QSPI device to a known state, because resetting RP2350 does not reset attached QSPI devices. It is also necessary when user code, having already performed some continuous-read-mode or QPI-mode accesses, wishes to return the QSPI device to a state where it will accept the serial erase and programming commands issued by the bootrom's flash access functions.

If a GPIO for the secondary chip select is configured via FLASH_DEVINFO, then the XIP exit sequence is also issued to chip select 1.

The QSPI device should be accessible for XIP reads after calling this function; the name flash_exit_xip refers to returning the QSPI device from its XIP state to a serial command state.

◆ rom_flash_flush_cache()

static void rom_flash_flush_cache ( )
inlinestatic

Flush the XIP cache.

Flush and enable the XIP cache. Also clears the IO forcing on QSPI CSn, so that the SSI can drive the flash chip select as normal.

Flush the entire XIP cache, by issuing an invalidate by set/way maintenance operation to every cache line. This ensures that flash program/erase operations are visible to subsequent cached XIP reads.

Note that this unpins pinned cache lines, which may interfere with cache-as-SRAM use of the XIP cache.

No other operations are performed.

◆ rom_flash_range_erase()

static void rom_flash_range_erase ( uint32_t  addr,
size_t  count,
uint32_t  block_size,
uint8_t  block_cmd 
)
inlinestatic

Erase bytes in flash.

Erase count bytes, starting at addr (offset from start of flash). Optionally, pass a block erase command e.g. D8h block erase, and the size of the block erased by this command - this function will use the larger block erase where possible, for much higher erase speed. addr must be aligned to a 4096-byte sector, and count must be a multiple of 4096 bytes.

This is a low-level flash API, and no validation of the arguments is performed.

See rom_flash_op on RP2350 for a higher-level API which checks alignment, flash bounds and partition permissions, and can transparently apply a runtime-to-storage address translation.

The QSPI device must be in a serial command state before calling this API, which can be achieved by calling rom_connect_internal_flash() followed by rom_flash_exit_xip(). After the erase, the flash cache should be flushed via rom_flash_flush_cache() to ensure the modified flash data is visible to cached XIP accesses.

Finally, the original XIP mode should be restored by copying the saved XIP setup function from bootram into SRAM, and executing it: the bootrom provides a default function which restores the flash mode/clkdiv discovered during flash scanning, and user programs can override this with their own XIP setup function.

For the duration of the erase operation, QMI is in direct mode and attempting to access XIP from DMA, the debugger or the other core will return a bus fault. XIP becomes accessible again once the function returns.

Parameters
addrthe offset from start of flash to be erased
countnumber of bytes to erase
block_sizeoptional size of block erased by block_cmd
block_cmdoptional block erase command e.g. D8h block erase

◆ rom_flash_range_program()

static void rom_flash_range_program ( uint32_t  addr,
const uint8_t *  data,
size_t  count 
)
inlinestatic

Program bytes in flash.

Program data to a range of flash addresses starting at addr (offset from the start of flash) and count bytes in size. addr must be aligned to a 256-byte boundary, and count must be a multiple of 256.

This is a low-level flash API, and no validation of the arguments is performed.

See rom_flash_op on RP2350 for a higher-level API which checks alignment, flash bounds and partition permissions, and can transparently apply a runtime-to-storage address translation.

The QSPI device must be in a serial command state before calling this API - see notes on rom_flash_range_erase

Parameters
addrthe offset from start of flash to be erased
databuffer containing the data to be written
countnumber of bytes to erase

◆ rom_func_lookup()

void * rom_func_lookup ( uint32_t  code)

Lookup a bootrom function by its code.

Parameters
codethe code
Returns
a pointer to the function, or NULL if the code does not match any bootrom function

◆ rom_func_lookup_inline()

static __force_inline void * rom_func_lookup_inline ( uint32_t  code)
static

Lookup a bootrom function by code. This method is forcibly inlined into the caller for FLASH/RAM sensitive code usage.

Parameters
codethe code
Returns
a pointer to the function, or NULL if the code does not match any bootrom function

◆ rom_funcs_lookup()

bool rom_funcs_lookup ( uint32_t *  table,
unsigned int  count 
)

Helper function to lookup the addresses of multiple bootrom functions.

This method looks up the 'codes' in the table, and convert each table entry to the looked up function pointer, if there is a function for that code in the bootrom.

Parameters
tablean IN/OUT array, elements are codes on input, function pointers on success.
countthe number of elements in the table
Returns
true if all the codes were found, and converted to function pointers, false otherwise

◆ rom_reset_usb_boot()

void rom_reset_usb_boot ( uint32_t  usb_activity_gpio_pin_mask,
uint32_t  disable_interface_mask 
)

Reboot the device into BOOTSEL mode.

This function reboots the device into the BOOTSEL mode ('usb boot"). Facilities are provided to enable an "activity light" via GPIO attached LED for the USB Mass Storage Device, and to limit the USB interfaces exposed.

Parameters
usb_activity_gpio_pin_mask0 No pins are used as per a cold boot. Otherwise a single bit set indicating which GPIO pin should be set to output and raised whenever there is mass storage activity from the host.
disable_interface_maskvalue to control exposed interfaces
  • 0 To enable both interfaces (as per a cold boot)
  • 1 To disable the USB Mass Storage Interface
  • 2 To disable the USB PICOBOOT Interface

◆ rom_table_code()

static uint32_t rom_table_code ( uint8_t  c1,
uint8_t  c2 
)
inlinestatic

Return a bootrom lookup code based on two ASCII characters.

These codes are uses to lookup data or function addresses in the bootrom

Parameters
c1the first character
c2the second character
Returns
the 'code' to use in rom_func_lookup() or rom_data_lookup()