No usable event timer found on RPI2

[Michael Tuexen]

> On 13 Apr 2016, at 16:41, Ian Lepore <ian at freebsd.org> wrote:
> 
> On Wed, 2016-04-13 at 16:34 +0200, Michael Tuexen wrote:
>>> On 10 Apr 2016, at 00:29, Ian Lepore <ian at FreeBSD.org> wrote:
>>> 
>>> On Sat, 2016-04-09 at 11:17 -0700, bob prohaska wrote:
>>>> On Sat, Apr 09, 2016 at 10:53:34AM -0600, Ian Lepore wrote:
>>>>> 
>>>>> The rpi.dtb file lives on the FAT partition where u-boot is,
>>>>> but
>>>>> it's
>>>>> created by the freebsd build process and installing the kernel
>>>>> puts
>>>>> the
>>>>> new dtb into /boot/dtb on the freebsd rootfs.  Something else
>>>>> (crochet
>>>>> or some similar script, or you by hand) have to copy from there
>>>>> to
>>>>> the
>>>>> FAT partition on the sdcard.
>>>>> 
>>>>> Note that right now all of this is unique to rpi.  For other
>>>>> arm
>>>>> boards, u-boot isn't involved in the dtb file loading at all
>>>>> and
>>>>> the
>>>>> file is normally read by ubldr from the freebsd filesystem.
>>>>> 
>>>>> There may come a day when all arm boards have to work more like
>>>>> rpi
>>>>> does now (due to the way the u-boot world is evolving).
>>>>> 
>>>>> 
>>>> 
>>>> What inhibits making the copy to FAT part of  kernel install?
>>>> 
>>> 
>>> The freebsd build process doesn't know anything about filesystems,
>>> it
>>> just installs things to DESTDIR (which is / by default).
>>> 
>>> If you're doing the kernel build and install native on the rpi, you
>>> could get the effect you want by doing:
>>> 
>>> mount -t msdosfs /dev/mmcsd0s1 /boot/dtb
>>> make installkernel
>>> umount /boot/dtb
>>> 
>>> At least, I think that should work.
>> Hi Ian,
>> 
>> I'm running into the same problem. I updated the source on a RPI2
>> today,
>> build a new kernel (with modules), installed it, manually copied
>> /boot/dtb/rpi2.dtb
>> to /boot/msdos/ (which is mounted) and rebooted.
>> The dtb files have the correct date, but the kernel panics. Do I need
>> to copy more?
>> 
>> Thanks for your help!
>> 
> 
> Sorry, I don't have any particular insight into this one (I don't have
> an rpi2).  I was just chiming in on the previous question about the
> specific issue of where the .dtb file lives and how it gets loaded (and
> it turns out I was a bit wrong about that: it's actually the rpi
> firmware (in the gpu) that loads the dtb file and passes it to u-boot).
OK.

Could it be that I need a newer version of uboot:

> ls -l /boot/msdos/
total 7320
-rwxr-xr-x  1 root  wheel    17900 May  8  2015 BOOTCODE.BIN
-rwxr-xr-x  1 root  wheel      103 May  8  2015 CONFIG.TXT
-rwxr-xr-x  1 root  wheel     6161 May  8  2015 FIXUP.DAT
-rwxr-xr-x  1 root  wheel     2366 May  8  2015 FIXUP_CD.DAT
-rwxr-xr-x  1 root  wheel     9214 May  8  2015 FIXUP_X.DAT
-rwxr-xr-x  1 root  wheel     1447 May  8  2015 LICENCE.BRO
-rwxr-xr-x  1 root  wheel      607 May  8  2015 README
-rwxr-xr-x  1 root  wheel     9153 Apr 13 14:37 RPI2.DTB
-rwxr-xr-x  1 root  wheel  2664088 May  8  2015 START.ELF
-rwxr-xr-x  1 root  wheel   567672 May  8  2015 START_CD.ELF
-rwxr-xr-x  1 root  wheel  3621768 May  8  2015 START_X.ELF
-rwxr-xr-x  1 root  wheel   301876 May  8  2015 U-BOOT.BIN
-rwxr-xr-x  1 root  wheel   261721 May  8  2015 UBLDR

Best regards
Michael
> 
> -- Ian
> 
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"