> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/intel/braswell/sbc-platform/solidpc-testpoints.md).

# SolidPC Testpoints

## Revision and Notes

| **Date**    | **Owner** | **Revision** | **Notes**       |
| ----------- | --------- | ------------ | --------------- |
| 19 Apr 2022 |           | 1.0          | Initial release |

## Description

Testpoints are designed to provide a secure anchoring point on a printed circuit board for j-hooks and miniature test leads.

## Carrierboard (Silk)

\[![](/files/IJizZ5OJoXbeTqkKNcPx)

]\(<https://developer.solid-run.com/wp-content/uploads/2018/10/sr-ibx-solidpc-rev1.2-component-side-silk.pdf)\\[![>]\(/files/5QTKjMeQQXkY7ShOke96)

]\(<https://developer.solid-run.com/wp-content/uploads/2018/10/sr-ibx-solidpc-rev1.2-print-side-silk.pdf>)

## Testpoints

**Power management**

![](/files/cOBpQxPqSXP7vh5Cnc4q)

**GPIOs and misc**

![](/files/IWHRgmieOX0JnFBExSJ8)

[**MCU: STM32**](https://developer.solid-run.com/knowledge-base/ib8000-drivers/)**PA1..PA4 pins**

![](/files/jiMpIohLNJk1Kk7iUMsS)

{% hint style="success" %}
**Missing TP-names on PCB:**
{% endhint %}

Few TP points are not named on the pcb:

* TP27
* TP21
* TP6
* TP7
* TP8
* TP3
* TP4
* TP5

Please see the pictures below:

![](/files/aJVhYrKGMMNSCfPBvZ71)

![](/files/kWoq5CHria7zjXWGcdqg)

## Detect all I2C busses

This patch can be used if not all I2C busses are detected:

```
--- drivers/i2c/busses/i2c-designware-baytrail.c	2016-10-22 12:41:00.000000000 +0200
+++ /tmp/i2c-designware-baytrail.c	2016-10-26 15:05:42.936807731 +0200
@@ -22,7 +22,7 @@
 #include "i2c-designware-core.h"
 
 #define SEMAPHORE_TIMEOUT	100
-#define PUNIT_SEMAPHORE		0x7
+#define PUNIT_SEMAPHORE		0x10e
 #define PUNIT_SEMAPHORE_BIT	BIT(0)
 #define PUNIT_SEMAPHORE_ACQUIRE	BIT(1)
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.solid-run.com/intel/braswell/sbc-platform/solidpc-testpoints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.