Re: QSPI for ATSAME51 #flash
Bolivar, Marti
Hi Theo,
"Theo Hussey via lists.zephyrproject.org" <theo=open-cosmos.com@...> writes: Hi,There is an extra unmatched "};" here. I'm assuming that is just a copy/paste issue in this email? It looks like a syntax error. [snip] zephyr/include/generated/devicetree_unfixed.h:4014:35: error: 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_P_label'?I'm going to explain what this mess means for the sake of the list archives before getting to what I am guessing the problem is. 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label' The 'DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0' part is the 'node identifier' for the gd25q16c@0 node. 'Node identifiers' are introduced here: https://docs.zephyrproject.org/latest/guides/dts/api-usage.html#node-identifiers The secret decoder ring for unpacking node identifiers is: - 'DT_N' -> 'devicetree node' - '_S_' -> '/' - all special characters become '_' So that: DT_N_S_soc_S_qspi_42003400_S_gd25q16c_0_BUS_P_label becomes: devicetree node /soc/qspi@42003400/gd25q16c@0 _BUS_P_label The trailing '_BUS_P_label' is just the devicetree API trying to figure out what the 'label' property of the bus node for /soc/qspi@42003400/gd25q16c@0 is. I also see: - 'qspi@42003400' does have a label property in your DTS, "QSPI_0" - its compatible, 'atmel,sam0-qspi', is not upstream So I'm guessing that the problem is: - you've got a custom binding for 'atmel,sam0-qspi', - it is a missing a 'bus: qspi' line Example binding with a 'bus: qspi' line: https://github.com/zephyrproject-rtos/zephyr/blob/master/dts/bindings/qspi/st%2Cstm32-qspi.yaml#L23 If that line is missing, please add it and try again. Otherwise please provide more details on your binding. Thanks and HTH, MartÃ
|
|