[JarekD]

Now I have another question.
In the SBC Ref Design there is a comment about U6:
This inverter can be removed if SW
is updated to change the polarity
the processor drives the eMMC reset.

How can I know if the software is updated or not?
Removing the inverter will cause no connection between the SiP and eMMC reset. I think that in case the software is updated the inverter should be replaced by non-inverting buffer or just a jumper? Am I right?

Thank you in advance

[JarekD]

Thank you,

I have seen C-SiP, but first I will try to fit eMMC under the SiP to have my PCB smaller.

Is it possible to download JEDEC standards for free?

[JarekD]

Thank you for yor reply.

Now I have doubt how should I connect boot configuration resistors. I understand that I should follow SBC design if I want to run BeagleBone Black software on OSD3358-512M-ISM. I have checked that the configuration of these pull-ups and pull-downs in RED and SBC designs are the same apart from LCD_DATA5 pin which is low state in RED design and high state in SBC. Surprisingly the comments in both designs suggest that this pin should be low state:
CLKOUT1 disabled (SYSBOOT[5] = 0b)

Also the comments:
SYSBOOT[15:0] = 0x401C (default)
– Boot Order: MMC1, MMC0, UART0, USB0
SYSBOOT[15:0] = 0x4018 (SD boot)
– Boot Order: SPI0, MMC0, USB0, UART0

are consistent with RED design but suggests a mistake in SBC design (R56 should be DNI-marked instead of R81).

I want to use only half of the resistors to save space.

Is it really a mistake in SBC design? Or does it not influence the system very much?

[JarekD]

Thanks for your response. Now I have some off-topic questions.
Do I have to remember about anything other than mapping the pins when using OSD3358-512M-ISM instead of OSD3358-512M-BAS?

For example, I can see that OSD-3358-SM-RED uses reset supervisor which is not used in OSD3358 SBC design. Is that for increased reliability only or the hardware inside the SiPs is somehow different so that one of them requires a supervisor an the other doesn’t?

The other question is that if I can omit some hardware used in OSD3358 SBC which I don’t need (e.g. HDMI framer)? Is it possible that omitting some hardware will cause device-tree related problems with the remaining hardware? I assumme that the device tree will not be modified.

[JarekD]

I need to use AR8035-AL1B for industrial temperature range which is even more difficult to obtain.
Is that possible to use any other part which is more common so that I can use linux image \ device tree provided with OSD3358-SM-RED?

I don’t need gigabit ethernet in my application, 100Mb would be enough. I know that OSD3358 SBC uses LAN8710 but it also uses bigger SIP.

Is there any design that integrates OSD3358-512M-ISM with ETH10/100 chip which is available on Mouser/Farnell and has device tree ready to download so that it would not require any low-level programming effort?

I may also use USB to Ethernet bridge solution. Is there any bridge that would not require any drivers for Linux?

Thank you in advance,
Jaroslaw

• This reply was modified 6 years ago by JarekD.
• This reply was modified 6 years ago by JarekD.

[Author]

Posts