Yes it's the same. I was wondering if it might be a generic one, but Koen was able to read his chip after replacing the contents of fw_env.config with the Ubuntu values. The stock Ubuntu doesn't expose the mtd device. So even if I install u-boot-tools on that fw_printenv can't find it.

I spent some time yesterday looking into mtd and looking at the output of mtd_debug and mtdinfo and I don't see how the values in the Ubuntu fw_env.config file correspond to the output from those tools.

> I looked at the source code you mentioned a few
> posts back and the mimas board .c file has offset
> as 0 for the mtd device (if I'm reading that
> right).

That's incorrect. That code is the kernel code patch which does not have any info about boot loader. What we lack is the GPL for their boot loader version. And they also turned off input/ouput for this boot loader so we can't see anything.

That's why I said I don't know yet where is the evns location, other than what Koen posted. Can you do a hex dump for mtd to see you can guess where the envs are, or you can dd the mtd0 and upload the dump somewhere so I can take a look.

I guess it's best to wait for Koen and see how they managed. Really all I was trying to do at this stage was to confirm the chip was being detected correctly (as you suggested it would be if fw_printenv worked).

Bob Wrote:
-------------------------------------------------------
> Hi bodhi and Koen
>
> I already tried that (default Ubuntu) config. It
> just gives a bad CRC message.
>
> Perhaps the dtb needs to match my spi chip? I
> edited the last dts with the details for my chip
> but couldn't figure out how to compile it to a
> dtb.

> do you want me to try these latest dtb files as
> well? I've had another response from Dell that
> they will chase the technical team for the uboot
> GPL sources of the T50.

Sure, please try the latest DTB file (good to do regression test).

Hope they will make GPL source available, that will solve the remaining issues for us. The fact that CRC error show up in Bob's box make me think there are 2 different u-boot version for T50 (Bob) and T10 (yours).

> Some more info about mtd. It seems the chip in my
> box is 8M while that in Bob's device is reported
> to be only 4M although that may possibly be due to
> different fw_env.config settings.

No, it is not fw_env.config. The size of the mtd is recognized by the kernel when it probes the mtd. So the mtd sizes are correct as the kernel sees. What in the fw_env.config is not the mtd size, it is the envs size. So if the envs size or the location are different, then the CRC error would make sense (this would be true if the u-boot versions are different between the 2 boxes).

OK, cool. It would be nice to have it working at some stage. I'd like to see if I can clean up the boot entries in the spi. I was able to edit them on Ubuntu with spi-w but they would reset back to default after a reboot. Which had me wonder if this was working right at all. Koen seemed to be able to edit them fine.

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.