new kernel.img sizes on 18 August 2018

[paulwratt]

are these correct, they are 2Mb less than before, and the numbers in the final make output dont add up any more either:

### Warning: The DATA segment is not empty.
### Please examine emutos.map and use "const" where appropriate.
# TEXT=0x00008000 STKBOT=0x00083900 LOWSTRAM=0x00000800 BSS=0x0004b200 MEMBOT=0x0008b900
arm-none-eabi-objcopy emutos.elf -O binary kernel7.img
# RAM used: 571648 bytes (528590 bytes more than TOS 1.62)

sysop@pipaos:~/build/emu/pTOS$ expr 571648 - 528590
43058

-rwxr-xr-x  1 sysop sysop 274820 Aug 18 11:00 kernel7.img
-rwxr-xr-x  1 sysop sysop 274188 Aug 18 10:59 kernel.img

are these similar to what you are getting?

[paulwratt]

well although the numbers dont add up, they are in fact totally valid.

I can get these images to boot on:
a) hand made FAT16 boot partition and files, on RPi B (armv6)
b) pre-built FAT16 boot partition and files, on RPi B and RP 2B+ (armv7)

Apparently my emudesk.inf file is broken, so I dont get to the Desktop immediately on a) setup.

All boots show USB hub found, but no devices after that (I use a wireless keyboard and mouse), even when plain USB keyboard is used. I have a regular USB mouse too, but since the regular keyboard did not work I did not try it.

The wireless mouse shows no powered activity on the USB reciever. IE when I turn mouse on/off there is not even mouse "red light" activity from IR sensors inside mouse, which means there is nothing paired to it that has power (USB reciever).

can you upload/import a usable emudesk.inf file.

edit: note the RPi 2B+ I am testing with only boots HDMI at 640x480, the same as SDTV connector. The 1280 x 720 is being scaled down by the RPi hardware, IE the HDMI monitor confirms 640x480.

[paulwratt]

A note on RPi Device Tree. The way the pTOS kernel.img boot atm, after start.elf, there is a dt present at 0x00000100, and populated the same as your boot partition *.dtb files, with /overlays/* and the relavent config.txt settings.

[kelihlodversson]

I've been considering adding support for ATAGs and device trees at some point, although it's currently not too high on my priority list.