Hello Chris,
there is no new requirement that I know of. The driver should parse the
same FDT fields that have been parsed by libbsd earlier. It only want's
to avoid the double initialization that had been done by RTEMS and libbsd.
But there is a simple method how we can find out whether it's FDT
related: Please try the dtb that I normally use:
https://nc.c-mauderer.de/index.php/s/JntMtLrE2GpH2Xf
That FDT is build from the FreeBSD sources from that revision:
https://github.com/freebsd/freebsd-src/tree/19a6ceb89dbacf74697d493e48c388767126d418
Note: I don't think that using that FDT is a solution. It's just to find
out whether it's the problem. A solution would be to find a method how
we can distribute matching FDTs with various licenses.
Best regards
Christian
On 23/06/2021 07:24, Chris Johns wrote:
I have bisect'ed the failure and this is the commit that is the problem:
https://git.rtems.org/rtems/commit/?id=56074644a733ecc984722da2a1b61736275270c0
Hmmmmm.... Is there a new requirement on the needed FDT for a beagleboneblack.
Chris
On 23/6/21 2:52 pm, Chris Johns wrote:
Hi,
hello.exe is not running. Any hints?
master at ...
https://git.rtems.org/rtems/commit/?id=b47dbbc5f7c8518634c7c5fccd57d78c65444f2d
config.ini:
[DEFAULT]
BUILD_TESTS = False
RTEMS_DEBUG = True
RTEMS_POSIX_API = True
[arm/beagleboneblack]
BUILD_TESTS = True
output:
RTEMS Beagleboard: am335x-based
ARM Debug: 0x4b141000
*** FATAL ***
fatal source: 1 (INTERNAL_ERROR_RTEMS_API)
fatal code: 22 (0x00000016)
RTEMS version: 6.0.0.4977dc74c60e75b90fe8dd72e4dedafd55d70c73
RTEMS tools: 10.3.1 20210409 (RTEMS 6, RSB
4e6dc6431435821a534da6307e72ecbd7e42b82a, Newlib 0c0f3df)
executing thread ID: 0x089010001
executing thread name: IDLE
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
