Ultibo core a full featured embedded (no OS) environment for Raspberry Pi

[Ultibo]

I`ve tried firefox 44 / opera latest / IE 11 and nothing worked.

I've checked everything I can from here and nothing appears to be wrong, what part of the world are you trying from? Can anyone else confirm availability of the site?

[taazz]

I`ve tried firefox 44 / opera latest / IE 11 and nothing worked.

I've checked everything I can from here and nothing appears to be wrong, what part of the world are you trying from? Can anyone else confirm availability of the site?

I have no problems opening it with firefox 44.0.2 both with noscript enabled and disabled.

[vincococka]

Should ultibo.org resolve to 67.225.133.22 ?
I`m connecting from Slovakia, and I`ve changed my ISP in the meantime so maybe something wrong with routing (BGP)..... maybe.

Can you ping from your server IP addr 87.197.159.146 ?

[taazz]

Should ultibo.org resolve to 67.225.133.22 ?
I`m connecting from Slovakia, and I`ve changed my ISP in the meantime so maybe something wrong with routing (BGP)..... maybe.

Can you ping from your server IP addr 87.197.159.146 ?

C:\Users\xxxxxxx>nslookup ultibo.org
Server:  UnKnown
Address:  fe80::20e:8fff:fe6c:9a20

Non-authoritative answer:
Name:    ultibo.org
Address:  67.225.133.22

how about running a tracert on your end?

[vincococka]

On my side it`s like this:

Code: [Select]

C:\windows\system32>TRACERT.EXE -d ultibo.org

Tracing route to ultibo.org [67.225.133.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2    11 ms    10 ms    11 ms  213.81.233.252
  3    11 ms    14 ms    11 ms  213.81.235.93
  4    12 ms    11 ms    11 ms  213.81.253.14
  5    14 ms    16 ms    11 ms  149.6.26.5
  6    13 ms    13 ms    13 ms  130.117.48.142
  7    19 ms    19 ms    19 ms  130.117.49.137
  8    25 ms    25 ms    25 ms  154.54.38.57
  9    33 ms    32 ms    32 ms  130.117.0.141
 10   134 ms   134 ms   134 ms  154.54.58.69
 11   134 ms   134 ms   134 ms  154.54.44.141
 12   135 ms   135 ms   134 ms  154.54.44.105
 13   134 ms   134 ms   133 ms  154.54.31.89
 14   134 ms   134 ms   134 ms  154.54.7.129
 15   134 ms   134 ms   134 ms  154.54.46.178
 16   136 ms   135 ms   136 ms  154.54.29.66
 17   125 ms   125 ms   125 ms  38.88.42.54
 18   132 ms   149 ms   132 ms  209.59.157.229
 19   136 ms   136 ms   140 ms  69.167.128.122
 20   137 ms   136 ms   137 ms  69.167.128.201
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.

It times out after 69.167.128.201
Can you post your traceroute?

[taazz]

Sure here you go.

Tracing route to ultibo.org [67.225.133.22]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.1.1
  2    22 ms    16 ms    35 ms  80.106.108.117
  3    20 ms    55 ms    35 ms  79.128.240.177
  4    17 ms    19 ms    22 ms  62.75.3.85
  5    60 ms    61 ms    60 ms  62.75.4.166
  6    60 ms    82 ms    60 ms  195.50.118.169
  7     *        *        *     Request timed out.
  8   154 ms   150 ms   172 ms  4.15.84.142
  9   168 ms   157 ms   158 ms  209.59.157.206
 10   190 ms   160 ms   159 ms  69.167.128.120
 11   166 ms   178 ms   158 ms  69.167.128.201
 12   168 ms   178 ms   178 ms  67.225.133.22

Trace complete.

[Thaddy]

Code: [Select]

Tracing route to ultibo.org [67.225.133.22]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  CISCOC1856 [192.168.1.1]
  2     2 ms     1 ms     1 ms  gwlogin.net [192.168.192.1]
  3     *        *        *     Request timed out.
  4    11 ms    12 ms    12 ms  212.142.62.149
  5     *        *        *     Request timed out.
  6   129 ms   118 ms   112 ms  us-was02a-rd2-ae105-0.aorta.net [84.116.130.66]
  7   114 ms   113 ms   114 ms  us-was03a-ri1-ae10-0.aorta.net [84.116.130.174]
  8   115 ms   113 ms   119 ms  xe-5-0-3 [204.148.11.109]
  9   128 ms   130 ms   128 ms  0.et-10-1-0.GW7.CHI13.ALTER.NET [140.222.234.221]
 10   144 ms   152 ms   208 ms  liquidweb-gw.customer.alter.net [152.179.92.134]
 11   141 ms   141 ms   144 ms  lw-dc3-core2-vlan66.rtr.liquidweb.com [209.59.157.226]
 12   143 ms   145 ms   144 ms  lw-dc3-core2-nexus-po6.rtr.liquidweb.com [69.167.128.126]
 13   143 ms   142 ms   140 ms  lw-dc3-dist15-po6.rtr.liquidweb.com [69.167.128.205]
 14   141 ms   144 ms   151 ms  host.australiangreenhosting.com.au [67.225.133.22]

[vincococka]

Thanks, it seems that 209.59.157.229 is returning back TTL exceeded

[ahmadian]

Great work 
When we see FpGui+Ultibo?
Thanks

[Ultibo]

When we see FpGui+Ultibo?

There is no timeframe yet, but from a little bit of looking at the source it looks like it should be possible. It seems to require a framebuffer (already available) and an event queue for mouse and keyboard events (mostly available too).

If you or anyone else knows more about the inner workings of fpGUI and where Ultibo would need to hook in to make these things work it would be really helpful information to save some time trawling through the source code.

[Ultibo]

The new Raspberry Pi 3 is now fully supported in 32 bit mode. A 64 bit implementation will be developed when further information becomes available.

Full details and how to update your install here:

https://ultibo.org/forum/viewtopic.php?f=4&t=52

[DonAlfredo]

Thanks for supporting RPi3 !

Question:
I can do all the update-install work myself naturally.
But when will you provide an Ultibo-update with RPi3 ?
I am asking because I am in time-shortage, and if you plan an update within a (couple of) week(s), I will wait for that update !

Thanks again for RPi3 !

[Ultibo]

Question:
But when will you provide an Ultibo-update with RPi3 ?

The next update for the Ultibo installer (with updated FPC and Lazarus) will be released once a few more items are completed, probably later next month unless there is an urgent need for a bug fix etc.

Rebuilding the RTL to get RPi3 support is pretty simple and should take no more than 10 minutes.

• Download the Ultibo core source as a zip from https://github.com/ultibohub/Core
• Unzip to a temporary folder
• Copy over the top of your existing install (\source\rtl\ultibo in the zip to \source\rtl\ultibo in your install)
• Open Lazarus
• Select Tools, Build Ultibo RTL...
• Click Build and wait until you see "Build RTL completed successfully", then click Exit
• Restart Lazarus
• Select Tools, Rescan FPC Source Directory

After this any project compiled for RPi2 will also work on RPi3.

The instructions (with screenshots) are also here https://ultibo.org/wiki/Building_from_Source in the "Building the Ultibo RTL" section, no need to rebuild FPC or Lazarus just the RTL.

Thanks.

[DonAlfredo]

Thanks for the instructions ! They work for me.

However, I still cannot get Ultibo to run on my RPi3 ... 

Compiled the RPi2 hello world example.
Copy kernel7.img onto SD, together with latest firmware.
I get the nice colored screen on boot, but nothing more happens. Just the colored screen and that's it.
Also green LED does not flash.

So, I need some more info for RPi3.
* what firmware to use (currently I am using the firmware from here: https://github.com/raspberrypi/firmware ; I just copy over  the whole boot directory) ?
* do I need only the kernel7.img or also the generated elf executable ?
* anything else that could be important.

[Ultibo]

However, I still cannot get Ultibo to run on my RPi3 ... 

Compiled the RPi2 hello world example.

For sanity checking I just tried the process myself, installed using Ultibo installer, updated to latest code from GitHub, rebuilt the RTL and compiled the Hello World example.

Surprise, surprise I get a colorful screen as well

However the fix is simple, the example is missing one unit from the uses clause.

Simply add the BCM2709 unit so it looks like this instead:

Code: Pascal  [Select][+][-]

1. uses
2.   GlobalConst,
3.   GlobalTypes,
4.   Threads,
5.   Console,
6.   Framebuffer,
7.   BCM2836,
8.   BCM2709;  //This one is missing from the example!
9.  

Compile again and everything should work correctly. The BCM2709 unit provides the core drivers for the RPi2/3 including the Framebuffer driver, in the original release the framebuffer was always included by a define to ensure something always showed on screen. This define was removed in a recent commit so that console and framebuffer can be optional now.

For completeness your SD card should contain the following files in the root directory:

bootcode.bin
fixup.dat
start.elf
kernel7.img

There can be others but these 4 are required, the SD should be FAT formatted.

Some other examples are also possibly missing the BCM2709 unit (BCM2708 for RPi1) so I'll check them all and push an update to GitHub.

Please let me know how you go, thanks.