[U-Boot] [RFC 0/9] Convert Pico-Pi i.MX7D to DM
Hi all,
Pinctrl, GPIO, I2C, MMC, ETH are converted.
Convert PMIC is the same of warp7 but i have a some erros, si this log : U-Boot SPL 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100) Trying to boot from USB SDP SDP: initialize... SDP: handle requests... Downloading file of size 556397 to 0x877fffc0... done Jumping to header at 0x877fffc0 Header Tag is not an IMX image
U-Boot 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100)
CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 43C Reset cause: POR Model: TechNexion PICO-IMX7D Board and PI baseboard Board: i.MX7D PICOSOM DRAM: 512 MiB read error from device: 9df65458 register: 0x3! PMIC: PFUZE3000 DEV_ID=0x0 REV_ID=0xfffffffb read error from device: 9df65458 register: 0x69! write error to device: 9df65458 register: 0x23! write error to device: 9df65458 register: 0x31! write error to device: 9df65458 register: 0x21! write error to device: 9df65458 register: 0x2f! read error from device: 9df65458 register: 0x2e! write error to device: 9df65458 register: 0x2e! MMC: FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@30a70000 Out: serial@30a70000 Err: serial@30a70000 Net: Warning: ethernet@30be0000 using MAC address from ROM eth0: ethernet@30be0000 Hit any key to stop autoboot: 0
USB is convert but update u-boot with dfu log a error :
=> dfu 0 mmc 0 Request would exceed designated area! #Deferred dfu_flush() failed!=>
Thanks a advance for your help.
Best Regards,
Joris Offouga
Joris Offouga (9): Arm: dts: imx7d-pico: Import Linux pico-pi dts Arm: imx7d-pico: Add DT file hooks pico-pi-imx7d: defconfig Enable DM gpio pinctrl and pinctrl_imx7 arm: imx7d-pico-pi: Convert to DM MMC initialization pico-pi-imx7d: defconfig: Switch to DM for I2C pico-imx7d-pico: defconfig: Switch to DM for UART pico-imx7d: Convert to DM PMIC arm: pico-pi-imx7d: Convert to DM USB pico-imx7d: Convert to DM Ethernet
arch/arm/dts/Makefile | 3 +- arch/arm/dts/imx7d-pico-pi.dts | 102 ++++++ arch/arm/dts/imx7d-pico.dtsi | 588 +++++++++++++++++++++++++++++++ board/technexion/pico-imx7d/pico-imx7d.c | 105 +----- configs/pico-pi-imx7d_defconfig | 17 +- include/configs/pico-imx7d.h | 11 - 6 files changed, 726 insertions(+), 100 deletions(-) create mode 100644 arch/arm/dts/imx7d-pico-pi.dts create mode 100644 arch/arm/dts/imx7d-pico.dtsi
On Sun, 20 Jan 2019 23:38:32 +0100 Joris Offouga offougajoris@gmail.com wrote:
Hi all,
Pinctrl, GPIO, I2C, MMC, ETH are converted.
Convert PMIC is the same of warp7 but i have a some erros, si this log : U-Boot SPL 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100) Trying to boot from USB SDP SDP: initialize... SDP: handle requests... Downloading file of size 556397 to 0x877fffc0... done Jumping to header at 0x877fffc0 Header Tag is not an IMX image
U-Boot 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100)
CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 43C Reset cause: POR Model: TechNexion PICO-IMX7D Board and PI baseboard Board: i.MX7D PICOSOM DRAM: 512 MiB read error from device: 9df65458 register: 0x3! PMIC: PFUZE3000 DEV_ID=0x0 REV_ID=0xfffffffb read error from device: 9df65458 register: 0x69! write error to device: 9df65458 register: 0x23! write error to device: 9df65458 register: 0x31! write error to device: 9df65458 register: 0x21! write error to device: 9df65458 register: 0x2f! read error from device: 9df65458 register: 0x2e! write error to device: 9df65458 register: 0x2e! MMC: FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@30a70000 Out: serial@30a70000 Err: serial@30a70000 Net: Warning: ethernet@30be0000 using MAC address from ROM eth0: ethernet@30be0000 Hit any key to stop autoboot: 0
USB is convert but update u-boot with dfu log a error :
=> dfu 0 mmc 0 Request would exceed designated area! #Deferred dfu_flush() failed!=>
Please check if malloc pool size (in Kconfig) is large enough to handle DFU requests.
Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c and share output.
Thanks a advance for your help.
Best Regards,
Joris Offouga
Joris Offouga (9): Arm: dts: imx7d-pico: Import Linux pico-pi dts Arm: imx7d-pico: Add DT file hooks pico-pi-imx7d: defconfig Enable DM gpio pinctrl and pinctrl_imx7 arm: imx7d-pico-pi: Convert to DM MMC initialization pico-pi-imx7d: defconfig: Switch to DM for I2C pico-imx7d-pico: defconfig: Switch to DM for UART pico-imx7d: Convert to DM PMIC arm: pico-pi-imx7d: Convert to DM USB pico-imx7d: Convert to DM Ethernet
arch/arm/dts/Makefile | 3 +- arch/arm/dts/imx7d-pico-pi.dts | 102 ++++++ arch/arm/dts/imx7d-pico.dtsi | 588 +++++++++++++++++++++++++++++++ board/technexion/pico-imx7d/pico-imx7d.c | 105 +----- configs/pico-pi-imx7d_defconfig | 17 +- include/configs/pico-imx7d.h | 11 - 6 files changed, 726 insertions(+), 100 deletions(-) create mode 100644 arch/arm/dts/imx7d-pico-pi.dts create mode 100644 arch/arm/dts/imx7d-pico.dtsi
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
Le 22/01/2019 à 10:47, Lukasz Majewski a écrit :
On Sun, 20 Jan 2019 23:38:32 +0100 Joris Offouga offougajoris@gmail.com wrote:
Hi all,
Pinctrl, GPIO, I2C, MMC, ETH are converted.
Convert PMIC is the same of warp7 but i have a some erros, si this log : U-Boot SPL 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100) Trying to boot from USB SDP SDP: initialize... SDP: handle requests... Downloading file of size 556397 to 0x877fffc0... done Jumping to header at 0x877fffc0 Header Tag is not an IMX image
U-Boot 2019.01-00197-ga524e5d-dirty (Jan 20 2019 - 21:09:49 +0100)
CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 43C Reset cause: POR Model: TechNexion PICO-IMX7D Board and PI baseboard Board: i.MX7D PICOSOM DRAM: 512 MiB read error from device: 9df65458 register: 0x3! PMIC: PFUZE3000 DEV_ID=0x0 REV_ID=0xfffffffb read error from device: 9df65458 register: 0x69! write error to device: 9df65458 register: 0x23! write error to device: 9df65458 register: 0x31! write error to device: 9df65458 register: 0x21! write error to device: 9df65458 register: 0x2f! read error from device: 9df65458 register: 0x2e! write error to device: 9df65458 register: 0x2e! MMC: FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@30a70000 Out: serial@30a70000 Err: serial@30a70000 Net: Warning: ethernet@30be0000 using MAC address from ROM eth0: ethernet@30be0000 Hit any key to stop autoboot: 0
USB is convert but update u-boot with dfu log a error :
=> dfu 0 mmc 0 Request would exceed designated area! #Deferred dfu_flush() failed!=>
Hi Lukasz,
Please check if malloc pool size (in Kconfig) is large enough to handle DFU requests.
The dfu request is smaller than the size of malloc pool size
Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c and share output.
This is a log when dfu failed :
blk_find_device: if_type=6, devnum=0: usdhc@30b40000.blk, 6, 2 blk_find_device: if_type=6, devnum=0: usdhc@30b50000.blk, 6, 1 blk_find_device: if_type=6, devnum=0: usdhc@30b60000.blk, 6, 0 Request would exceed designated area! dfu_write_buffer_drain: Write error! #Deferred dfu_flush() failed!reset_config: unbind function 'dfu'/9ef6e678 g_dnl_unbind: calling usb_gadget_disconnect for controller 'ci_udc'
Best Regards,
Joris Offouga
Thanks a advance for your help.
Best Regards,
Joris Offouga
Joris Offouga (9): Arm: dts: imx7d-pico: Import Linux pico-pi dts Arm: imx7d-pico: Add DT file hooks pico-pi-imx7d: defconfig Enable DM gpio pinctrl and pinctrl_imx7 arm: imx7d-pico-pi: Convert to DM MMC initialization pico-pi-imx7d: defconfig: Switch to DM for I2C pico-imx7d-pico: defconfig: Switch to DM for UART pico-imx7d: Convert to DM PMIC arm: pico-pi-imx7d: Convert to DM USB pico-imx7d: Convert to DM Ethernet
arch/arm/dts/Makefile | 3 +- arch/arm/dts/imx7d-pico-pi.dts | 102 ++++++ arch/arm/dts/imx7d-pico.dtsi | 588 +++++++++++++++++++++++++++++++ board/technexion/pico-imx7d/pico-imx7d.c | 105 +----- configs/pico-pi-imx7d_defconfig | 17 +- include/configs/pico-imx7d.h | 11 - 6 files changed, 726 insertions(+), 100 deletions(-) create mode 100644 arch/arm/dts/imx7d-pico-pi.dts create mode 100644 arch/arm/dts/imx7d-pico.dtsi
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
Hi Lukasz,
On Wed, Jan 23, 2019 at 7:01 PM Joris Offouga offougajoris@gmail.com wrote:
Hi Lukasz,
Please check if malloc pool size (in Kconfig) is large enough to handle DFU requests.
The dfu request is smaller than the size of malloc pool size
Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c and share output.
This is a log when dfu failed :
blk_find_device: if_type=6, devnum=0: usdhc@30b40000.blk, 6, 2 blk_find_device: if_type=6, devnum=0: usdhc@30b50000.blk, 6, 1 blk_find_device: if_type=6, devnum=0: usdhc@30b60000.blk, 6, 0 Request would exceed designated area! dfu_write_buffer_drain: Write error! #Deferred dfu_flush() failed!reset_config: unbind function 'dfu'/9ef6e678 g_dnl_unbind: calling usb_gadget_disconnect for controller 'ci_udc'
Do you have any idea on this issue, please?
This DFU bug is one of the items that is blocking the DM conversion of this board.
Thanks
Hi Fabio,
Hi Lukasz,
On Wed, Jan 23, 2019 at 7:01 PM Joris Offouga offougajoris@gmail.com wrote:
Hi Lukasz,
Please check if malloc pool size (in Kconfig) is large enough to handle DFU requests.
The dfu request is smaller than the size of malloc pool size
Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c and share output.
This is a log when dfu failed :
blk_find_device: if_type=6, devnum=0: usdhc@30b40000.blk, 6, 2 blk_find_device: if_type=6, devnum=0: usdhc@30b50000.blk, 6, 1 blk_find_device: if_type=6, devnum=0: usdhc@30b60000.blk, 6, 0 Request would exceed designated area!
Please carefully check the eMMC partition size (as defined in dfu_alt_info) and the size of sent data.
This error happens when one wants to write bigger file than the reported space on the partition.
Please look at drivers/dfu/dfu_mmc.c Line: 44
dfu_write_buffer_drain: Write error! #Deferred dfu_flush() failed!reset_config: unbind function 'dfu'/9ef6e678 g_dnl_unbind: calling usb_gadget_disconnect for controller 'ci_udc'
Do you have any idea on this issue, please?
This DFU bug is one of the items that is blocking the DM conversion of this board.
Thanks
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
Le 15 févr. 2019 à 12:50, Lukasz Majewski lukma@denx.de a écrit :
Hi Fabio,
Hi Lukasz,
On Wed, Jan 23, 2019 at 7:01 PM Joris Offouga offougajoris@gmail.com wrote:
Hi Lukasz,
Please check if malloc pool size (in Kconfig) is large enough to handle DFU requests.
The dfu request is smaller than the size of malloc pool size
Otherwise, please #define DEBUG in ./drivers/dfu.c and dfu_mmc.c and share output.
This is a log when dfu failed :
blk_find_device: if_type=6, devnum=0: usdhc@30b40000.blk, 6, 2 blk_find_device: if_type=6, devnum=0: usdhc@30b50000.blk, 6, 1 blk_find_device: if_type=6, devnum=0: usdhc@30b60000.blk, 6, 0 Request would exceed designated area!
Please carefully check the eMMC partition size (as defined in dfu_alt_info) and the size of sent data.
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
Best Regards
Joris Offouga
This error happens when one wants to write bigger file than the reported space on the partition.
Please look at drivers/dfu/dfu_mmc.c Line: 44
dfu_write_buffer_drain: Write error! #Deferred dfu_flush() failed!reset_config: unbind function 'dfu'/9ef6e678 g_dnl_unbind: calling usb_gadget_disconnect for controller 'ci_udc'
Do you have any idea on this issue, please?
This DFU bug is one of the items that is blocking the DM conversion of this board.
Thanks
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
Hi Joris,
On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
What is the U-Boot size you used in the dfu_alt_info?
What is the error you see in SPL now?
Thanks
On Sat, Feb 16, 2019 at 10:17 AM Fabio Estevam festevam@gmail.com wrote:
Hi Joris,
On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
What is the U-Boot size you used in the dfu_alt_info?
What is the error you see in SPL now?
Also, imx7 is missing the u-boot,dm-spl properties.
Take a look at imx6ul, for example:
git grep u-boot,dm-spl | grep mx6ul
And see if doing the same for mx7 works.
Thanks
Le 16/02/2019 à 13:17, Fabio Estevam a écrit :
Hi Joris,
On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
What is the U-Boot size you used in the dfu_alt_info?
"u-boot raw 0x8a 0x1000"
What is the error you see in SPL now?
See this log : U-Boot SPL 2019.04-rc1-00142-g7fe4b77-dirty (Feb 15 2019 - 20:11:50 +0100) Trying to boot from MMC1
Thanks
Thanks
On Sat, Feb 16, 2019 at 10:34 AM Joris Offouga offougajoris@gmail.com wrote:
Le 16/02/2019 à 13:17, Fabio Estevam a écrit :
Hi Joris,
On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
What is the U-Boot size you used in the dfu_alt_info?
"u-boot raw 0x8a 0x1000"
The original setting was correct: u-boot-dtb.img needs to be flashed at the position 69kB of the eMMC.
Originally we had:
u-boot raw 0x8a 0x400;
which means: 0x8a = 138 * 0x400 = 138 * 1024 = 138 sectors. Each sector is 512 bytes, so 138*0.5k = 69kB
Could you also try:
u-boot raw 0x45 0x800
Does it make any difference?
Le 16/02/2019 à 13:46, Fabio Estevam a écrit :
On Sat, Feb 16, 2019 at 10:34 AM Joris Offouga offougajoris@gmail.com wrote:
Le 16/02/2019 à 13:17, Fabio Estevam a écrit :
Hi Joris,
On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio
I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
What is the U-Boot size you used in the dfu_alt_info?
"u-boot raw 0x8a 0x1000"
The original setting was correct: u-boot-dtb.img needs to be flashed at the position 69kB of the eMMC.
Originally we had:
u-boot raw 0x8a 0x400;
which means: 0x8a = 138 * 0x400 = 138 * 1024 = 138 sectors. Each sector is 512 bytes, so 138*0.5k = 69kB
Could you also try:
u-boot raw 0x45 0x800
Does it make any difference?
Yes , download with dfu it's okay but after rebooting the SPL does not load.
For u-boot, dm-spl, this does not work only if the SPL is converted to DM too, because the add-on in the uscdh3 node did not change the problem of loading the U-Boot
On Sat, Feb 16, 2019 at 11:02 AM Joris Offouga offougajoris@gmail.com wrote:
Yes , download with dfu it's okay but after rebooting the SPL does not load.
Does it boot if you flash SPL and u-boot-dtb.img via "ums 0 mmc 0" command?
Le 16/02/2019 à 14:58, Fabio Estevam a écrit :
On Sat, Feb 16, 2019 at 11:02 AM Joris Offouga offougajoris@gmail.com wrote:
Yes , download with dfu it's okay but after rebooting the SPL does not load.
Does it boot if you flash SPL and u-boot-dtb.img via "ums 0 mmc 0" command?
By doing this the SPL still does not find the U-Boot binary always this same log:
U-Boot SPL 2019.04-rc1-00142-g7fe4b77-dirty (Feb 16 2019 - 13:58:30 +0100) Trying to boot from MMC1
Hi Joris,
On Sat, Feb 16, 2019 at 12:38 PM Joris Offouga offougajoris@gmail.com wrote:
By doing this the SPL still does not find the U-Boot binary always this same log:
U-Boot SPL 2019.04-rc1-00142-g7fe4b77-dirty (Feb 16 2019 - 13:58:30 +0100) Trying to boot from MMC1
Yes, just tried it and I saw the same here.
I started from scratch and used top of tree U-Boot.
When I load it via USB I see a hang:
CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 50C Reset cause: POR Board: i.MX7D PICOSOM I2C: ready DRAM: 512 MiB ...
So this is a regression and I will try to bisect it.
Le 16/02/2019 à 15:42, Fabio Estevam a écrit :
Hi Joris,
Hi Fabio,
On Sat, Feb 16, 2019 at 12:38 PM Joris Offouga offougajoris@gmail.com wrote:
By doing this the SPL still does not find the U-Boot binary always this same log:
U-Boot SPL 2019.04-rc1-00142-g7fe4b77-dirty (Feb 16 2019 - 13:58:30+0100) Trying to boot from MMC1
Yes, just tried it and I saw the same here.
I started from scratch and used top of tree U-Boot.
When I load it via USB I see a hang:
CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 50C Reset cause: POR Board: i.MX7D PICOSOM I2C: ready DRAM: 512 MiB ...
So this is a regression and I will try to bisect it.
Ok, thanks for your help :).
I worked new commits do you want me to update the RFC in v2?
Best Regards,
Joris
On Sat, Feb 16, 2019 at 12:52 PM Joris Offouga offougajoris@gmail.com wrote:
Ok, thanks for your help :).
I worked new commits do you want me to update the RFC in v2?
Please generate your series against the latest u-boot-imx tree.
However, I observed the hang when I use the latest u-boot or u-boot-imx tree, so we will need to fix the hang problem first.
Thanks
Le 16/02/2019 à 15:54, Fabio Estevam a écrit :
On Sat, Feb 16, 2019 at 12:52 PM Joris Offouga offougajoris@gmail.com wrote:
Ok, thanks for your help :).
I worked new commits do you want me to update the RFC in v2?
Please generate your series against the latest u-boot-imx tree.
However, I observed the hang when I use the latest u-boot or u-boot-imx tree, so we will need to fix the hang problem first.
Actually on the top of u-boot-imx there is a blocking when loading u-boot-dtb.img with imx_usb_loader.
I show you my log:
U-Boot SPL 2019.04-rc1-dirty (Feb 16 2019 - 16:10:56 +0100) Trying to boot from USB SDP SDP: initialize... SDP: handle requests... Downloading file of size 530520 to 0x877fffc0... done Jumping to header at 0x877fffc0 Header Tag is not an IMX image
I will send the series with the status rfc and not patch you are from okay ?
Thanks
Thanks
On Sat, Feb 16, 2019 at 1:14 PM Joris Offouga offougajoris@gmail.com wrote:
Actually on the top of u-boot-imx there is a blocking when loading u-boot-dtb.img with imx_usb_loader.
Just run a "git bisect" and the problem comes from:
commit 9e3c0174da842dd88f5feaffbf843ba332233897 (refs/bisect/bad) Author: Fabio Estevam festevam@gmail.com Date: Tue Dec 11 16:40:38 2018 -0200
pico-imx7d: Add LCD support
Add support for the VXT VL050-8048NT-C01 panel connected through the 24 bit parallel LCDIF interface.
Signed-off-by: Fabio Estevam festevam@gmail.com Signed-off-by: Otavio Salvador otavio@ossystems.com.br
It used to work at some point as I could see the splashscreen logo in the screen.
Please revert it from your tree and see if it works for you.
I will need to investigate why my commit broke the boot, but for now just revert it locally so that you can continue the DM conversion.
Thanks
Le 16/02/2019 à 16:25, Fabio Estevam a écrit :
On Sat, Feb 16, 2019 at 1:14 PM Joris Offouga offougajoris@gmail.com wrote:
Actually on the top of u-boot-imx there is a blocking when loading u-boot-dtb.img with imx_usb_loader.
Just run a "git bisect" and the problem comes from:
commit 9e3c0174da842dd88f5feaffbf843ba332233897 (refs/bisect/bad) Author: Fabio Estevam festevam@gmail.com Date: Tue Dec 11 16:40:38 2018 -0200
pico-imx7d: Add LCD support Add support for the VXT VL050-8048NT-C01 panel connected through the 24 bit parallel LCDIF interface. Signed-off-by: Fabio Estevam <festevam@gmail.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>It used to work at some point as I could see the splashscreen logo in the screen.
Please revert it from your tree and see if it works for you.
I will need to investigate why my commit broke the boot, but for now just revert it locally so that you can continue the DM conversion.
I reversed your commit but the block is still there, but even with
your commit on the top of the u-boot master.
I don't have the block with imx_usb_loader just when I try to boot from the emmc
Thanks
On Sat, Feb 16, 2019 at 1:41 PM Joris Offouga offougajoris@gmail.com wrote:
I reversed your commit but the block is still there, but even with
your commit on the top of the u-boot master.
I don't have the block with imx_usb_loader just when I try to boot from the emmc
Ops, it seems we have different issues going on.
I think you would need to run "git bisect" to find out what breaks your boot case.
Le 16 févr. 2019 à 16:43, Fabio Estevam festevam@gmail.com a écrit :
On Sat, Feb 16, 2019 at 1:41 PM Joris Offouga offougajoris@gmail.com wrote:
I reversed your commit but the block is still there, but even with
your commit on the top of the u-boot master.
I don't have the block with imx_usb_loader just when I try to boot from the emmc
Ops, it seems we have different issues going on.
Hi Fabio, Have you been able to solve your bug? I think that the coming must come from yours and that with the conversion dm that I have in local it must persist
Best Regards
Joris
I think you would need to run "git bisect" to find out what breaks your boot case.
Hi Joris,
On Tue, Feb 19, 2019 at 4:24 PM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio, Have you been able to solve your bug? I think that the coming must come from yours and that with the conversion dm that I have in local it must persist
Unfortunately, I haven't had a chance to debug this further.
If you make progress, please let us know.
Regards,
Fabio Estevam
Hi Joris,
On Sat, Feb 16, 2019 at 1:25 PM Fabio Estevam festevam@gmail.com wrote:
Just run a "git bisect" and the problem comes from:
commit 9e3c0174da842dd88f5feaffbf843ba332233897 (refs/bisect/bad) Author: Fabio Estevam festevam@gmail.com Date: Tue Dec 11 16:40:38 2018 -0200
pico-imx7d: Add LCD support Add support for the VXT VL050-8048NT-C01 panel connected through the 24 bit parallel LCDIF interface. Signed-off-by: Fabio Estevam <festevam@gmail.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>It used to work at some point as I could see the splashscreen logo in the screen.
Just a quick update: if I boot from eMMC I don't see this video related hang. I only see the hang when I boot from USB.
Le 28 févr. 2019 à 21:38, Fabio Estevam festevam@gmail.com a écrit :
Hi Joris,
On Sat, Feb 16, 2019 at 1:25 PM Fabio Estevam festevam@gmail.com wrote:
Just run a "git bisect" and the problem comes from:
commit 9e3c0174da842dd88f5feaffbf843ba332233897 (refs/bisect/bad) Author: Fabio Estevam festevam@gmail.com Date: Tue Dec 11 16:40:38 2018 -0200
pico-imx7d: Add LCD support
Add support for the VXT VL050-8048NT-C01 panel connected through the 24 bit parallel LCDIF interface.
Signed-off-by: Fabio Estevam festevam@gmail.com Signed-off-by: Otavio Salvador otavio@ossystems.com.br
It used to work at some point as I could see the splashscreen logo in the screen.
Just a quick update: if I boot from eMMC I don't see this video related hang. I only see the hang when I boot from USB.
I do not have the screen connected when I do my tests and I disabled CONFIG_VIDEO because it lacks the GPIOs for the screen in the current device tree
Le 28 févr. 2019 à 23:06, Offouga Joris offougajoris@gmail.com a écrit :
Le 28 févr. 2019 à 21:38, Fabio Estevam festevam@gmail.com a écrit :
Hi Joris,
On Sat, Feb 16, 2019 at 1:25 PM Fabio Estevam festevam@gmail.com wrote:
Just run a "git bisect" and the problem comes from:
commit 9e3c0174da842dd88f5feaffbf843ba332233897 (refs/bisect/bad) Author: Fabio Estevam festevam@gmail.com Date: Tue Dec 11 16:40:38 2018 -0200
pico-imx7d: Add LCD support
Add support for the VXT VL050-8048NT-C01 panel connected through the 24 bit parallel LCDIF interface.
Signed-off-by: Fabio Estevam festevam@gmail.com Signed-off-by: Otavio Salvador otavio@ossystems.com.br
It used to work at some point as I could see the splashscreen logo in the screen.
Just a quick update: if I boot from eMMC I don't see this video related hang. I only see the hang when I boot from USB.
I do not have the screen connected when I do my tests and I disabled CONFIG_VIDEO because it lacks the GPIOs for the screen in the current device tree
Hi Fabio,
I revert the commit about add lcd and on u-boot master and u-boot imx i have the u-boot is flashed correctly in usb and dfu.
do you agree that I send the revert of the commit?
Best Regards, Joris
Hi Joris,
On Sat, Mar 9, 2019 at 7:21 PM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio,
I revert the commit about add lcd and on u-boot master and u-boot imx i have the u-boot is flashed correctly in usb and dfu.
do you agree that I send the revert of the commit?
Yes, please revert it for now and resubmit your series that converts pico mx7 to DM.
So the only issue now is the I2C errors?
Thanks,
Fabio Estevam
Le 10/03/2019 à 15:24, Fabio Estevam a écrit :
Hi Joris,
On Sat, Mar 9, 2019 at 7:21 PM Offouga Joris offougajoris@gmail.com wrote:
Hi Fabio,
I revert the commit about add lcd and on u-boot master and u-boot imx i have the u-boot is flashed correctly in usb and dfu.
do you agree that I send the revert of the commit?
Yes, please revert it for now and resubmit your series that converts pico mx7 to DM.
Ok, i send revert add lcd
So the only issue now is the I2C errors?
No, I have not solved the problem of the spl that can not find the u-boot-dtb.img in the emmc.
I think the problem comes from the dfu_alt_info we already talked about it but the solution with raw u-boot 0x45 800 does not work do you have another idea?
Thanks,
Joris Offouga
Thanks,
Fabio Estevam
participants (4)
-
Fabio Estevam -
Joris Offouga -
Lukasz Majewski -
Offouga Joris