Hello,
I have another BeagleBoard-xM turn up this morning. It's apparently a
rev B (can supply serial number privately). When it came, it had an SD
card adapter shoved somewhat precariously between the protruding GND pin
next to the camera port and the ethernet port and an microSD card
installed labeled "xM TEST 20100820". Perhaps these come with such cards
now, but I wasn't aware this was the case - is this a production issue?
Jon.
So the microSD card itslef was not plugged into the microSD connector? There is an adapter that should be floating around in the bag, but the microSD card itself should be inserted into the board connector. Where did you get the board from?
Gerald
So the microSD card itslef was not plugged into the microSD connector?
Yes, it was. I see it has the Angstrom disto on it, so ok, I guess it
does come with that (don't recall that being the case, but cool). Seems
it's a 4GB card that's been partitioned down to 128MB.
There is an adapter that should be floating around in the bag
This was my cause for concern. It had become lodged between some of the
pins. I suspect a bit of rough handling could damage some boards this
way...I'd recommend taping that down or shipping it outside of the bag
and inside the box. Perhaps it's not been a problem in reality.
Where did you get the board from?
Digikey. Also, out of interest perhaps you can clarify something about
the version. It reports as a rev A. in U-Boot but says Rev B. on the
box, and has an inverted (upside down) Ethernet port compared with my
older xM. Additionally, I noticed that the TAP device contained within
the DM37 has revved from version 0x0 to 0x1, which OpenOCD doesn't know
about (but I will teach it this when I have some time - I was just
playing while I ate lunch today after this came in the mail :P).
Jon.
No, the 128MB partition is the FAT partition. The second partition Carnot be read by a Windows machine.
I will check with the production guys on how they are placing the board in the boxes. Tape creates static, so I do not see that as a viable solution.
Yes, it will report as a Rev A. The Rev B boards did not get the update to read them as a Rev B. The only difference in Rev A vs B is the processor revision. All SW is exactly the same on bot A and B.
Gerald
No, the 128MB partition is the FAT partition. The second partition
Carnot be read by a Windows machine.
My point was actually that that partitions totalled to 128MB between the
one marked FAT32 and the 8MB Linux partition. The rest of the 4GB card
was unused, as I mentioned. Here was the partition map:
/dev/sdd1 * 1 15 120456 c W95 FAT32 (LBA)
/dev/sdd2 16 16 8032+ 83 Linux
Not that it even matters 
I will check with the production guys on how they are placing the
board in the boxes. Tape creates static, so I do not see that as a
viable solution.
I see that, but in that case they could just insert the adapter inside
the cardboard but outside of the plastic bag. The box alone should be
more than sufficient to protect a plastic adapter, and in the worst case
that it were somehow damaged, better that than the board itself.
Yes, it will report as a Rev A. The Rev B boards did not get the
update to read them as a Rev B. The only difference in Rev A vs B is
the processor revision. All SW is exactly the same on bot A and B.
Right. I assumed it was that (and also it's obvious that the PHY has
changed, as I can plainly see by plugging the cable in upside down). I
suspect U-Boot could be taught to tell them apart on processor rev.
Anyway, thanks for your help. I'll let you know when I get chance to fix
OpenOCD to recognize the revved processor (TAP revision is 1 not 0 now).
Jon.
Thank you for your suggestion.
Gerald