Activity
From 03/22/2026 to 04/20/2026
04/16/2026
- MW 08:13 PM MitySOM-QC6490 Software Development: RE: SPI bringup
- Hi Nathan,
I think you can remove the NFC pins and give it a shot.
-Mike - NO 07:49 PM MitySOM-QC6490 Software Development: RE: SPI bringup
- The original commit message for those lines is "Add gpio-reserved-ranges for QCM6490 boards."
In mainline linux, I found the following in qcs6490-rb3gen2.dts: - NO 07:01 PM MitySOM-QC6490 Software Development: RE: SPI bringup
- Edit: The boot crash in unrelated and I've resolved that. However, SPI configuration still fails:
04/15/2026
- Are there any reference examples of software using SPI? I'm attempting to configure the QUP to use SPI on my carrier board.
Here's my device tree modification:
04/13/2026
- WE 04:19 PM MitySOM-QC6490 PCB Development: RE: 4V on 3V3-SOM!
- Unfortunately this cannot be addressed on the SOM as the SOM will hang if this voltage is dropped lower than 4V.
For future baseboard revisions there will need to be a regulator in between the SOM and the downstream components on this... - NO 04:06 PM MitySOM-QC6490 PCB Development: RE: 4V on 3V3-SOM!
- Thanks Will. The pins are tied directly to a power plane on my prototype boards, so I'll try breaking the connector pins as you suggest.
Will this issue be fixed in later versions of the SOM, or should I plan on adding a 3V3 regulator... - WE 01:07 PM MitySOM-QC6490 PCB Development: RE: 4V on 3V3-SOM!
- Hello Nathan,
The PMICs on the SOM support changing the output voltage of this pin. The idea was to have it at 3.3V but unfortunately the SOM hangs if this voltage is lower than 4V.
As a result we had to re-spin our development boa...
04/11/2026
- Hello,
Why is 3V3-SOM outputting 4V? Is there a way to change this to 3.3V?
I see that the devkit schematic shows it as 4V, but the datasheet and Carrier Board Design Guide (and the name!) show it as 3.3V. Unfortunately I just rece...
03/30/2026
- SY 02:45 PM MitySOM-C10GX Firmware: RE: CLKUSR - Oscillator Specs?
- Hi Mike,
Thanks for providing the oscillator part number, this is very helpful!
- Sean
03/27/2026
- MF 05:27 PM MitySOM-C10GX Firmware: RE: CLKUSR - Oscillator Specs?
- Hi Sean,
The oscillator that is driving the CLKUSR pin is *KC2520Z100.000C15XXK*. Per the datasheet, this is a 30 ppm oscillator.
- Mike - What is the frequency tolerance and stability (in PPM) of the 100 MHz oscillator used to drive the CLKUSR pin on the SOM? I cannot seem to find this information in the SOM datasheet.
For context, my design contains an elastic FIFO us...
03/26/2026
- JC 02:09 PM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Using WKUP_UART0 in Linux Space
- If your able, please jump in and respond to them directly and I'll monitor and i'll jump in as needed.
- JC 01:56 PM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Using WKUP_UART0 in Linux Space
- Holden, TI wants to know if you are using the "VPAC/ISP camera functionality on your AM62A7". Presumably to determine if you need the dm_edgeai firmware or if you can get away with just the normal "ipc_echo_testb_mcu1_0_release_strip.xe...
03/25/2026
- JC 08:41 PM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Using WKUP_UART0 in Linux Space
- I just responded to your support email but will put my response here as well so others can benifit.
Holden Wozniak wrote:
> Hi,
> ...
As you noted in your email, the DM firmware is baked into the tispl.bin u-boot file. Linux doesn'... - Hi,
I am having some difficulty bringing up a serial port that utilizes WKUP_UART0 pins. From what I understand, it is typically reserved for DM logging and is unusuable in Linux until it is disabled. I have disabled the UART log for ... - EH 05:53 PM MitySBC-Agilex5 FPGA Development: RE: Where can I find the schematic for MitySBC_Agilex5
- Thank you Mike.
We currently have SBC and SOM Dev kit. We were told that they are equivalent from FPGA connections point of view, but I found out that's not completely correct.
I need the schematic to figure out which FPGA pins and how...
03/24/2026
- NO 03:46 PM MitySOM-QC6490 Software Development: RE: Long build times
- That matches what I'm seeing, although it seems your machine is much faster than mine. For me it's about 7 hours for a clean build, and 28 minutes for a rebuild.
- GG 02:36 AM MitySOM-QC6490 Software Development: RE: Long build times
- Hi Nathan,
We have similar experiences. Unfortunately we do not currently have a fix. We are building off of Qualcomm's methodology and there is a lot of complexity there that we haven't needed to dig into yet. We will update this is... - JC 01:26 PM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Uart issue in Am62P
- Thanks for the update
- RD 11:44 AM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Uart issue in Am62P
- Hi Jonathan,
The issue was in the code. We have a function that returns an int, but the application was crashing within that function when running on the AM62P with Debian OS. However, it works fine on the AM62A BSP.
I suspect the ... - MW 09:37 AM MitySBC-Agilex5 FPGA Development: RE: Where can I find the schematic for MitySBC_Agilex5
- Hi Eleonora,
I was advised that you are working with our "MitySOM-A5E":https://www.criticallink.com/product/mitysom-a5e-standard-dev-kit/ product vs. our "MitySBC-A5E":https://www.criticallink.com/product/mitysbc-a5e-single-board-comp... - GG 02:42 AM MitySOM-QC6490 Software Development: RE: Configuring the QUP pins
- Hi Nathan,
Please refer to the [[Configuring the QUP Ports (I2C I3C SPI and UART)]] wiki page which has recently been published for details on how to do this.
Let me know if you have any questions or issues.
Thanks,
Greg
03/23/2026
- JC 01:51 PM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Uart issue in Am62P
- Thanks for the update. Would you mind sharing what the solution was?
- RD 05:44 AM MitySOM-AM62, MitySOM-AM62A, & MitySOM-AM62P Software Development: RE: Uart issue in Am62P
- Hi Jonathan,
I was on a long vacation until recently. The issue has now been fixed.
Best regards,
Rajkumar.