Recent posts

#21

STMP1 / Re: Olimex STM32MP1 Yocto

Last post by simonK - July 10, 2024, 05:21:46 PM

Hi,
no answers yet and also not for the other requests regarding yocto support in the forum.

I guess you can't permanently ignore a defacto standard like Yocto, we'll see...

#22

Neo6502 / Memmory when programming pure ...

Last post by powersoft - July 10, 2024, 02:48:46 PM

Hello,
I wont to install the wozmon monitor started at $FF00.
Is that allowed?

Cheers
Jan

#23

NXP / Re: Debugging IMX8MP SOM boot

Last post by LubOlimex - July 10, 2024, 08:38:44 AM

Yes, we've rebuild the image recently so it says July, the buildroot from the web-site should say May. This is not a problem.

Umm, I am not sure if the dd command you use is alright. I feel like you write to the second partition of the card by writing to da1, leaving some problematic partition on the card. Specifying the block size is not needed either. I have two suggestions:

1. Can you try preparing the card with:

sudo dd if=buildroot-202405212131.img of=/dev/da

If that still shows a problem, try:

2. Downloading the image to the card with free version of BalenaEtcher instead? This would exclude problems related to the preparation of the card.

Let me know how it goes.

#24

NXP / Re: Debugging IMX8MP SOM boot

Last post by thj - July 09, 2024, 07:01:23 PM

I have been creating the sd card like so:

<code>
$ curl -O http://images.olimex.com/release/imx8mp/buildroot-202405212131.img.gz
$ sha256sum buildroot-202405212131.img.gz
9422671397373070cecfc946677fa56b60b5af991a07cb7de7d16ecb29da1bc5  buildroot-202405212131.img.gz
$ gunzip buildroot-202405212131.img.gz
$ sha256sum
600d77b9c36b9769ae22e9f880644cba195862afb029dd3307c348c9d46386ab  buildroot-202405212131.img
$ file buildroot-202405212131.img
buildroot-202405212131.img: DOS/MBR boot sector; partition 1 : ID=0xc, active, start-CHS (0x1,5,5), end-CHS (0x9,45,36), startsector 16384, 131072 sectors; partition 2 : ID=0x83, start-CHS (0x9,45,37), end-CHS (0x18,121,33), startsector 147456, 245760 sectors
$ sudo dd if=buildroot-202405212131.img of=/dev/da1 bs=1m
$ gpart show da1
=>      63  15523777  da1  MBR  (7.4G)
        63     16321       - free -  (8.0M)
     16384    131072    1  fat32lba  [active]  (64M)
    147456    245760    2  linux-data  (120M)
    393216  15130624       - free -  (7.2G)
</code>

I just followed these steps and tested again.

I am using a tigard for serial configured at 1.8v. I verified the tigard serial is functioning by connecting it to a ch340 based usb serial and successfully sending bytes between the two devices. I think my usb serial is working.

When I could boot successfully the start of my log looked like this:

<code>
U-Boot SPL 2020.04 (May 21 2024 - 18:08:43 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE:  BL31: v2.4(release):2022.08-462-g759e1257e7
NOTICE:  BL31: Built : 13:35:27, May 21 2024


U-Boot 2020.04 (May 21 2024 - 18:08:43 +0000)

CPU:   i.MX8MP[8] rev1.1 1600 MHz (running at 1200 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 44C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 EVK board
DRAM:  4 GiB
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port2 init failed, err=-19
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port1 init failed, err=-19
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment
</code>

It looks like the uboot I have is different to the one you have. If I look in the image I downloaded just now it is also from May 21 2024.

<code>
$ strings buildroot-202405212131.img| grep "U-Boot SPL"
U-Boot SPL 2020.04 (May 21 2024 - 18:08:43 +0000)
</code>

When I could boot I would get errors on some boots leading to panics. I am wondering if maybe the connections in the sd card slot are bad in some way.

#25

NXP / Re: Debugging IMX8MP SOM boot

Last post by LubOlimex - July 09, 2024, 03:54:12 PM

I have no idea how you got any output without SD card. I can't get any output on the serial if I don't have SD card. Also the boot with card starts very different from what you got:

Code Select Expand

U-Boot SPL 2020.04 (Jul 05 2024 - 10:18:39 +0300)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE:  BL31: v2.4(release):2022.08-462-gcc43a0c3c5-dirty
NOTICE:  BL31: Built : 10:18:26, Jul  5 2024


U-Boot 2020.04 (Jul 05 2024 - 10:18:39 +0300)


#26

NXP / Re: Debugging IMX8MP SOM boot

Last post by LubOlimex - July 09, 2024, 03:38:07 PM

How do you download to the SD card? Did you try to re-download the archive with the image?

Can it be related to powering or serial debug cable?

#27

NXP / Re: Debugging IMX8MP SOM boot

Last post by thj - July 09, 2024, 11:44:25 AM

I don't get anything on serial when using the the buildroot image.

I have successfully booted the image, but can no longer.

I have tried:
- 5 different sd cards
- two different usb serial devices

#28

NXP / Re: Debugging IMX8MP SOM boot

Last post by LubOlimex - July 09, 2024, 09:21:34 AM

What is the error that you get when booting from the SD card with the buildroot? What do you get over the serial?

#29

A20 / Re: Interrupt EINT31(PI19)

Last post by EmmaAlva - July 09, 2024, 06:44:11 AM

It is similar to this:
https://www.olimex.com/forum/index.php?topic=4400.0

EINT are already supported in older sunxi images, and can be used as described in here:

https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3 tiny fishing.txt

Older sunxi images can be found at our FTP.

Thank you both. I was having the same problem and didn't know how to solve it until I read this article.

#30

NXP / Re: Debugging IMX8MP SOM boot

Last post by thj - July 08, 2024, 06:55:28 PM

Probing the SD card with an extension with a scope I see a short clock pulse on reset, but it stops quickly.

I have connected a jtag header, but I don't have 0402 10k resistors to add pull ups. Openocd with a tigard board detects a non-nxp device:


<code>
Info : JTAG tap: auto0.tap tap/device found: 0x1cf80553 (mfg: 0x2a9 (Telegent Systems USA Inc), part: 0xcf80, ver: 0x1)
</code>

I put together a usb cable with 5V removed, but D+ D- and GND connected through, but with the EVB set to usb serial boot I don't see any device enumerating. This was a guess for what the cable should be so it might be entirely wrong.

I'm a bit limited by tools I have a available and ideas for what to try that will make some progress figuring out why the som and evb aren't working together.