Notices


Reply
Thread Tools
Posts: 140 | Thanked: 538 times | Joined on Oct 2013 @ France
#101
Originally Posted by gerbick View Post
But he cannot go any further it seems despite having a flasher. Now... how to obtain firmware to flash to go further. I want to see this thing boot!
As I understood (https://talk.maemo.org/showpost.php?...2&postcount=89), the flasher didn't succeed to connect to the device, so having a firmware to flash would not yet be enough.

I wonder how much of the flasher/bootloader is tied specifically to ARM ?

Here, we have an Intel x86 device, not an ARM based one like all previous Nokia (If I am not mistaken).
The flasher program is really low level - at least from what I remember when using it for Symbian, where we could flash a dead device through USB. That means, there is a bootloader of some sort in the device, separate form the OS. What I don't know is if this bootloader is part of the chip (like DfuSe in STM32 devices, which would then likely be different/incompatible when switching to x86), or if it is simply a part of firmware (like U-boot or Grub) which could then have been implemented in a compatible way in a x86 device ?

Is there any master who would knows more on this ?
 

The Following 3 Users Say Thank You to Zeta For This Useful Post:
gerbick's Avatar
Posts: 6,396 | Thanked: 13,674 times | Joined on Jul 2007 @ undecided.
#102
Originally Posted by Zeta View Post
I wonder how much of the flasher/bootloader is tied specifically to ARM ?

Is there any master who would knows more on this ?
Asking the real questions here. And yes, you're right about it not being seen by the flasher utility.
__________________
gerbick | iPhone 7 [ 128GB iOS 10.3 Beta ] | iPad Pro [ 128GB iOS 10.3 Beta ]
Former Maemo Council Member - 2015
 

The Following 3 Users Say Thank You to gerbick For This Useful Post:
Community Council | Posts: 3,920 | Thanked: 9,128 times | Joined on May 2012 @ Southerrn Finland
#103
There are some quite fundamental things yet unclear with the prototypes presented here.

The deciding question is what is the hardware platform, is it intel or arm? That has not fully been cleared yet, as I think the SOC's are under a welded shielding cage as @dirkvl noted. Hence it would need a bit of meddling to actually eyeball the chips.

Something could be deduced from the boot display, as I think the devices (or one/some of them?) are in a mode that shows up the startup messages on screen. It scrolls probably too fast for human reading so it is advisable to make a video recording of the bootup messages.

However, the OS by itself doesn't necessarily tell anything about the intended HW platform since it is fairly common to run first development releases on an existing platforms when the "Real HW" is not yet made in sufficent quantities so that all involved R&D people would have their own development environment.
Hence, it is possible that the HW platform is arm but the OS in the device is Ilmatar.
(This is a very common R&D pattern in Nokia, and I believe also in other design houses.)

As for the flasher; I believe that the base protocol between the flasher and NOLO is most probably same whether the HW platform is arm or intel; it is designed to be fairly insensitive for the underlying architecture.
Flasher has two different modes; an inquiry/setting mode where device operation parameters can be read and tweaked and the actual flashing mode which is implemented by separate extension for each device model.

In the flashing mode the flasher utility reads a specific part from the image file called "APE Algorithm" which is a self-contained rescue-OS image which is sent to device and which therein performs the actual device-dependent actions of the flashing.
This way it doesn't make any difference what HW platform is under flashing.
The trick here is now to find a good image file to be flashed to the device. (pro tip; you won't find one )
 

The Following 6 Users Say Thank You to juiceme For This Useful Post:
Posts: 1,093 | Thanked: 5,601 times | Joined on Feb 2010 @ Holland
#104
Maybe there is some sw expert that can do these investigations better than me?
 

The Following User Says Thank You to dirkvl For This Useful Post:
wicket's Avatar
Posts: 486 | Thanked: 2,202 times | Joined on May 2010 @ Colombia
#105
Originally Posted by dirkvl View Post
Hmm i coul pull one of the shielding caps from the pcb, but don't know if n950 will like it if i pull out my heat gun
Hmm, no screws? Now I wonder if the case damage comes from it being prised open.

Originally Posted by juiceme View Post
The deciding question is what is the hardware platform, is it intel or arm?
What about the IC errors that are specific to the Moorestown/Medfield IC chip (as shown in the patch in the mailing list linked to by Dirk)? There are the other pointers such as "medfield_wifi_power" in the local mode photo and "MEDFIELD" in Dirk's Windows device manager screenshot. Perhaps n950 could tell us what his photo of the Intel logo actually is (the battery icon makes me wonder if it is a boot screen). I'm not saying you're wrong, but so far I've seen no indication that the hardware platform might be ARM.
__________________
DebiaN900 - Native Debian on the N900.

Mobile devices with mainline Linux support - Help needed with documentation.

"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
 

The Following 2 Users Say Thank You to wicket For This Useful Post:
Posts: 1,005 | Thanked: 1,001 times | Joined on Aug 2011
#106
Originally Posted by wicket View Post
Hmm, no screws? Now I wonder if the case damage comes from it being prised open.



What about the IC errors that are specific to the Moorestown/Medfield IC chip (as shown in the patch in the mailing list linked to by Dirk)? There are the other pointers such as "medfield_wifi_power" in the local mode photo and "MEDFIELD" in Dirk's Windows device manager screenshot. Perhaps n950 could tell us what his photo of the Intel logo actually is (the battery icon makes me wonder if it is a boot screen). I'm not saying you're wrong, but so far I've seen no indication that the hardware platform might be ARM.
It's the startup LOGO when device is in charge just before local mode logs.
 

The Following 2 Users Say Thank You to n950 For This Useful Post:
Community Council | Posts: 3,920 | Thanked: 9,128 times | Joined on May 2012 @ Southerrn Finland
#107
Originally Posted by wicket View Post
What about the IC errors that are specific to the Moorestown/Medfield IC chip (as shown in the patch in the mailing list linked to by Dirk)? There are the other pointers such as "medfield_wifi_power" in the local mode photo and "MEDFIELD" in Dirk's Windows device manager screenshot.
Yes, I have to admit I missed those. That evidence indeed suggests it is an Intel based device.
 

The Following 2 Users Say Thank You to juiceme For This Useful Post:
Posts: 1,005 | Thanked: 1,001 times | Joined on Aug 2011
#108
Hello everybody,

Dirk can't progress with the devices he is busy.
I wait he try to boot 2 others devices.

I would like two things:

- 3 batteries fitted inside and connected to the device.
- 3 3D printed rear covers for 3 deviced.

If anybody can do this work let me know here and Dirk can send to you the 3 devices.
 

The Following 2 Users Say Thank You to n950 For This Useful Post:
Posts: 2 | Thanked: 10 times | Joined on Apr 2017
#109
I'm student of university of telecommmunications here in Russia. We have IoT labaratory founded by Intel and we were working w/ Medfield platform. We can take a look for some hardware and software, if it's needed.
 

The Following 6 Users Say Thank You to sasha19323 For This Useful Post:
Posts: 1,005 | Thanked: 1,001 times | Joined on Aug 2011
#110
Originally Posted by sasha19323 View Post
I'm student of university of telecommmunications here in Russia. We have IoT labaratory founded by Intel and we were working w/ Medfield platform. We can take a look for some hardware and software, if it's needed.
Hi,
If you have my 3 devices what you will do?
Please activate your email or PM.
 

The Following User Says Thank You to n950 For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 22:34.