Jump to content

Build environment broken?


Christos

Recommended Posts

Did a fresh OrangePi Plus2E image, legacy, Debian jessie, desktop, RT, but the SD boot gives this

U-Boot SPL 2016.11-armbian (Jan 06 2017 - 14:49:44)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2016.11-armbian (Jan 06 2017 - 14:49:44 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus 2E
I2C:   ready
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
hdmi enabled
Error: no valid bmp image at 66000000
In:    serial
Out:   vga
Err:   vga
Net:   phy interface7
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0
6944 bytes read in 145 ms (45.9 KiB/s)
There is no valid bmp file at the given address
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2092 bytes read in 178 ms (10.7 KiB/s)
## Executing script at 43100000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2092 bytes read in 170 ms (11.7 KiB/s)
## Executing script at 43100000
Booting from SD
144 bytes read in 123 ms (1000 Bytes/s)
3138997 bytes read in 406 ms (7.4 MiB/s)
5100840 bytes read in 519 ms (9.4 MiB/s)
** File not found /boot/.next **
** File not found .next **
36808 bytes read in 491 ms (72.3 KiB/s)
SCRIPT FAILED: continuing...
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
USB4:   USB EHCI 1.00
USB5:   USB OHCI 1.0
scanning bus 0 for devices... 4 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 4 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 2 USB Device(s) found
scanning bus 5 for devices... 1 USB Device(s) found

USB device 0: unknown device
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 44
*** Unhandled DHCP Option in OFFER/ACK: 44
DHCP client bound to address 192.168.1.12 (154 ms)
*** Warning: no boot file name; using 'C0A8010C.img'
Using ethernet@1c30000 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1
Filename 'C0A8010C.img'.
Load address: 0x42000000
Loading: *
TFTP error: 'File not found (/var/tmp/C0A8010C.img)' (1)
Not retrying...
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-20-40-62-97-69
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8010C
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8010
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A801
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
*** ERROR: `serverip' not set
Config file not found
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 44
*** Unhandled DHCP Option in OFFER/ACK: 44
DHCP client bound to address 192.168.1.12 (120 ms)
Using ethernet@1c30000 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1
Filename 'boot.scr.uimg'.
Load address: 0x43100000
Loading: *
TFTP error: 'File not found (/var/tmp/boot.scr.uimg)' (1)
Not retrying...
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 44
*** Unhandled DHCP Option in OFFER/ACK: 44
DHCP client bound to address 192.168.1.12 (137 ms)
Using ethernet@1c30000 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1
Filename 'boot.scr.uimg'.
Load address: 0x42000000
Loading: *
TFTP error: 'File not found (/var/tmp/boot.scr.uimg)' (1)
Not retrying...
=>

Is the environment working ok for others after todays commits?

 

Link to comment
Share on other sites

Nothing relevant was changed recently. It must be some problem on your side - reboot host, remove cache, ...

 

If you are compiling with RT I can't give you warranty that patch still applies O.K. ... it's some time that I built RT kernel.

Link to comment
Share on other sites

Hello Christos & Igor Pecovnik,

Thanks very much for all this great work!

 

I am very NOOB to building kernels

I wanted RT kernel to use with linuxcnc, specifically linuxcnc's 'hal' system

 

Before building, I repaired 2 patch files that are missing 0x0a at end of file

( they produce err saying the file ends in middle of line, actually meaning at EOF )

friendlyarm_m1_gigabit.patch ( ends in 0x3a)

ov5640-enhanced-device-with-vfe-drc-table-fix.patch (ends in 0x29)

 

I repair by simply opening in nano and immediately saving.

This action adds 1 0x0a byte to each file, and changes the timestamp.

 

But, changing the timestamp creates another problem,

the compile reports that it cannot update due to the change.

 

I chose to continue

Is this correct to add the missing 0x0a?

Can I ignore the errors about ending in middle of line?

 

 

I am trying to make preempt model 5,

Christos said "Did a fresh OrangePi Plus2E image, legacy, Debian jessie, desktop, RT, but the SD boot gives this"

Which preempt model did you succeed with?

 

regards

tomp

 

 

Link to comment
Share on other sites

2 hours ago, tomp said:

But, changing the timestamp creates another problem,

the compile reports that it cannot update due to the change.


That's correct behaviour. You don't alter main script - and if you do, warning is issued.

 

2 hours ago, tomp said:

Can I ignore the errors about ending in middle of line?


Yes.

 

2 hours ago, tomp said:

Which preempt model did you succeed with?

 

IIRC all works but full preempt.

Link to comment
Share on other sites

Thanks Igor,

I built preempt model 4 ok and booted it on OPi+2e

but my RT app does not think the result is really an RT kernel

the hint is  from  uname -a...

Linux orangepiplus2e 3.4.113-rt143-sun8i #2 SMP PREEMPT Thu May 18 08:04:38 ICT 2017 armv7l GNU/Linux

 

it does not say "PREEMPT RT" so apps wont work ( and many linuxes are PREEMPT out of the box )

 

I was able to load and run 'cyclictest' from https://www.kernel.org/pub/linux/utils/rt-tests/

but the jitter was way too high (500 to 2500uS) on the few tests i tried (https://rt.wiki.kernel.org/index.php/Cyclictest)

So, I dont have very tight timing bounds. I'd like to get 200uS, but its not christmas today ;-)

 

Thanks for your help, the fix is beyond my skills. I will watch for news though, its a great little board.

TomP

 

 

Link to comment
Share on other sites

On 06/01/2017 at 2:06 PM, Christos said:

Thanks @Igor ,

 

Performed a new git clone and now its ok again with all the added gizmos I put on.

 

Lesson learned, will not ask again that question unless I have done a new git clone and flushed any cache. :rolleyes:

 

I met exactly the same errors today...

new git clone and flush any cache??

How to flush the cache folder under armbian/cache?

 

 

Cheers

Pei

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines