Hi Dmitry,

Are you saying that you are using a Linux machine and not Windows?  Panel+ only runs on Windows OS.
I don't know the cabling numbers very well (or at all) but according to the EAN-Recovery: https://sightlineapplications.com/wp-content/uploads/EAN-OEM-Recovery.pdf, SLA-CAB-0304 should be connected to the J4 connector of the 4000-DEBUG board.  You are NOT using the 0304 cable?  I have a 3pinto serial connector on J4 of the 4000-Recovery board, then a serial to USB adapter connected to that so that I can plug the USB end into my PC.  I also have the micro-USB to USB A connected to the 4000-Recovery  at J2 (and then connected to my PC).  From the above EAN, "The 4000-DEBUG board is powered by the 5V supplied by the SLA-CAB-USB-mUSB cable on J2."  I have never used the Power on J3 of the 4000-Recovery (and I cannot find where this is documented).

Once you get the serial Debug working, you should be able to enter fastboot mode by pushing (and holding) the blue button on the 4000-Recovery board (see above document).  Then you can fastboot versions of your kernel.

If you could,  it would be easiest if you took a picture(s) of your setup.  Out of the items you mentioned that you aren't using, I think 0304 is needed.  0404 is only needed if you have an SLA-DIST board.  I don't know what the USBto3pin is.

Thanks,
Kim

-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Sent: Thursday, January 19, 2023 11:34 PM
To: Kim Steiner <kim.steiner@sightlineapplications.com>
Cc: Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report

Hi Kim

On 17/01/2023 16:17, Kim Steiner wrote:
> Hi Dmitry,
>
> Also, did you take a look at the startup guide for the 4000?  Or maybe it was still confusing?
> https://sightlineapplications.com/wp-content/uploads/EAN-Startup-Guide
> -4000-OEM.pdf

Yes, following this document allowed me to make some progress. The board powers up, gets IP address via DHCP and displays a diagonal cross over the HDMI ("No Video Source Available" message jumping all over it).

However:
- I attached the provided USB-Serial connector to the J4 on the "recovery" board. I see nothing on the serial line. Is it a correct way to get the serial console from the unit?

- If I try attaching the microUSB cable to the J2 connector on recovery board, my laptop shows "usb port overcurrent" messages.

- The PanelPlus software seems to be available only for Windows machines. I tried using it with the Wine and with CrossOver, but the software crashed as soon as I tried connecting to the board.

So, few questions to proceed:
- How do I get the serial console?
- Do I need to connect any power supply to the recovery board? the label "power" near J3 connector hints that
- How can I test my own kernels? This is probably connected to the previous two questions.
- I have the following cables left unattached: 0304, 0504, 1505, 0402, 0404, TC2USB, the USB-to-3pin. Is this correct?

>
> Thanks,
> Kim
>
> -----Original Message-----
> From: Kim Steiner
> Sent: Friday, January 13, 2023 5:50 AM
> To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Cc: Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
> Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
>
> Hi Dmitry,
>
> Comments ** below.
>
> -----Original Message-----
> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Sent: Thursday, January 12, 2023 6:15 AM
> To: Kim Steiner <kim.steiner@sightlineapplications.com>
> Cc: Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
> Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
>
> Hi Kim,
>
> I hope you feel better now!
> ** yes, feeling better!  Thank you.  We just finished moving our office to a new location so haven't been able to do any GPU temp testing yet.  Once we get the test area set up, then that will begin (next week).
>
> On 29/12/2022 16:19, Kim Steiner wrote:
>> Hi Dmitry,
>>
>> Happy Holidays to you too!
>> I am still dealing with this cold and am not able to go into the
>> office to do any testing this week.  I am working remotely so will do
>> some power cycles/reboots on the DB820c today.  I hope to see your
>> same results 😊
>
> Were you able to do resume the boot and cpufreq tests by chance?
> ** I feel confident boot is working successfully and have rebooted many times.  I also below the cpufreq is working as expected.  I have tested both the boot and cpufreq on the DB820c and our custom board.
>
>>
>> I had also been running our custom board with the latest from last week (cpufreq changes).  With a higher intensity use of the GPU, the frame rate (should be 60fps) bounces a lot.  We think this is because the GPU is doing some frequency changes on the fly.  In 4.14 kernel, the GPU frequency was not changing so we think this is why the frame rate was a solid 60fps in high intensity GPU situations.  Do you have any suggestions?  Can we just use a single GPU frequency?
>
> I'll look into this during the forthcoming week.
>
> An update from my side. I got the hardware package today. I must admit, it looks like a constructor :-)
>
> If your or anybody from your colleagues will have time next week to walk me through the assembly and first boot, I'd really appreciate that.
>
> ** yes!  Someone here can help walk you through the assembly and first boot.  Should I set up a meeting?  Which day works for you?
>
>>
>> I will be out Friday-Monday for the New Year's holiday.  Have a Happy New Year!
>>
>> Thanks,
>> Kim
>>
>>
>>